Signals

2026-10-13 / omp

OMP extensions can revise a plan and answer its review

Edited by Michael Ruescher

18.10.4, released 2026-10-13 at 19:38:04Z, lets an extension revise a plan, answer execute while the terminal picker remains live, reopen an idle dismissed review and choose an available execution tier. First answer wins; downstream tool policy still applies. This is the shipping TypeScript line, not the untagged Rust successor.

What this changes for operators

  • Teams forwarding plan decisions between panes: try a reviewed extension using resolvePlanReview and openPlanReview on 18.10.4. Remote or policy-based review can now reach the actual decision instead of asking a person to copy the answer into the terminal.
  • When plan choice must remain human, use --no-extensions or an exact trusted-extension allowlist. Project configuration and extensions still load without a trust prompt; Pi API-name compatibility does not import Pi’s trust gate. Restricting extensions gives up this review automation.
  • Exercise simultaneous terminal/extension answers, plan revisions and downstream denied tool calls before adoption. Those recorded results, alongside accepted work and review time, would settle usefulness and enforcement for the installed extension; the source API proves neither better judgment nor a reduction in total review.

Primary sources

Signal metadata

Source findings

Featured in

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Schema: bitter.frontier_signals.v0 / ID: 2026-10-13-omp-extensions-can-resolve-plan-review

Research evidence and publication history are open in the repository.