Multi-repo autonomous dev team loop
The fleet pattern: run agent loops across multiple repos in parallel, each isolated in its own git worktree, with a pluggable vendor layer spanning Claude Code, Codex, Cursor CLI, and OpenCode.
Implementation note
When to use: you are past single-repo loops and want agent capacity across a portfolio — several services or projects receiving loop attention in parallel, the fleet pattern. How it works: register your repos with the runner, then launch loops across them in parallel, each loop isolated in its own git worktree so concurrent runs never trample each other's working state. A pluggable vendor layer means each loop can run on Claude Code, Codex, Cursor CLI, or OpenCode, and the loop shape covers plan, review, fix, and ship. Safety: worktree isolation is the core rail — parallel agents share nothing at the filesystem level, so one loop's mess cannot corrupt another's checkout. The risk that scales with the fleet is spend and review load: five parallel loops produce five streams of diffs needing human eyes. Start with one or two repos and per-loop caps before going wide.
More automation loops
Run workflows with dynamic sub-agents
Split a task into packets, run sub-agents in parallel, synthesize results, and verify completion.
Run agent turns until goal met
Agent executes repeated turns toward a condition, with a lightweight evaluator checking progress after each turn until the goal is reached.
Run agent until goal met
Queue agent turns with goal context until your objective is achieved, treating the goal as untrusted data.