Try Intent-System→
ProductSupported alternative

The three-thread timer loop — the simpler alternative.

Timer loops remain fully supported. Design, implementation, and review run as three independent threads; implementation and review wake on their own schedules instead of receiving work from a fourth orchestrator. Choose this when fewer moving parts matter more than message-driven coordination.

For new setups, this site leads with the released v0.22.0 four-thread model and herdr-only as the preferred non-preview path for collocated teams. See the primary model →

Intent-System · Step 4 of 9↑ Overview
  1. 01Current Flow
  2. 02Evidence Showcase
  3. 034-Thread Orchestration
  4. 04Timer-Loop Alternative
  5. 05Intent Tree
  6. 06Unified Intents
  7. 07Human + AI Assignment
  8. 08Review & Closeout Loop
  9. 09Roadmap
Design threadhuman + LLMImplementation threadClaude /loop 5mReview threadClaude /loop 5m · separate cwdApprove → merge → re-evaluate next packet (back to ③)▸ Issue▸ submit PR▸ Decline + comment▸ updated PR①Intent treePurpose / Context / Means②Generate packetsLLM slices work from intent③Cut as GitHub Issuespacket → issue (carries why)④Implement → open PRClaude /loop 5m (impl cwd)⑥Apply review commentspush, re-request review⑤PR reviewClaude /loop 5m (review cwd)

This diagram shows the timer-loop alternative. Approve on ⑤ returns the flow to ③ so the next packet is re-evaluated against post-merge state.

Why teams still choose it

Less coordination infrastructure

  • No orchestrator thread or message bus is required. Implementation and review wake independently and inspect canonical state.
  • Implementation and review still run in separate folders, so review remains structurally independent.
  • The same issue → PR → review → repair → closeout logic applies. Only the delegation mechanism changes.
Start the alternative

Ask intent-cli for a child implementation loop

Let intent-cli inspect the repository and produce the setup instructions for your agent and scheduler. Do not combine this with orchestrator mode for the same domain/repository.

Set up a child implementation loop for <owner>/<repo>.
Ask intent-cli for the next step.

One mode per workflow

The timer-loop and four-thread models share review and closeout semantics, but they must not drive the same domain/repository at the same time. Stop the outgoing driver, verify the incoming setup, then switch.

Try Intent-System→