Product01How it works02Agents03Security04Brand05Early access
AI CTOSteers Claude Code, Codex, OpenCode and 12 more

Plan it.Build it.You ship it.

Mamba is the AI CTO for the coding agents you already use. Chief plans the work, specialists build it in their own worktrees, and nothing merges until you say so.

The Mamba board with tasks across Needs you, Running, Review and DoneThe Mamba board with tasks across Needs you, Running, Review and Done

Works with
what you have

Claude CodeCodexOpenCodeCursorAmpGemini CLIKilo CodeGitHub CopilotGooseAuggieKiro CLIOpenHandsMistral VibeFactory Droidfx

01Why Mamba

Your agents can write code. Somebody still has to plan the work, route it to the right specialist, check what came back and decide what ships. Mamba is that somebody, and it never decides without you.

A day with Mamba

01 / Today

Know where to look.

Needs you first, then running, then review. Colour only ever means state, so the thing waiting on you is the thing you see.

  • Needs you collects every prompt and question in one place.
  • Running shows each agent's turn as it reports it.
The Today screen with tasks that need a decision, running agents and reviewsThe Today screen with tasks that need a decision, running agents and reviews
02 / Permissions

Every prompt comes to you.

When an agent wants to run something your rules do not cover, it waits. You see the exact command and where it runs, then allow it once or deny it.

  • Answer anywhere: the task, a push on your phone, or the CLI.
  • Steer mid-turn or queue a message for the next one.
A task waiting on a permission prompt with Allow once and DenyA task waiting on a permission prompt with Allow once and Deny
03 / Review

Nothing merges until you say so.

Every turn is a checkpoint. A task lands in Review with its diff, your test run and, if you want one, a second agent's review.

  • Ready to merge means every check that ran passed.
  • Merge locally or open a PR. Closing is always your call.
A task in review with its diff, checks and merge controlsA task in review with its diff, checks and merge controls
04 / Chief

Say the outcome. Chief does the org chart.

Chief plans across your projects, routes each step to the right agent, follows what they report and brings back only the decisions that are yours.

  • The packet: at most five decisions each morning, with evidence.
  • Your mandate is read on every turn.
A Chief conversation planning work across projectsA Chief conversation planning work across projects
15coding agents steered through their own protocols
1git worktree per task, on its own branch
$0billed for model use. Agents run on your accounts.
6loops, from a single turn to your whole portfolio

02Everywhere

Your Mac, your phone, your terminal.

The board runs on your machine and installs on your phone's Home Screen. The Mac app is native. The CLI does everything the board does.

The plans screen in the Mamba Mac appThe plans screen in the Mamba Mac app
Mamba on a phone, showing the tasks that need youMamba on a phone, showing the tasks that need you
~/storefront
$ mamba status
needs you Fix VAT rounding at checkout
running Rate limit the /v1/ask route
review Split the billing boundary
$ mamba allow 7f3a
Allowed once: bun run db:migrate
$

03And more

The rest of the operating system.

One worktree per task

Each task runs on its own branch in its own git worktree. Agents never touch your checkout.

Notifications that matter

Push for what needs you and nothing else. Approve from the lock screen.

GitHub and GitLab

Open PRs, feed CI logs and review comments back to the agent, record merges.

Scheduled workflows

Nightly test health, dependency audits and docs drift, each a readable task.

Limits, as reported

Each agent's usage window and reset time, straight from the agent.

Every session, searchable

Transcripts and checkpoints kept, compared and restorable.

Acceptance criteria

Criteria tick only when the test behind them passes.

Agent access

Your other AI agents can create and steer tasks over MCP or REST.

Extensions

A new agent is one driver file. A new policy is one rule file.

04Principles

A meta-harness,not an agent.

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

Native protocols

One driver per agent. No terminal scraping when a structured protocol exists.

The log is the truth

Every change is an event. Every screen can be rebuilt from history.

Only what was reported

Status comes from the agent and git, never from a guess.

Code travels by git

Anything the next step needs is on the task branch.