Docs navigation mb-help

Start & Status

mb-help

Last updated May 25, 2026

Supported in Codex

List the available Main Branch routes for the current agent runtime.

mb-help spans Sense
  1. Sense
  2. Decide
  3. Ship
  4. Reflect

Usage

Use mb-help 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-help

# Claude Code, when installed
/mb-help

When to use it

Best for

A command surface inventory when the operator asks what Main Branch can do in the current runtime.

Use when

  • The operator asks for help or available commands.
  • You need to distinguish supported, planning-only, and unsupported routes.
  • Runtime parity with Claude Code is uncertain.

Route workflow

  1. Read the Codex workflow inventory.
  2. Group routes by support level.
  3. Explain the narrow job for each route.
  4. Point the operator to mb-start or the closest matching route.

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 workflow list --runtime codex --json
mb status --json --peek

Command contract

Reads

  • workflow inventory
  • Codex runtime command availability
  • status facts

Writes

  • none

Approval gates

  • none

Expected output

Return

  • Supported routes.
  • Read-only planning routes.
  • Unsupported or future surfaces with clear boundaries.

Do not

  • Do not claim Claude Code parity without runtime evidence.
  • Do not show installation internals as product-facing routes.
  • Do not hide unsupported routes if the operator asks about them.

Example response

agent
Use mb-start for orientation, mb-think for decisions, mb-site for page readiness, and mb-end to close the session.