- Who it helps
- Developers running several Claude Code sessions or worktrees.
- Availability
- Public MIT repository; version 0.2.0 is described. Node 18 or later and Claude Code are required. Account costs are separate.
What the replay can show
The scan checks recorded shell commands for patterns such as broad process termination or changes to a checkout another session was using. Its value is a concrete list to review before enabling guards.
What the record cannot show
Transcripts do not preserve historical port occupancy or free memory, so those checks cannot be replayed. The repository’s illustrated guard demo uses stand-in processes. Live enforcement and false positives were not tested here.
What you can do
- Read the source and its evaluation conditions before applying this approach. Open reference ↗
Where the evidence stops
Documentation checked only. Hooks are not a demonstrated security boundary, and replay counts do not prove an incident would have happened.
Sources read. Primary sources checked November 9, 2026 UTC during the November 8 scheduled run. No third-party software, inference, proofs or complete workflow executed.
Sources & further reading
GitHub · implementation
Claude bulkhead repository ↗
README and version 0.2.0 behavior checked. Transcript replay omits historical port and free-memory checks; the illustrated demo uses stand-in processes.
dooly6276 · page checked 2026-11-09
More sources reviewed (1)
Hacker News · discussion
Bulkhead launch thread ↗
Original launch thread had no substantive independent replies in the returned page.
dooly6276 · page checked 2026-11-09
Coverage note: Independent dated demonstrations, cross-platform attention and complete execution remain unverified.
The record over time (1)
Dated source checks and published explanations. An observation date can differ from the original release date.
- · Added to Current
Bulkhead helps developers see where parallel coding sessions could interfere with one another on a shared computer.