Release Notes

The changelog is the short version. Use this page when you need the practical details behind recent releases: what changed, whether you need to migrate, and what was verified before release.

v0.17.0 — Hermes MCP, $design, plugin discovery, and adversarial UltraQA

Upstream release notes · CHANGELOG entry · Readiness evidence

User impact

• Hermes MCP adds a bounded coordination bridge for session listing/status, audited follow-up dispatch, safe artifact reads, session starts, log tails, and final coordination reports without exposing tmux scrollback or raw private state.
• $design becomes the canonical workflow for creating or refreshing repo-local DESIGN.md; the older frontend-ui-ux shortcut remains only for compatibility.
• Plugin-mode setup now exposes OMX skills through local Codex plugin marketplace discovery, verifies the plugin cache, and publishes plugin-scoped MCP metadata including Hermes.
• $ultraqa now requires adversarial dynamic e2e coverage: hostile scenario modeling, prompt-injection attempts, interrupt/cancel/resume cases, stale state checks, useful temporary harnesses, and explicit cleanup evidence.
• Runtime hardening improves Windows native hooks, tmux continuation ownership, startup shell isolation, committed project-memory loading, and Ultragoal task-scoped goal reconciliation.

Compatibility

No normal migration is required. Existing $frontend-ui-ux prompts still route as compatibility shortcuts, but new durable product/UI/frontend/design-system decisions should start with $design. If plugin-mode skill discovery or Hermes MCP metadata looks stale after upgrade, run omx setup and omx doctor.

Verification noted upstream

The upstream readiness record marks local release preparation as passing while external publication was still pending at that snapshot. Local gates included previous-tag ancestry, version metadata sync, build/lint/no-unused, targeted MCP/Hermes state-path tests, Cargo tests, a final full release gate, $code-review approval, release body generation, and npm pack --dry-run. The targeted Node release suite passed 467 tests, Rust tests passed, the generated release body SHA-256 was e1fdf5bd7961ee7d1370046114301f2939007828d91e9fd361fdb6a7515cae7e, and the dry-run package shasum was 64b6cb807fab9ddb6213dde72472df137c8e81db.

v0.16.4 — Approved handoffs and runtime completion hardening

Upstream release notes · CHANGELOG entry · Readiness evidence

User impact

• Ralph, Team, and planning handoffs keep approved context references, ready context-pack role refs, private context-pack entry metadata, canonical approved PRD aliases, multiline launch hints, visible hint lineage, and Team scale-up handoffs intact.
• Codex hook setup stays compatible across CLI releases by preferring [features].hooks = true when available, retaining the legacy codex_hooks fallback, deduping stale aliases, keeping hooks active after clear resets, and detecting stale PostCompact wiring.
• Runtime ownership and visibility are safer: notify dispatch avoids recursive wrapper chains, setup avoids duplicate hook state, plugin-mode skill discovery and MCP cleanup are hardened, boxed Team state-root precedence is corrected, and HUD visualization stays rooted in runtime authority.
• Completion gates are harder to overclaim: Ralph completion requires audit evidence, and Ultragoal final completion requires cleanup/review proof before accepting done state.

Compatibility

No migration is required for normal users. Older Codex installs remain supported through the legacy codex_hooks fallback path, while current generated configuration prefers [features].hooks = true when the installed CLI advertises it. If local hooks look stale after a Codex CLI upgrade or reset, run omx setup and omx doctor.

Verification noted upstream

The upstream readiness record shows green dev/main CI, a successful tag release workflow, GitHub release assets, npm 0.16.4, npm run build, npm run lint, npm run check:no-unused, targeted release tests, cargo test, npm pack --dry-run, release body generation, and git diff --check. No shipped-tag gaps are listed.

v0.14.4 — Frontier default moves to GPT-5.5

Upstream release notes · CHANGELOG entry

User impact

• Fresh/default frontier-managed paths now prefer gpt-5.5.
• Runtime defaults, Codex agent defaults, and omx explore fallback behavior resolve the frontier lane to gpt-5.5.
• Generated setup config and executor worker launch defaults use medium reasoning instead of high.
• Standard/mini and spark lanes remain pinned: gpt-5.4-mini and gpt-5.3-codex-spark keep their exact semantics.

