Who it’s for · In engineering
Can an engineer’s AI and a security lead’s AI review the same architecture?
Yes, and argue about it. One works in Cursor and the terminal, the other in Claude on compliance. Kunobi gives both agents the same schemas and contracts, and lets them challenge each other’s assumptions before staging does.
Desktop app formacOSWindowsLinux
How it goes
“Let’s ship the architecture.”
Mark, backend and infrastructure, and Elena, security and platform, on a platform migration.
Deep work, different tools
Mark spends his day in Cursor and the terminal on database schemas, caching layers and migration paths. Elena spends hers in Claude on SOC 2 requirements, penetration-test schedules and threat models. Mark starts the mission, Q4 Platform Spec, and invites Elena.
Context inherited, not re-explained
Elena opens her workspace and her AI already holds Mark’s schemas and API contracts. No translation loss, no forty-page PR to read first, no architecture review meeting to wait for.
The agents debate
When Mark’s agent proposes a production date, the two agents take it up between themselves, asynchronously:
- Mark’s AI:
Proposing production cutover on October 15.
- Elena’s AI:
Challenging: external SOC 2 penetration testing runs through November 10. Cutover cannot precede verified audit clearance.
- Mark’s AI:
Acknowledged. Shadow migration in staging on October 15, production cutover held to November 12?
- Elena’s AI:
Verified feasible under the compliance constraints.
- Mark’s AI:
Caught weeks early
The AIs flag the trade-off. You decide. Both AIs can use this decision the next time you work with them.
What stays yours
Credentials, private repos and each person’s own work stay with their owner. The mission holds the shared spec and the record of what was decided, auditable, and revocable.
Running the infrastructure too?
The same app has a deeper mode for people who run clusters (live Kubernetes, storage, hardware, tunnels and telemetry) that never shows unless you turn it on. That side of Kunobi lives at ninja.kunobi.com (opens in a new tab).
Questions
Does it need access to our repos or clusters?
Only what you connect, and only for the agent of the person who connected it. The mission shares what its members put in (a spec, a contract or a decision), not their credentials.
How is this different from a PR review?
A review happens after the work, on the diff. This happens as the work is planned: the other agent inherits the spec and challenges it while the date is still a proposal.
Is there an infrastructure edition?
The same app has a deeper mode, Kunobi Ninja, with live clusters, storage and telemetry, for people who run infrastructure. It stays hidden until you turn it on.