Claude Bulkhead

English |
  한국어 |
  简体中文

claude-bulkhead

  Hooks that stop parallel Claude Code sessions on one machine from killing each other's servers or running it out of RAM.

7 guards, 9 commands, a status line, 5 slash commands, 1 skill, zero dependencies

  What is it |
  Why |
  Features |
  Install |
  Quick start |
  Remote |
  How it works |
  Guards |
  FAQ
Release notes: CHANGELOG.md.

What is it?

Claude Code hooks are small programs that Claude Code runs at fixed points, for example before every shell command, and that can stop the command and tell Claude why.

bulkhead is a set of these hooks for one situation: several Claude Code sessions, and their subagents, working on the same computer at the same time. Each session acts as if it had the machine to itself. bulkhead checks each shell command against what the other sessions are doing: which processes and ports belong to which session, how much RAM is left, and which git tree each session works in. When a command would hurt another session, it is blocked, and Claude gets a message with the safer command to run instead.

You need it if you run two or more Claude Code sessions at once, often one per git worktree, or your sessions and subagents start dev servers, builds and test runs.

You probably do not need it if you run one session at a time and do not let it start servers or builds. Most of what bulkhead does is about sessions getting in each other's way.

Why this exists

A common way to speed up work with Claude Code is to run several sessions on one repository, each in its own git worktree, each with its own subagents. git keeps the branches apart. The machine does not: every session shares the same ports, the same process table and the same RAM. That is where they collide.

- Two worktrees of the same app…