Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By mgdickinson
Coordinate Claude Code, Codex, and generic CLI agents across sibling Git worktrees.
npx claudepluginhub mgdickinson/worktree-fleetUse whenever working in, creating, switching, listing, syncing, or coordinating Git worktrees, especially when a repo may use worktree-fleet or sibling AI sessions.
Initialize worktree-fleet for the current repository from Claude Code.
Declare or inspect intended file edits for worktree-fleet coordination.
Use before manually running git pull, git merge main, or git rebase main; safely catch this worktree up to the latest fleet integration target.
Use when starting feature work that needs an isolated Git worktree, before executing implementation plans in a new worktree, or whenever the user says to go in a worktree; fleet-aware replacement for generic git-worktree setup.
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Memory compression system for Claude Code - persist context across sessions
Ultra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.
Multi-model consensus engine integrating OpenAI Codex CLI, Gemini CLI, and Claude CLI for collaborative code review and problem-solving.
Curate auto-memory, promote learnings to CLAUDE.md and rules, extract proven patterns into reusable skills.
Unified status line for Claude Code with multi-CLI (Claude, Codex, Gemini, z.ai) usage monitoring, context, rate limits, and cost tracking
Harness-native ECC plugin for engineering teams - 64 agents, 262 skills, 84 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses
Add the Claude Code plugin. Open Claude in a repo. Work normally.
worktree-fleet keeps parallel Claude sessions in sibling Git worktrees aware of each other. When one worktree advances your integration branch, the others see it, catch up when safe, or get a clear blocked message when a human decision is needed.
No central service. No hidden branches. No git stash. No stale-main drift quietly piling up behind your back.
In Claude Code:
/plugin marketplace add mgdickinson/worktree-fleet
/plugin install worktree-fleet@worktree-fleet
That's it.
Now open Claude in any Git repo. On session start, the plugin initializes fleet state for that repo, installs safe Git hook blocks, registers the Claude session, and starts a small local monitor.
From then on, Claude has fleet awareness while it works.
If Claude tries to manually git pull, git merge main, or git rebase main, the plugin redirects it back through worktree-fleet sync so fleet can do the safety check first.
If Claude tries to mutate worktrees with raw Git, the plugin makes it check the fleet board first.
worktree-fleet observeMost days, you do not need to touch the CLI. The plugin is the point.
When you want to see whether fleet is actually working:
worktree-fleet observe
It opens a local dashboard with working status, agent heartbeat health, process liveness, safety hook status, pending catch-ups, sync blocks, divergent main targets, path contention, recent main events, and the local activity feed.
When you want the terminal version:
worktree-fleet watch
It shows sessions, worktrees, changed files, observed tool paths, optional planned intent, pending updates, blocked reasons, divergent targets, and recent activity in a compact terminal frame. Use worktree-fleet watch --web to launch the local observer from the watch command.
When you want a one-shot health check:
worktree-fleet status --refresh-current
When you want to force the current worktree to catch up:
worktree-fleet sync
When a feature worktree is ready to land onto local main:
worktree-fleet land
land syncs first, requires clean current and integration worktrees, fast-forwards the local integration branch, and records the main-advance event for sibling sessions.
When you want the local audit trail, including Claude monitor starts, stops, and sidecar errors:
worktree-fleet activity --all --limit 50
Claude is great at running multiple focused worktree sessions. Git is great at letting those worktrees drift apart while nobody notices.
worktree-fleet closes that gap. It records exact main-advance SHAs locally, watches active sessions, and only integrates when the current worktree is safe to touch. If there are staged changes, dirty overlap, an active merge/rebase, a missing commit object, or divergent main targets, it stops and tells you why.
State lives under:
~/.worktree-fleet/
├── activity/
├── adapters/
├── bus/main-events/
├── intents/
├── repos/
└── sessions/
The Claude plugin installs managed blocks into the repo's Git hooks. Existing hook content is preserved. Hook failures are logged and do not block normal Git commands.
Claude monitor and sidecar diagnostics are recorded in ~/.worktree-fleet/activity/*.jsonl as sidecar-started, sidecar-error, and sidecar-stopped events.
Remove fleet-managed hooks and local adapter registration with:
worktree-fleet uninstall
Claude gets the native plugin path. Codex has two pieces:
AGENTS.md block, which tells native Codex sessions to use fleet before worktree, sync, and land operationsfleet codex wrapper, which gives CLI Codex heartbeat/session sidecar behaviorFor native Codex, install the package once and stamp the current repo:
npm install -g @mgdickinson/worktree-fleet
cd /path/to/repo
worktree-fleet setup --adapter codex
worktree-fleet setup --adapter codex writes a managed block into the repo's AGENTS.md. That gives Codex native app sessions repo-level instructions to check the fleet board before worktree operations, use worktree-fleet sync for catch-up, and use worktree-fleet land for merging completed work back to local main. Existing AGENTS.md content is preserved; worktree-fleet adapter uninstall codex removes only the managed block.
Install the Codex plugin marketplace: