Oh My Codex

v0.17.3 Feature

This release adds 1 notable feature for engineering teams evaluating rollout.

Published 20d Developer Productivity

View tool

✓ No known CVEs patched

Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

ReleasePort's take

Light signal

editorial:auto 13d

Codex v0.17.3 restores default team launch functionality and maintains worker MCP isolation for legacy configurations.

Why it matters: Patch to v0.17.3 immediately if Codex startup failures occur due to missing default team configuration.

Summary

AI summary

Restores default omx team launch for Codex CLI-first/plugin configs while preserving worker MCP isolation.

Changes in this release

Type	Severity	Summary	CVE
Security	Medium	Release-train includes AGENTS contract overwrite protection and metadata alignment. Release-train includes AGENTS contract overwrite protection and metadata alignment. Source: llm_adapter@2026-05-21 Confidence: high	—
Feature	Medium	`OMX_TEAM_WORKER_MCP_COMPAT` remains explicit compatibility opt-in for worker MCP disables. `OMX_TEAM_WORKER_MCP_COMPAT` remains explicit compatibility opt-in for worker MCP disables. Source: llm_adapter@2026-05-21 Confidence: low	—
Bugfix	Medium	Default Team launch works again, preventing Codex startup failure. Default Team launch works again, preventing Codex startup failure. Source: llm_adapter@2026-05-21 Confidence: high	—
Refactor	Medium	Worker MCP isolation is preserved where valid in legacy configs. Worker MCP isolation is preserved where valid in legacy configs. Source: llm_adapter@2026-05-21 Confidence: low	—
Refactor	Low	Worker MCP isolation is preserved in legacy configs that declare first-party OMX MCP servers. Worker MCP isolation is preserved in legacy configs that declare first-party OMX MCP servers. Source: granite4.1:30b@2026-05-22-audit Confidence: low	—

Full changelog

oh-my-codex v0.17.3

0.17.3 is a hotfix release after 0.17.2 that restores default omx team launch for Codex CLI-first/plugin configs while preserving the worker MCP isolation introduced in 0.17.1.

Highlights

Default Team launch works again — Codex team workers no longer synthesize mcp_servers.<omx> tables that are absent from CODEX_HOME/config.toml, avoiding Codex's invalid transport startup failure.
Worker MCP isolation is preserved where valid — legacy configs that explicitly declare first-party OMX MCP servers still get those servers disabled for Codex Team workers by default.
Release-train hardening included — AGENTS contract overwrite protection and plugin/question metadata alignment from the dev compare range are included in this patch.

Fixes / compatibility

OMX_TEAM_WORKER_MCP_COMPAT=1|true|on|compat remains the explicit compatibility opt-in that suppresses worker MCP disable overrides.
CLI-first/plugin Codex configs without first-party OMX MCP tables now reach Team worker readiness normally.
Team readiness was not loosened; failed workers still fail instead of being reported as started.

Validation

npm run build
node --test dist/team/__tests__/tmux-session.test.js
npm run check:no-unused
Default live Team smoke with bounded startup timeouts
Compatibility live Team smoke with OMX_TEAM_WORKER_MCP_COMPAT=1

Contributors

Thanks to bellman and @Yeachan-Heo for contributing to this release.

Full Changelog: v0.17.2...v0.17.3

View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track Oh My Codex

Get notified when new releases ship.

About Oh My Codex

All releases →

Related context

Related tools

Earlier breaking changes

v0.18.5 Ultragoal completion now requires independent reviewer and architect evidence before marking complete.