This playbook is for engineering managers piloting BMO with a team. It
assumes evaluators already read Security and data.
| Day | Action |
|---|
| 1 | Install + Authentication on a pilot machine |
| 1 | Run Quickstart with one repo |
| 2 | Agree approval policy: interactive TUI vs CI --auto-approve-tools |
| 2 | Commit project bmo.toml or document global config baseline |
| 3 | Enable Sandbox for CI if using headless runs |
| 4 | Document provider keys: env vars or secret manager — never commit keys |
| 5 | Share Decision guide — what not to enable yet |
- Session modes — coding vs review vs planning defaults per team
(Session modes)
- Tool allowlists —
options.disabled_tools, per-agent [agents.<id>.tools]
(FAQ)
- Sensitive paths — default denylist for
.env, .ssh/; do not weaken
without review (Security posture)
- Remote surfaces — HTTP/MCP only when needed; token auth required
- BMO data dirs are per operator machine by default — not a shared team DB.
- Workspace claims reduce clobber risk within one BMO process; they are
not cross-machine file locks. See
Multi-Agent Workflows.
- For review-before-merge culture, adopt
Review before merge early.
