Skip to content

feat(codex): update placemat for Codex CLI v0.162.1 - #65

Merged
dommango merged 2 commits into
mainfrom
claude/codex-update-v0.162.1
Oct 10, 2026
Merged

dommango merged 2 commits into
mainfrom
claude/codex-update-v0.162.1

Conversation

@dommango

Copy link
Copy Markdown
Owner

What this changes

Syncs the Codex CLI placemat to v0.162.1, a bug-fix patch release (per releases.atom cross-checked against the /releases HTML page for prerelease status, and registry.npmjs.org/@openai/codex dist-tags.latest, since api.github.com is gated in the routine sandbox).

  • Added a changelog entry for v0.162.1 (two FIX items)
  • Added a note to codex app-server (card-cli, i-codex-app-server) documenting that startup compatibility checks now scope to explicit command-line feature overrides, fixing false-positive failures from drift between a running background server's feature settings and CLI defaults
  • The TUI crash fix (multi-line async questions, hyperlink preservation) is changelog-only — it doesn't change any documented command/setting
  • Bumped .release-tag / .print-head / footer "Content synced" to v0.162.1 / 2026-10-09
  • Re-checked existing unverified rows (/tui, /daemon, instant_interrupt, mcp_oauth_callback_port/mcp_optional_startup_grace_ms, ~/.codex/prompts, ~/.codex/rules) against this release's notes — none touched, none promoted
  • No new rows added, so sources.json → inventory is unchanged

Type

  • Content correction (wrong/outdated/missing entry)

Checklist

  • I read AGENTS.md's Style Guide and Content Rules
  • node tests/placemat.test.js codex passes locally (54 passed, 0 failed)
  • node scripts/build-changes.js --all --check passes locally (generated files are fresh)
  • No versions/*.html files were edited
  • No hand-edited changes.json or feed.xml — both regenerated via scripts/build-changes.js
  • Every new/changed row is sourced from Codex's own release notes (never from a sibling placemat)
  • Anything only inferable carries class="unverified" (no new unverified items added)
  • N/A — no new rows added this sync
  • Only the codex/ directory is touched

Source

🤖 Generated with Claude Code

https://claude.ai/code/session_015RnbLpbFX4nohBw82gnrY5


Generated by Claude Code

Bug-fix patch release: app-server startup compatibility checks now
scope to explicit CLI feature overrides, and a TUI crash on multi-line
async questions is fixed.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015RnbLpbFX4nohBw82gnrY5
The release note's TUI crash fix isn't confirmed to be the same feature
as the still-unverified /tui row, and tagging the changelog entry with
<code>/tui</code> made build-changes.js mark that row "new" — which the
unverified CSS silently overrides, hiding the highlight. Describe the
fix in plain text instead of tying it to an unconfirmed row.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015RnbLpbFX4nohBw82gnrY5

Copy link
Copy Markdown
Owner Author

Merge-gate code review (per codex/PIPELINE.md Step 10)

First pass (commit 37ca6d4) found one CRITICAL/HIGH-equivalent issue, reported as two linked findings:

  1. The v0.162.1 changelog entry tagged the TUI crash fix with <code>/tui</code>, asserting it as a confirmed fix for the specific (still unverified) /tui fullscreen-transcript command — a fabricated near-miss, since the release note describes a general TUI rendering fix, not confirmed to be that feature.
  2. As a direct consequence, build-changes.js would emit a changes.json item of "/tui", which shared/placemat.js's since-highlighting would apply as class="new" on top of the row's existing class="unverified" — a CSS-specificity conflict that silently hides the highlight.

Fix (commit 293da36): rewrote the entry as plain text ("TUI — fixed a crash …") with no <code> tag, so it isn't tied to the unconfirmed /tui row and build-changes.js emits no matching item for it.

Re-review (second pass, same scope): clean — node scripts/build-changes.js codex --check passes (not stale), node tests/placemat.test.js codex passes 54/54, and the fix was confirmed to correctly resolve both findings with no new issues introduced.

Verdict: clean, no CRITICAL/HIGH findings outstanding. Proceeding to merge per Step 10.


Generated by Claude Code

@dommango
dommango merged commit 5e76792 into main Oct 10, 2026
2 checks passed
@dommango
dommango deleted the claude/codex-update-v0.162.1 branch October 10, 2026 09:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants