How it works
From the contract to the line of code, and back to the client.
One chain of records runs from what the client signed to what landed on main. Your agents walk it step by step, and your client reads the parts you share.
The chain
Client seesYour team only- Client seesContractThe statement of work the client signed, with its milestones and price.
- Client seesMilestonesComingWhat gets delivered and when. Your clients will accept each one (Coming); today your team records each acceptance, naming who approved it.
- Client seesStreams on the roadmapEach milestone is delivered by a stream of work, shared on the roadmap.
- Your team onlyCards and plansA stream breaks into cards. Each card is built from a reviewed plan that cites the decisions it rests on.
- Your team onlyPull requests to mainAgents build tests first, and the work lands on main when it is green.
- Client seesReports, then invoicesA report is drafted from the records and you publish it. An invoice follows the accepted milestone.
When scope changes, a change request amends the contract. The milestones move with it, and the client sees exactly what changed and why.
AI-native
Agents follow the process, not guess at it.
Agile tooling was built for people in meetings. Bolting an MCP onto it hands your agents that same ceremony. onMain is shaped around how agents actually work, and three loops guide each step.
Loop 1Product LoopAn idea becomes a stream with a written brief: what it is, what done means, what it assumes.
Loop 2Planning LoopEach card gets a plan that is checked against the code and challenged before anyone builds it.
Loop 3Engineering LoopTests first, a review at each phase, and the work lands on main with its records updated.
| The question | Bolted on | onMain |
|---|---|---|
| What does the agent do next? | Reads a ticket and guesses | Claims a card and reads its plan |
| Who checks the approach? | Whoever reviews the pull request, afterwards | The plan is challenged before it is built |
| Do the records match the code? | They drift until someone tidies them | Updated in the same step as the code |
| How does the client hear about it? | Someone writes it up | A report drafted from the records, which you publish |
Built for agents
An MCP your agents were meant to use.
Your agents connect to onMain over its MCP. Every tool maps to a step in the loops, so an agent never has to work out your process from a board built for people.
› claim_next_card card 212 claimed · in progress › read_plan card=212 Plan 31 · executing · phase 2 of 3 › record_pull_request recorded · lands on main when green › add_status_report draft saved · you publish, the client reads
One engine