claude-bulkhead

What it does

When several Claude Code sessions and their subagents share one machine, they get in each other's way. pkill node stops another session's dev server, two sessions start servers on the same port, git add -A sweeps another session's half-finished edits into a commit, and parallel test runs use up the RAM. claude-bulkhead adds PreToolUse hooks that check the command text before it runs. When a command matches one of these patterns, the hook blocks it and tells the agent the reason and a command to run instead.

Guards

• kill-guard blocks kills by program name (pkill node, taskkill /IM node.exe). Kills by PID pass.
• port-guard blocks a dev server on a port another session already uses.
• memory-guard holds heavy commands when free RAM is low, and bulkhead-slot queues them.
• checkout-guard blocks git checkout, stash, add -A and commit -a in a tree another live session works in.
• wait-guard stops long sleeps and polling loops.
• disk-guard blocks whole-disk scans such as du -sh ~.
• orphan-reaper stops dev servers left behind by sessions that ended.
• basics blocks a few risky commands such as force pushes to main.

bulkhead scan

bulkhead scan replays the shell commands in your past Claude Code transcripts against the guards and shows what they would have stopped. It is read-only and sends nothing anywhere.

Limits

It parses command strings and is not a sandbox. Commands hidden in scripts, functions or aliases are not seen. A project's .claude/bulkhead.json can relax the guards for that repository.

Install

/plugin marketplace add dooly6276/claude-bulkhead
/plugin install bulkhead@bulkhead