Your agents need a director.
troupe runs your development process with agents and people in named roles. Work branches and loops, decisions go to whoever owns them, and every decision records who made it.
The problem
Agents work alone, in a line, and ask one person everything.
- One agent, one lineWork runs in a single thread, step after step.
- One bottleneckEvery question goes to “the human”.
- No homeworkQuestions arrive with no research done.
- No recordNobody can say who decided what.
How the show runs
A season, not a single show.
Your process runs again and again. Each run gets better.
↻ and again, every showing
The cast
Your process, as a cast list.
Every role in your process, and who holds it: a person or an agent. Each decision goes to whoever owns it.
- Product ownerAlex
- EngineerBuild agent
- ReviewerReview agent
- QASam
Release: decided by the product owner
Example cast
Principles
What we’re building.
The ideas troupe is built on.
Local-first, everything in your project
Config, history and decisions live in git, on your machine. No hosted service required.
Work that branches
Tasks fork, join, swarm and loop, instead of one agent working in a line.
Built for teams of agents and people
People hold roles the same way agents do, so each question goes to the person who owns it.
Escalation that does its homework
Before an agent asks, it checks the issues, reads the docs and researches the standard, then brings a decision brief.
Lineage for every decision
Every decision records who made it, human or agent, what it was based on, who approved it, and where its results went.
Bring your own agent
Agents are pluggable: use ours, or bring your own.