Bring your work.
Give the loop a real test.
We’re recruiting a first group of 10 builders who already use coding agents, plus a small set of Grow design partners. Try Orchestro on one real project and help us find where setup, prioritization or verification falls short.
What you get
- Access to the private Orchestro repository and setup docs.
- A workflow for mapping capabilities, investigating problems and recording what happened.
- Direct feedback on setup blockers. Start asynchronously; a call is optional.
What makes a good first project
Builders bring an app they maintain, a signed-in coding CLI, and one test, log or metric the system can read. Grow partners bring one campaign or experiment with a metric they already read. Start in observation mode and choose the boundaries before allowing repairs.
Codex, Claude Code and Grok support repair workers. Muse Spark supports mapping and Advisor review. Check agent compatibility.
Your first week
- Connect: map one capability and inspect the first checkpoint.
- Observe: check whether the next proposed job is actually useful.
- Report: share what failed, what needed your intervention and whether you would run it again.
This is a private preview. Access is reviewed, not granted automatically. Your coding-agent subscription and its usage limits still apply.
Inspect the 12-signal exampleRequest access
Prefer email? Send your project and GitHub handle.