orchestrate

AI Community

Skill notes

Scripts

Script · Purpose find-spare.sh [REPO_ROOT] · List free worktrees — one PATH BRANCH per line spawn-agent.sh SESSION PATH SPARE NEW_BRANCH OBJECTIVE [PR_NUMBER] [STEPS...] · Create window + checkout branch + launch claude + send task. Stdout: SESSION:WIN only recycle-agent.sh WINDOW PATH SPARE_BRANCH · Kill window + restore spare branch run-loop.sh · Mechanical babysitter — idle restart + dialog approval + recycle on ORCHESTRATOR:DONE + supervisor health check + all-done notification

Supervision model

You (the orchestrating Claude) are the supervisor. After spawning agents, stay in this conversation and actively monitor: poll each agent's pane every 2-3 minutes, check CI, nudge stalled agents, and verify completions. Do not spawn a separate supervisor Claude window — it loses context, is hard to observe, and compounds context compression problems. run-loop.sh is the mechanical layer — zero tokens, handles things that need no judgment: restart crashed agents, press Enter on dialogs, recycle completed worktrees (only after verify-complete.sh passes).

Checkpoint protocol

Agents output checkpoints as they complete each required step: Required steps are passed as args to spawn-agent.sh (e.g. pr-address pr-test). run-loop.sh will not recycle a window until all required checkpoints are found in the pane output. If verify-complete.sh fails, the agent is re-briefed automatically.

Worktree lifecycle

Windows are never auto-killed. The worktree stays on its branch, the session stays alive. The agent is done working but the window, git state, and Claude session are all preserved until you choose to recycle. To resume a done or crashed session: To manually recycle when ready:

State file (~/.claude/orchestrator-state.json)

Never committed to git. You maintain this file directly using jq + atomic writes (.tmp → mv). Top-level optional fields: repo — GitHub owner/repo for CI/thread checks. Auto-derived from git remote if omitted. discord_webhook — Discord webhook URL for completion notifications. Also reads DISCORD_WEBHOOK_URL env var. Per-agent fields:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@Significant-Gravitas · no license declared
Token usage
Heavy
Setup complexity
Manual integration
External API key
Not required
Operating systems
macOS · Windows · Docker
Runtime requirements
Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview orchestrate.preview
# /pr-test result evaluation

tmux send-keys -t SESSION:WIN "PARTIAL result on /pr-test — S5 (Apply button) never appeared. The AI must output JSON action blocks for the Apply button to render. Fix this before re-running /pr-test."
   sleep 0.3
   tmux send-keys -t SESSION:WIN Enter

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.