OMP (Oh My Pi)

OMP is on this watchlist because of a relationship rather than a feature list. Pi is already tracked here, OMP says in its README that it is a fork of Pi, and the fork has outrun the project it forked in a way no operator can resolve from a version string.

	package	version
Pi	@earendil-works/pi-coding-agent	0.84.2
OMP	@oh-my-pi/pi-coding-agent	17.3.5

Same basename, different scope, seventeen majors apart, both published in the same week. This publication spent its 2026-08-03 issue on a release line renumbered below its own predecessor. This is that failure mode from the other direction, and an adjacent-tool entry could not carry the handling rule it needs.

Where it stands, 2026-08-20

Channel. v17.3.7 gained a GitHub release and an npm publish on 2026-08-18. v17.3.6 still has neither (GitHub 404, npm missing). v17.4.0 (2026-08-20) is the window-close default on npm, Homebrew, Bun, and omp.sh/install, and it breaks the tokenizer API. v17.4.1 and v17.4.2 are 2026-08-21, outside this window. Parent "only Nix reached 17.3.6/7" ended when 17.3.7 published. Name the path when you report a version.

The write-fallback hook is installable. registerFileWriteFallback is in types.ts at the 17.3.7 tag. An OS denial is no longer the last word when an extension is loaded. Pin 17.3.7 if you want the hook without the 17.4.0 tokenizer break.

Where it stood, 2026-08-18

Channel, and it was split. Tags v17.3.6 and v17.3.7 existed with no GitHub release behind them; the newest release and the npm latest tag were both v17.3.5. Four install paths exist -- an install script piped to a shell, a Homebrew tap, a global Bun install, and a Nix flake -- and on 2026-08-18 only the flake reached the newest tag.

What was in those unreleased tags. v17.3.6 added extension hooks that let a handler service a filesystem write or delete after the native path refused it with a permission error. The mechanism is legitimate and guarded: the path is symlink-resolved, an unresolvable destination is not brokered, and the issuing session is identified. It is also a documented route by which an operating-system denial becomes an extension-mediated allow, which makes the handler's allowlist the real filesystem boundary for any host that registers one.

Approval. The always-ask prompt opened before large edit previews finished rendering, so an operator was asked to approve a diff they could not see. Fixed in v17.3.13, then reopened through a tool's wire-level alias and fixed again six days later. Two fixes for one hole is a fact about the surface area, not about carelessness.

Capability. The reason to read it closely is that it drives a language server and a live debugger rather than only editing text, which is a genuine widening of what a terminal agent operates. Hindsight memory and time-traveling rules load behaviour from stored state, which is the shape of defect this publication keeps finding elsewhere.

Fork discipline

Findings are not laundered between OMP and Pi in either direction. A behaviour observed in OMP is a fact about OMP unless the code path is shown to be shared, and an upstream Pi change is not an OMP change until it lands in a tag OMP publishes. The maintainer has stated publicly that the fork has not followed Pi since around March; that statement is reported here as something he said, and it is consistent with the divergence visible in the two version lines.

What is unresolved

• Whether tag-ahead-of-release becomes this project's normal state or was a two-day gap. 17.3.7 gained a release; 17.3.6 still has not.
• Whether the four install paths stay aligned. At window close Homebrew, npm, Bun, and the install script all resolved 17.4.0; Nix follows the git ref you pass. Observation 17.4.2 is the next day.
• Who operates the session relay, and what it retains.
• What the review gate is on a single-maintainer project carrying roughly 80,000 lines of Rust, now that the pull-request vouch requirement is lifted on a stated trial.