This repo / marketplaces will contain plugins I develop as I'm trying to hone my dev flow.
| Maybe they work for you too, maybe they won't. |
| Maybe they'll make claude hallucinate and wipe your computer 🤷 |
| Install at your own risk. |
A Claude Code plugin that turns Claude into an async coordinator -- it delegates all implementation to background sub-agents working in git worktrees while staying responsive to you.
Important
You have to remind Claude, every now and then, that it is a coordinator (I just say "yo, you're supposed to be the coordinator"). This is especially true in a new session, no matter how strongly worded the prompt in the hook for this plugin is.
/plugin marketplace add gm2211/claude-plugins
/plugin install claude-multiagent@gm2211-plugins
Note: The marketplace name is
gm2211-plugins(the repo can host multiple plugins). The plugin name isclaude-multiagent.
| Deploy | Github Actions |
|---|---|
![]() |
![]() |
- Async dispatch -- describe work, Claude files a ticket and spawns a sub-agent, you keep talking to it (basically team mode, but without having to figure out team composition)
- Git worktree isolation -- each agent works in
.worktrees/<branch>, no interference - Tickets and active agents dashboards -- live ticket list + agent status panes alongside your Claude session
- Auto-cleanup -- merge, remove worktree, close ticket, all in one step
- Claude Code
- Zellij terminal multiplexer
- bd (beads) issue tracker
- Git
On first use in a repo, the plugin detects missing permissions and offers to configure .claude/settings.local.json automatically. Just approve the prompt and restart the session.
Manual setup (or reference)
Add to your repo's .claude/settings.local.json:
{
"permissions": {
"allow": ["Read", "Edit", "Write", "Bash(bd:*)", "Bash(git:*)"]
},
"sandbox": {
"enabled": true,
"autoAllowBashIfSandboxed": true
},
"env": {
"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
}
}Why this works: autoAllowBashIfSandboxed auto-allows all bash commands within Claude's sandbox (filesystem restricted to repo dir, network restricted). Read/Edit/Write are explicitly allowed since they're not bash commands. bd and git are explicitly allowed for clarity.
Add your own project-specific permissions (build tools, test runners, etc.) to the allow array.
MIT

