Every release, one page
The living record of what each OVM release adds, fixes, or catches. Newest first. Versions link to tags; incidents link to the research write-ups they produced.
v0.0.3 · in progress — introducing claudex
Claude Code as the harness, GPT-5.6 as the model. One command
(ovm claudex setup) configures a localhost-only
CLIProxyAPI sidecar, connects a Codex subscription via OAuth, and
creates an isolated Claude home so claudex sessions never mix with
normal claude history. The native /model
picker maps to gpt-5.6-sol / terra / luna; launch with
claudex, ccx, or ccxy (yolo).
A pin can freeze a known-good (Claude Code, proxy) pair when
upstream moves. Ships bundled in every install channel. Origin:
the recipe OpenAI's Codex lead
shared publicly —
unofficial integration, use at your own risk.
v0.0.2 · 2026-07-10 — catching what version checks can't
Codex 0.144.0 moved shell execution into a sidecar binary the old installer didn't ship — every install looked healthy and every tool call died. v0.0.2 installs release sidecars, and the release canary gained three layers: asset-manifest diffs, an execution probe that verifies every shipped sidecar spawns, and an authenticated tool-use probe that must round-trip a real shell command. Full story: the canary that catches what --version can't.
v0.0.1 · 2026-07-10 — first tagged OVM
The baseline: install, pin, switch, and launch Claude Code, Codex,
and Pi side-by-side; a PATH plugin system (ovm-*);
and the verification pipeline — a watcher that spots upstream
releases within minutes and a benchmark runner that measures every
one before it's promoted. v0.0.1 is also, deliberately, the
"before" half of the sidecar incident pair: it ships the pre-fix
installer so the v0.0.2 catch is reproducible from tags. What OVM
is and how the pipeline works:
the intro note.