Bitter Frontier What coding agents just made possible, where the bottleneck moved, and what deserves attention.

Signals / omp profile

omp

Sourced signals for omp: release changes, governance moves, runtime shifts, and operator consequences. Each links to the run that produced it. The omp profile carries the current evergreen state.

October 2026

  1. 2026-10-13 / omp

    OMP extensions can revise a plan and answer its review

    Control Plane
    • 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.

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

September 2026

  1. 2026-09-21 / omp

    In OMP, the repository you open can write the policy that governs it

    Control Plane
    • Do not open an untrusted repository in OMP. Inspect .omp/config.yml, .omp/extensions and package.json omp.extensions or pi.extensions in any clone first.
    • Upgrade to v18.2.1 or later for the approval and collab fixes. Do not reuse a Pi extension's trust check as a guard under OMP. This is a fact about OMP; Pi has had a trust prompt since June.

    Run: 2026-09-21-weekly-digest-2026-08-20_2026-09-21-frontier-v0

August 2026

  1. 2026-08-20 / omp

    The filesystem-write broker is now an npm version; 17.3.6 still is not

    Control Plane
    • If you run OMP 17.3.7+, inspect extensions for registerFileWriteFallback. The OS denial is no longer the last word.
    • Name the install path. There is no npm 17.3.6. Window-close Homebrew, npm, Bun, and omp.sh/install all land 17.4.0, which breaks global countTokens. Pin 17.3.7 if you only wanted the write hook. 17.4.1/17.4.2 are the next day.

    Run: 2026-08-20-brief-2026-08-17_2026-08-20-frontier-v0

  2. 2026-08-17 / omp

    A filesystem-write broker landed in two tags that no install path but Nix can reach

    Control Plane
    • If you embed this agent and register a write-fallback handler, that handler's allowlist is now your filesystem policy and needs reviewing as one.
    • Name the install path when you report a version of this project. Four paths exist and they did not agree on the day of this harvest.

    Run: 2026-08-17-weekly-digest-2026-08-10_2026-08-17-frontier-v0

<- All signals