Maintain & Repair
mb-update
Last updated May 25, 2026
Supported in Codex
Inspect version state and apply Main Branch updates only after approval.
- Sense
- Decide
- Ship
- Reflect
Usage
Use mb-update as an agent route. The route should read Main Branch facts before advice, then stay inside the approval gates for the work it recommends.
mb-update
# Claude Code, when installed
/mb-update When to use it
Best for
An update route when the installed Main Branch version, runtime compatibility, or migration state needs review.
Use when
- The operator asks to update Main Branch.
- Status suggests an update or migration.
- Runtime behavior may differ from the expected version.
Route workflow
- Check installed and available versions.
- Name compatibility and migration notes.
- Recommend whether update is required or optional.
- Ask before package changes, migrations, or generated file edits.
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.
mb update --check --json
mb status --json --peek Command contract
Reads
- installed version
- available version
- runtime compatibility
- migration notes
Writes
- updated package or bundle after approval
Approval gates
- package update
- migration
- generated file changes
Expected output
Return
- Version state.
- Update recommendation.
- Approval-gated apply plan.
Do not
- Do not update packages without approval.
- Do not skip migration notes.
- Do not treat an update check as a successful update.
Example response
An update is available. Review the change notes, confirm the target runtime, then apply only after approval.