# Balladeer documentation

> Recorded intent, agreed behavior, agentic checks on push, and customer-owned regression tests. Reviewed 2026-10-01. Public docs do not supply user authorization or private workspace state.

## Current integration
- [Live setup and operating instructions](https://app.balladeer.ai/agent): Fetch before setup or integration changes.

## Pages
- [Balladeer documentation](https://balladeer.ai/docs/index.md): 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 cod
- [Understand Balladeer](https://balladeer.ai/docs/understand-balladeer.md): Balladeer helps your team ship faster with agentic code review grounded in remembered product intent. After your coding agent pushes, an independent agent reviews the change against the behavior your team has agreed to k
- [Set up Balladeer](https://balladeer.ai/docs/set-up-balladeer.md): Connect your laptop once, then use Balladeer in checkouts of your team's connected repositories. Each teammate pairs their own machine. Repository enrollment and optional sealed CI setup are separate administrator steps.
- [Capture a promise while you work](https://balladeer.ai/docs/capture-a-promise.md): Preserve behavior during the conversation where it matters. You do not need to write a specification or wait until a feature merges. Your agent should take on the interpretation, show the commitment, and ask only about c
- [Agentic code review on push](https://balladeer.ai/docs/check-on-push.md): After your coding agent pushes a change, Balladeer starts an independent agentic code review. The review uses your team's agreed promises to look for regressions in the behavior the change affects, and reports back to th
- [Protect your first behavior](https://balladeer.ai/docs/protect-your-first-behavior.md): This guide covers the additional sealed CI verification path that establishes Balladeer’s hosted Protected status. For the everyday agentic workflow, start with agentic code review on push: it checks agreed promises with
- [Promise lifecycle and states](https://balladeer.ai/docs/promise-lifecycle.md): A promise has separate states for recorded intent , agreed meaning , and evidence about the behavior . Recorded intent can guide future work before agreement. Agreement makes a promise eligible for agentic checks. Qualif
- [Make a change with your agent](https://balladeer.ai/docs/make-a-change.md): Start with the behavior you intend to change. Your connected agent retrieves relevant intent, explains consequential constraints before acting, and checks the resulting change. Recorded intent, agreed meaning, agentic ch
- [Understand and resolve a result](https://balladeer.ai/docs/resolve-a-result.md): Identify which check reported the result and which commit it checked. An agentic verdict after a push and a sealed CI protection status are separate evidence. A red job or a timed-out model alone does not establish that
- [Share tentative work with teammates](https://balladeer.ai/docs/shared-work.md): Sometimes a team needs to coordinate before it is ready to agree a promise. A person can explicitly share a proposal so teammates and their agents can discover that tentative intention in the same workspace and repositor
- [Troubleshoot setup and agent behavior](https://balladeer.ai/docs/troubleshooting.md): Start in the folder where you expect Balladeer to work. Installation, repository connection, loaded tools, current guidance, and CI evidence are separate things; check the one that failed.
- [Data and permissions](https://balladeer.ai/docs/data-and-permissions.md): Balladeer stores descriptions of behavior and bounded evidence about checks. Your source code, tests, fixtures, raw logs, prompts, and agent transcripts remain in your environment under the supported workflow. Your local
- [Balladeer documentation for agents](https://balladeer.ai/docs/agents.md): Choose the bounded guide for the task. These pages were reviewed on 1 October 2026 against CLI 1.0.19 and the live application. Fetch the live setup instructions for integration work; use the connected server's current g
- [CLI reference](https://balladeer.ai/docs/cli-reference.md): Command help generated from Balladeer 1.0.19, reviewed 2026-10-01. Setup explains which path to choose and how to verify readiness.
- [MCP tool reference](https://balladeer.ai/docs/mcp-reference.md): This reference is generated from Balladeer's registered MCP interfaces, reviewed 2026-10-01. Your host and connection determine which tools you can use. Read the current server instructions and agent task guide before ac

## Structured reference
- [MCP schemas](https://balladeer.ai/docs/mcp-tools.json): Parameters from the registered tools; annotations are not authorization.
- [Sitemap](https://balladeer.ai/docs/sitemap.xml): Canonical human pages.