Balladeer is a multiplayer harness for teams building with coding agents. It remembers how your product should behave, brings that context into their work, and helps catch regressions with agentic code review and deterministic checks.
Collaborate with your team, straight from your agent
When you plan a change, your agent offers to record important commitments as a promise. Say yes and the recorded promise is available to your teammates and their agents with full context.
DDana’s conversation
Quoted prices stay valid for 30 days.
Saved as a promise
MMaya
Claude Code session
Updating pricing
Promise received
LLeon
Codex session
Rebuilding checkout
Promise received
From the plan to the next change.
Plan · relevant context
Build with the promise in mind.
Your agent receives relevant promises before making a change, so it can spot conflicts before they become code.
Agent context
Keep existing quotes valid for 30 days.
Push · agentic code review
Find what the change breaks.
An independent agent checks affected agreed promises. A reproduced break gives your coding agent something concrete to fix.
Before$1,200Pass
→
After$1,450Fail
Future changes · deterministic checks
Make the fix last.
Keep the reproduction as a regression test. Your suite and CI check that behavior as the product changes.
quote_price_stays_fixed()
Old rate → $1,200✓
New rate → $1,200✓
Don't change your style.
Balladeer works naturally. You don't have to do anything differently once it's installed. Keep working in Claude Code or Codex just like you normally would!
Your agent will naturally offer to track promises when you start working on new features.
3
Push your next change.
Agentic review runs automatically in a connected repository.
Get started in minutes.
$20 / month
14-day free trial
A few things worth knowing.
What makes it multiplayer?
Relevant intent can reach your teammates’ agents as well as your own, with its author and standing shown. Each change can build on what your team already knows.
What can a promise cover?
A journey, system invariant or engineering standard with clear passing and failing cases. Illustrative commitments: retries never double-charge; workspaces cannot read each other’s data; external requests have bounded timeouts.
Who decides what to preserve?
You consent before anything is recorded. Recorded intent can guide work immediately.
How do deterministic checks fit?
Regression tests run in your ordinary suite and CI. You can also qualify a sealed verifier for an agreed promise. Read about sealed verification.
What does a passing review establish?
The cases exercised passed for the selected promises. Missing evidence is a gap. An agentic pass does not grant sealed Protected status. Read about review results.
What exactly does Balladeer receive?
Balladeer doesn’t receive your code, tests, reproductions, full maps, raw logs or agent transcripts. It receives intent, ownership, repository metadata, code anchors and bounded results. Read the full data boundary.
Does it hold a push?
By default, review reports after a successful agent push. Local block mode is optional; GitHub branch rules control merges. See how hooks work.
Can we keep the tests if we leave?
Yes. They stay in your repository and keep running without Balladeer.
