Maintain & Repair

mb-setup

Last updated May 25, 2026

Supported in Codex

Initialize Main Branch after read-only preflight checks and explicit operator consent.

mb-setup spans Sense, Ship

Sense
Decide
Ship
Reflect

Usage

Use mb-setup as an agent route. The route should read Main Branch facts before advice, then stay inside the approval gates for the work it recommends.

bash

mb-setup

# Claude Code, when installed
/mb-setup

When to use it

Best for

A setup route when a folder should become the owned business-memory repo.

Use when

The operator asks to install, initialize, or onboard Main Branch.
The target folder, runtime, or GitHub backup posture needs explanation.
Setup would write files and needs consent.

Route workflow

Check the installed CLI and setup help.
Explain the target folder and what setup will write.
Ask for approval before initialization.
Run status after setup to confirm the fact layer.

Safe fact commands

Run only the read-only facts needed for the route before recommending next work. Approval-gated commands belong in the plan, not the first move.

bash

mb --version
mb onboard --help
mb status --json --peek

Command contract

Reads

target folder
runtime availability
git and GitHub posture when relevant

Writes

Main Branch folder structure
starter memory files after approval

Approval gates

initialization writes
GitHub backup setup
provider configuration

Expected output

Return

Preflight result.
Setup plan with target folder.
Post-setup status check.

Do not

Do not initialize the wrong folder.
Do not write files before approval.
Do not configure backup or providers without consent.

Example response

agent

Preflight passed. With approval, initialize the business repo, then run mb status to confirm the fact layer.