Product01How it works02Agents03Security04Brand05Early access

How it worksArchitecture

A meta-harness,not an agent.

Mamba does not write your code. It steers the agents that do, through their own protocols, records everything they report, and keeps every change on its own branch until you decide.

The systemThree layers

Surfaces, a runner, and your agents.

One TypeScript implementation runs everywhere. The core is runtime-neutral, so the same rules run on your laptop, in the browser and in a cloud hub.

Where you steer

  • BoardBrowser, Home Screen app
  • Mac appNative window, tray and notifications
  • CLIEvery action, --json output
  • Other agentsMCP and REST with their own keys

What keeps the truth

  • RunnerHono on Bun, on your machine
  • Event logEvery change is a domain event. State is a projection.
  • PolicyAutomation rules run where the log is authoritative
  • Optional cloud hubFor your phone and remote runners

Who does the work

  • DriversOne per agent, native protocol
  • Your agentsClaude Code, Codex, OpenCode, ACP agents
  • WorktreesOne per task, on its own branch
  • GitCheckpoints, merges and PRs

Life of a taskEight steps

What happens after you press start.

  1. You write a task

    Title, brief, and optional acceptance criteria. Or Chief writes it from your outcome.

  2. A runner claims it

    The runner on your machine creates a git worktree on a branch named for the task.

  3. The agent starts natively

    Mamba launches the agent's own program and speaks its protocol: SDK, JSON-RPC, HTTP or ACP.

  4. Events stream to the log

    Messages, tool calls, prompts and usage arrive as events. The board is a projection of that log.

  5. Prompts come to you

    Anything your rules do not cover waits on you: on the task, in a push, or in the CLI.

  6. Each turn is a checkpoint

    The worktree is committed after every turn, so any point can be compared or restored.

  7. Checks run

    Your tests, browser checks and an optional reviewer agent. Results are recorded, never summarised into a claim.

  8. You decide

    Merge locally, open a PR, ask for changes or close. The agent never decides that it is done.

ChiefSix loops

From one turn to the whole portfolio.

Chief works in nested loops. Each one asks a single question, acts on a signal, and has a hard stop that hands the decision back to you.

LoopQuestionSignalActionStop
TurnIs this step right?Tool result, diffContinue the agentBudget, limit, blocked
CardIs this outcome done?Check, review, observed behaviourFix, review, shipThree rounds, then you
LaneIs this project moving?Open items, queue ageDelegate, unblock, reorderStall, collision, you
PortfolioWhat matters now?Decisions waiting, risk, valuePrioritise, delegate, reportThe owner packet
DiscoveryWhat are we missing?Issues, CI, correctionsPropose work with evidenceProposal cap, no new evidence
LearningWhat should change?Outcomes, cost, correctionsUpdate a rule, skill or routineNo improvement, revert

Design rules

Four rules we do not bend.

The architecture notes ship with the source in docs/ARCHITECTURE.md.

Rule 01

Steer native protocols

A new agent is one driver implementing one interface. No terminal scraping when a structured protocol exists.

Rule 02

The log is the truth

State changes are events. Nothing edits the projection directly, so every screen can be rebuilt from history.

Rule 03

Never claim what was not reported

Transcripts, limits and checkpoints are facts from the agent and git. Mamba does not judge completion.

Rule 04

Code travels by git

Anything the next step needs is on the task branch or in the handoff packet.