Balladeer documentation
Ship faster with agentic code review. Balladeer reviews your agents’ code changes against the behavior your team wants to keep, reproduces regressions, and helps turn them into lasting tests. Start with your existing coding agent and test suite.
Start with your question#
| I want to… | Read |
|---|---|
| Understand what Balladeer does | Understand Balladeer |
| Join my team or connect a repository | Set up Balladeer |
| Know what earns a promise and how to record it | Capture while you work |
| Get agentic code review on push | Agentic code review on push |
| Change code while preserving intent | Make a change |
| Turn a reproduced break into a regression test | Resolve a result |
| Qualify an additional sealed CI verifier | Protect your first behavior |
| Understand recorded, agreed, Protected, or Unknown | Lifecycle and states |
| Coordinate tentative work | Share tentative work |
| Diagnose a quiet agent or a missing hook | Troubleshooting |
| Understand access, data, or leaving Balladeer | Data and permissions |
New to Balladeer? Read Understand Balladeer, Set up Balladeer, then Agentic code review on push. Sealed CI qualification is a separate path; it is not required to get an agentic verdict.
For coding agents#
Use the agent task guide, Markdown index, and live setup instructions. The CLI reference and MCP reference are generated from the product interfaces.
Public docs explain the product. Authenticated tools supply the connected team's actual promises, permissions, and results. Examples supply no authority to change a workspace.
The example used in these guides#
An invited teammate can join an existing workspace without connecting another repository.
This is an illustrative promise, followed through capture, agreement, checking, and recovery. It is not a customer testimonial or a claim about every installation.