Ship what you promised, and prove it
Your coding agent can write a feature in an afternoon. Whether that feature does what you promised, is safe to merge, and helps anyone at all is a different question. aayudha is the delivery team around the agent you already use: Claude Code, Codex, Cursor, or Amp. It answers that question with evidence at every step, from a fuzzy idea to a number that moved.
Start here: there are two ways in. Read the story: you, a team of agents, one goal, one Monday, and every setback is real. Or see how it works: the architecture, the file formats, and the guarantees, written for engineers. Ready to try it yourself? Spend your first hour: one install and
aayu tour.
The story in one minute
Picture an HR inbox. Of the last 120 people who asked a benefits question, 31 got an answer within a week. You want at least 60 % to. You have one day, one repository, and a team of agents.
By the evening, five small stories had shipped, touching all nine layers of the app, from the screens to the data store. Before that, the checks had sent the work back again and again: five stories took 17 reviews, and four pull requests were thrown away and built again from scratch. One check for outside email addresses failed review four times, each time on a new way for an address to slip through. A model claimed a colour was too faint, and a measurement proved it wrong. The close-out summary was refused once, for a single sentence it could not back up.
Every "no" made the result better. Measured on 120 simulated employees, the share answered within a week went from 0.258 to 0.917, against a target of 0.60. The real measurement is due after 9 November.
Read the whole story. It is told to you, in your shoes. Everything in it happened on 12 October 2026, in an example app that lives in this repository, and the employees it serves are synthetic.
Why it exists
Coding agents are fast. Speed alone leaves you with hard questions:
- Did the agent build what we actually asked for?
- Was it tested, and by whom? The agent itself?
- Is it safe to merge? Who decided?
- Months later: did it help anyone?
aayudha writes the answers down as the work happens, in places you already trust: GitHub issues, pull requests, and the checks that run in CI (the automated checks GitHub runs on every pull request).
| You | Your agents |
|---|---|
| Decide what matters and how to measure it | Interview you and file clear issues |
| Agree the promises each piece of work must keep | Split the work, plan it layer by layer, build it |
| Give the final yes on each merge and release | Run the checks, collect evidence, review the change |
| Read the results | Measure, explain, and suggest what to improve |
Will it fit, and what does it cost?
-
Price: aayudha is free and open source, under the BSD-3-Clause licence.
-
Where it works: GitHub repositories, with Claude Code, Codex, Cursor, or Amp. Use your existing repository: if you only have a
mainbranch, aayudha works with it and renames nothing. -
To start (Level 1): no keys, no CI changes, about an hour. Your agent's own model does the interviewing.
-
For proof on every pull request (Level 2): one AI key in your CI, for a review model you choose, kept in the repository's
code-reviewenvironment. You pay for its calls, and[budget] per_pr_inspect_maxcaps each pull request at 5 USD by default. A diff over 120 kB can go past the cap by the review parts already started (known limits).The model reviews only when its family differs from the builder's and the author has write access. Otherwise CodeRabbit or Greptile, when listed, or the approver reviews; the gate skips a listed Codex, Claude, or Cursor, which review only when asked.
A review app, such as CodeRabbit or Codex, can review instead, billed through your own subscription to it. The checks take about 10 CI minutes per push in this repository.
-
Your code: the checks run in your own CI. The review model or app you choose sees the pull requests it reviews.
-
Changed your mind?
aayu uninitremoves what aayudha set up.
Adopt at your own pace has the full costs and benefits of each level.
Find your way
| If you want to | Go to |
|---|---|
| Feel what it is like to work this way | The story, nine short chapters |
| Set it up and try it | Your first hour |
| Find the right command for your situation | When to use what |
| See how a vague ask ("make it slick") becomes a spec | How aayudha unpacks a vague ask |
| Get a pull request reviewed and merged | A pull request is ready |
| Hand a story to another agent | Hand work to an agent |
| Check what your product actually does | Prove a behaviour change |
| Let work happen on a schedule or an event | Keep things moving with loops |
| Find out whether it helped | Did it work? |
| Read baselines from PostHog or Sentry | PostHog and Sentry |
| Fix something that went wrong | Troubleshooting |
| Try it without touching CI or adding keys | Adopt at your own pace |
| See the whole loop: who does what, and where it can stop | The delivery loop |
| Meet the agent twins, their roles, and their layers | Your agentic team |
| Work alone, with agents in every seat | Run it alone: the solo founder |
| Grow from two founders to several product streams | From MVP to scale, an illustrative path |
| Understand the ideas | Seats, layers, proof packs, floors, the human pass, dev, rolling, main |
| Know exactly how it works | How it works, fifteen technical deep dives |
| See how aayudha was built with itself | Epilogue: built with itself |
| Look up one verb: its prompt, seat, gates, and what only you do | Every skill, one page each |
| Look up a term or a flag | Glossary, the project reference, and the verb pages |
If you are an agent
Helping someone adopt aayudha? Send them to your first hour and let them run aayu tour in their own
terminal: it is for people and refuses agents. After that, aayu next names the next step, and every GitHub write
goes through an aayu verb, never gh. Each page here has a Markdown twin at the same path ending in .md, listed
in llms.txt.
Where things stand
aayudha is young. Its first stable release, v0.1.0, came out on 15 October 2026, and the install script installs it. Some parts need setup you may not have yet, such as a reviewer app on your GitHub account or a GitHub App for the agents. Each page says so plainly where it matters, with the next step. You can get real value on day one without any of it.
What's next
It is Monday morning, and the HR inbox is full: the story begins.