Compatibility

No migration is required. Existing explicit gpt-5.4-mini and gpt-5.3-codex-spark overrides keep working as before.

Verification noted upstream

The upstream release notes record npm run build, targeted model/default Node suites, lint/no-unused checks, and Cargo workspace tests, with full evidence in docs/qa/release-readiness-0.14.4.md.

v0.14.3 — Operator reliability hardening

Upstream release notes · CHANGELOG entry

User impact

• omx question better preserves the invoking leader pane across tool-launched prompts, prompt reseeding, renderer paths, and metadata races.
• Deep-interview reconciles answered question records before re-prompting and adds summary gates for oversized clarification flows.
• Project-local setup is honored during explore launches by resolving project-local CODEX_HOME from persisted setup scope.
• Setup refresh handles multiline root TOML assignments more safely.
• HUD reconciliation targets the emitting tmux window instead of drifting across windows.
• Team/runtime surfaces add canonical supervisor events and native Windows psmux pane bootstrap hardening.

Compatibility

No migration is required. omx question intentionally fails closed when there is no visible/returnable tmux pane.

Verification noted upstream

The upstream notes record npm test with 3910 passing tests, no-unused checks, Cargo workspace tests, lint, build, and targeted changed-path suites.

v0.14.2 — Fast-follow question/deep-interview fixes

Upstream release notes · CHANGELOG entry

User impact

• omx question fails visibly outside attached tmux instead of creating an unseen detached renderer.
• Duplicate MCP stdio siblings can self-exit after a safe post-traffic idle window.
• Deep-interview state clearing is safer and failed question launches clear pending obligations.
• Korean ulw keyboard drift (ㅕㅣㅈ) normalizes to the ultrawork shorthand before activation.
• Question answer injection reuses shared tmux submit semantics.
• Deep-interview guidance now tells agents to wait for background omx question terminals and read JSON answers before continuing.
• TypeScript and Biome baselines were refreshed.

Remaining risk noted upstream

The upstream notes call out real tmux/reused-session behavior as the highest-value post-release observation surface.

v0.14.1 — Interactive orchestration reliability follow-through

Upstream release notes · CHANGELOG entry

User impact

• Pending deep-interview question obligations keep Stop blocked until the question is resolved.
• Question panes are more resilient across tmux environments and fail closed when startup cannot be made reliable.
• omx update can refresh setup state even when the installed version is already current.
• Lifecycle compatibility code reuses the shared runtime run-outcome contract.
• Code-review guidance was strengthened and lightweight fallback lanes were kept lean.

Remaining risk noted upstream

Real multi-session tmux/operator behavior around omx question, Stop gating, and upgraded-install setup refresh remains the most valuable observation surface.

v0.14.0 — Structured questions and explicit runtime outcomes

Upstream release notes · CHANGELOG entry

User impact

• omx question becomes the owned interactive question surface with JSON input, UI rendering, persistent question state, and structured answers.
• Deep-interview rounds create and satisfy question obligations instead of relying on ad-hoc plain-text fallback.
• Autoresearch becomes skill-first and validator-gated; direct omx autoresearch is hard-deprecated.
• PASS/LIGHT/HEAVY advisory triage hints can steer non-keyword prompts without implicitly activating a workflow.
• Runtime run outcomes are normalized so Stop/continuation behavior stays consistent.
• Specialist routing guidance is narrower and clearer.

Verification noted upstream

The upstream notes record build, lint, TypeScript, affected interactive/runtime suites, catalog checks, packed-install smoke testing, and pack dry-run verification.

Legacy docs signal

The older oh-my-codex.dev/docs.html page is useful as a historical signal because it collected release-style operational topics in one long page: team worktrees, mixed Codex/Claude/Gemini workers, notifications, recommended workflows, and team CLI API examples. This docs site now splits those topics into focused pages under Skills, Tools, Integrations, and Reference, while this page keeps the release-note thread explicit.