Skip to content
BMO

BMO

Open-source agent-native coding system for the terminal. Parallel agents with workspace claims, first-party docker and ssh sandbox backends, durable evidence, and approval-gated tools.
Get Started Explore Workflow Map View on GitHub

BMO fixes a failing test in the terminal

Provenance: OUTCOME-VIGNETTE — VHS-scripted terminal; illustrates fix flow, not Bubble Tea capture. See Proof & claims in the repo.

Multi-agent coordination proof (Experimental) →

New to BMO?

Section titled “New to BMO?”

Read the Your First 10 Minutes guide. It walks you from installation through your first edit in a single short page. The rest of this book is reference material organized by topic.

Contributing to BMO itself? Start with the CONTRIBUTING.md first-contribution walkthrough, then return to this book when you need product or feature reference.

See About This Book for how the guide and reference layers are organized.

Start Here

Section titled “Start Here”
  • Overview explains what BMO is, who it is for, and how the docs are organized.
  • Quickstart gets you into your first real session fast.
  • How BMO thinks and acts gives the core mental model for shared workspace, tools, workflows, and bounded adaptation.
  • Workflow map shows how a request can turn into tool use, staged plans, background automation, mesh delegation, and observability.
  • How to discover what BMO can do covers the in-product discovery surfaces so you do not have to memorize commands first.

What Makes BMO Different

Section titled “What Makes BMO Different”

Run agents in `local`, `docker`, or `ssh` sandboxes

Route every tool call through options.sandbox.backend in bmo.toml to execute on the host, in a container, or on a remote machine — without changing your prompt. Verify with bmo run --sandbox docker "echo hi".

Share one session state with the agent

Agents read and write the same sessions, file history, message log, and data directory you do. Inspect any run with bmo session show after the fact — no opaque external thread.

Approve risky tools before they run

Edits, shell commands matching the blocklist, and writes to sensitive paths (.ssh/, .env, …) wait for confirmation by default. Widen the policy with --auto-approve-tools only when you opt in.

Drive BMO from TUI, CLI, MCP, ACP, or A2A

The same agent core is reachable through bmo (TUI), bmo run / bmo autopilot (CLI), bmo serve-mcp (editor integration), the ACP endpoint (agent-client protocol consumers), and A2A (peer agents). Pick the surface; the tools and policy stay the same.

Learn by Outcome

Section titled “Learn by Outcome”
I want to…Start here
Install BMO and run the first sessionInstallation and Quickstart
Understand how the system is structuredHow BMO thinks and acts
See how everyday requests branch into workflowsWorkflow map
Learn practical prompts and delivery patternsCommon Workflows
Choose the right feature without reading every pageAbout This Book and How to discover what BMO can do
Inspect the tool surface available to the agentTools Reference
Understand configuration and operating modesConfiguration and Operating mode parity
Work across multiple agents or remote peersMulti-Agent Workflows, Agent Mesh, and A2A Protocol
Review agent-produced code before it landsPatch Proposals and Quality Gates
Run BMO in CI, scripts, or long-lived background modeAutomation & Headless
Diagnose a run from durable evidenceAgent Debugger, TUI Runtime Signals, and Session Observability Parity