Oh My Codex

v0.17.2 Security

This release includes 1 security fix for security teams reviewing exposed deployments.

Published 21d Developer Productivity

View tool

✓ No known CVEs patched

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

This release patches 1 known CVE

ReleasePort's take

Light signal

editorial:auto 13d

v0.17.2 bounds Hermes bridge stdin to prevent arbitrary commands from compromising coordinators. Also restores structured answer leader-pane resume and safely handles invalid return targets.

Why it matters: Prevents Hermes bridge stdin-based coordinator compromise. Verify structured answer and return-target behavior in dev before production; update recommended.

Summary

AI summary

Restores leader-pane resume behavior for structured question answers and prevents Hermes bridge from gaining arbitrary terminal stdin control.

Changes in this release

Type	Severity	Summary	CVE
Security	Medium	Hermes bridge stays bounded, preventing arbitrary terminal stdin control for coordinators. Hermes bridge stays bounded, preventing arbitrary terminal stdin control for coordinators. Source: llm_adapter@2026-05-21 Confidence: high	—
Feature	Medium	Structured answers resume the leader pane again. Structured answers resume the leader pane again. Source: llm_adapter@2026-05-21 Confidence: low	—
Bugfix	Medium	Invalid or missing return targets are skipped safely while answer state persists. Invalid or missing return targets are skipped safely while answer state persists. Source: llm_adapter@2026-05-21 Confidence: low	—

Full changelog

oh-my-codex v0.17.2

0.17.2 is a hotfix release after 0.17.1 that restores omx question leader-pane resume behavior for structured question answers, including Hermes/MCP answer submission.

Highlights

Structured answers resume the leader pane again — answered question records with persisted renderer return_target metadata now send the bounded [omx question answered] notice through the existing safe tmux-send-keys path.
Hermes bridge stays bounded — Hermes submits structured answers to question records and OMX uses record-authorized return metadata when present; coordinators do not gain arbitrary terminal stdin control.

Fixes / compatibility

Local tmux question UI answers and Hermes/MCP structured submissions share the same answer-side resume behavior.
Invalid or missing return targets are skipped safely while answer state still persists.
Regression tests cover the state/UI/Hermes answer paths.

Validation

npm run build
env -u OMX_STATE_ROOT -u OMX_ROOT -u OMX_SESSION_ID -u CODEX_SESSION_ID -u SESSION_ID node --test dist/question/__tests__/state.test.js dist/question/__tests__/ui.test.js dist/mcp/__tests__/hermes-bridge.test.js dist/question/__tests__/renderer.test.js
npm run check:no-unused
npx biome lint src/question src/mcp/hermes-bridge.ts

Contributors

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

Full Changelog: v0.17.1...v0.17.2

Security Fixes

Hermes bridge now bounded — coordinators cannot gain arbitrary terminal stdin control when submitting structured answers

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.