Braveli
Conducted multi-agent development

Agents that argue. Evidence that settles it.

Put Claude, Codex and Gemini on the same task, in one thread, on your own Mac. A conductor routes every turn on merit — and checks it against your Git worktree and your test suite before passing it on.

macOS · Apple Silicon·First month free


The problem

One agent. One opinion. Nobody checking it.

A single agent commits to the first approach it finds, then reports what it believes it did. Neither of those is visible to you until you read the diff.

No second opinion It never disagrees with itself

One agent picks an approach and spends the rest of the task defending it. Nothing in the loop is arguing for the alternative it discarded in the first minute.

Unverified work Claims are not evidence

An agent that reports a change without touching a file is reporting a fiction, and it reads exactly like a change that happened. Nothing about the transcript tells them apart.

Cost Agents talking to agents run all night

The obvious fix — let them confer — is also how a run quietly burns a day of tokens. Bounding it is part of the design, not a setting you remember to check.

Council

Read the argument, not three scrollbacks.

Members open by stating how they would approach the task and where they think the others are wrong — they are told not to defer to each other. After every turn a conductor model reads the whole discussion and decides who speaks next.

Routed, not rotated

QA goes back to the implementer. A contested decision goes back to the architect. Fixed turn order is the fallback, not the design.

Checked against the repository

Every turn is verified against the Git worktree and the project’s own tests. A member whose change breaks the build is flagged to the conductor rather than passed on as finished work.

Survives a restart

The thread, roster and routing history are stored with the run. Close the lid; it comes back paused at the turn it reached, with full context.

You are in the thread

Anything you type joins the same discussion, so the conductor routes with your instruction in view.

Readable afterwards

The whole debate is one conversation you can scroll — who argued what, who was overruled, and why each turn went where it did. Not three terminal scrollbacks to reconcile by hand.

Turn 3Reviewer / QAClaude

Verified against the worktree: the four files are real and the suite passes. But the new test never reaches the branch it guards. Not finished.

Reviewer Implementer Conductor routed Uncovered branch; back to the author rather than on to synthesis.
Turn 4You

Agreed — cover that case before handing off again.

Every turn and every routing decision, with the reason it was made.
Your board

Import the tickets. Start an agent on one.

Connect Jira, Linear or GitHub Issues over MCP and pull in the open work assigned to you. Pick a ticket and Braveli opens a session already holding it — the title, the description, and a working branch named after it.

Read-only, by design

Braveli audits the tracker’s MCP tools and uses the read-only ones. Importing your board cannot move a ticket or comment on it.

Straight into a Council

A ticket is a task like any other, so it can go to one agent or to a full Council with an architect, an implementer and a reviewer.

Your CLIs, your subscriptions

Braveli does not resell you tokens.

Every agent runs as the CLI you already installed and already pay for. Braveli launches it, gives it a worktree and a role, and shows you what it does. Add any other command-line agent as a custom provider.

Claude Claude Code
Codex OpenAI
Gemini Google
Grok xAI
Kimi Moonshot
Custom any CLI
Local-first

There is no Braveli server.

No hosted backend, no remote execution, no telemetry carrying your work. Projects, tasks, sessions, transcripts and credentials stay on the machine that made them.

Credentials Encrypted on device

GitHub accounts and tokens are held per project in Electron safe storage. MCP OAuth tokens never leave the provider CLI’s own credential store.

Your editor Opens what you already use

VS Code, Cursor, Zed, Sublime, JetBrains or Xcode — detected from what is installed, not bundled and imposed.

Analytics Six counts, no content

Anonymous counts of things like launches and sessions started. Never your code, file names, ticket titles or prompts. Off in one click.

Pricing

Free for a month. Then $10.

One plan with everything in it, a new build every week, and a price that stays where it is. Nothing is held back to sell you later.

First month free
$10per month, after that

$10 is the price, permanently. It does not rise as features land, and it does not rise later for the people who joined first.

Cancel whenever you like. Braveli keeps running on your machine either way — your projects, sessions and history are local files, not an account.

Download Braveli
Everything included
  • Conducted Councils — merit routing, opening debate, one shared thread
  • Turns checked against the Git worktree and your own test suite
  • The full debate as one readable thread, with every routing decision
  • Compare — one task, several agents, answering independently
  • Every provider CLI, plus any command-line agent you add yourself
  • Unlimited projects, sessions, worktrees and MCP servers
  • Cost guards: turn ceilings, completion signal, manual mode
  • A new build every week, updated in place — see the changelog

Council is in alpha. Expect rough edges, and tell me about them.

Download

Put it on your Mac.

One drag into Applications. Point it at a repository you already have and start a session.

Download Braveli for Mac

macOS 12+Apple Silicon only96 MBVersion 0.1.0

Before you open it: this build is not yet notarised by Apple, so macOS will refuse it on first launch. Right-click the app and choose Open, then confirm. You only do this once. A notarised build lands shortly and this step disappears.