Repository navigation
bulkhead: guards for the processes and ports that squad sessions still share #343
dooly6276
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Disclosure: I maintain bulkhead, an MIT licensed plugin of PreToolUse hooks for Claude Code.
claude-squad gives each instance its own tmux session and git worktree, so branches and files stay apart. The machine is still shared: every instance sees the same process table and the same ports. The collisions I kept hitting were an agent restarting its dev server with
pkill nodeand taking down the servers in the other worktrees, and a second worktree'snpm run devmoving to 3001 while its agent kept testing localhost:3000.bulkhead checks each shell command before it runs. kill-guard blocks a kill by name that would reach a process another session started, and it also blocks
pkill tmux. port-guard blocks starting a server on a port another agent session holds and names a free one. A blocked command goes back to the agent with the reason and a safer way to do it, such as stopping its own PID. The same guards load in Codex and Gemini CLI, which squad can also run.Install inside Claude Code with
/plugin marketplace add dooly6276/claude-bulkhead, then/plugin install bulkhead@bulkhead.https://github.com/dooly6276/claude-bulkhead
All reactions