Bitter Frontier What 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.

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