Skip to content
BMO

Review before merge

Teams that require human review before merge should wire BMO into proposal and gate surfaces instead of letting edits land silently.

Section titled “Recommended flow”
flowchart LR
  agent["Agent produces change"]
  proposal["Patch proposal queue"]
  human["Human review in TUI/CLI"]
  gate["Quality gate optional"]
  merge["Apply / git commit"]
  agent --> proposal --> human --> gate --> merge

Surfaces

Section titled “Surfaces”
StepFeature
Queue agent diffsPatch proposals
Inspect diffTUI proposal viewer, bmo workstream proposals
Automated checkQuality gates
Git safety netAuto checkpoint, Git workflows

Policy alignment

Section titled “Policy alignment”
  • Keep approval gates on for interactive sessions.
  • In CI, prefer proposals or explicit patch application over blind --auto-approve-tools.
  • Use Session modes review-oriented modes when available in your operating pack.

When quality gates help

Section titled “When quality gates help”

Quality gates run a judge pass on drafts when configured — useful for high-risk repos. They complement human review; they do not replace it. See Conversation quality for the full quality stack.

Section titled “Related”