OpenAI Codex v0.153.0 Lands Vim Undo/Redo With Full Draft Preservation, a Plugin CLI That Manages Remote Marketplaces, and an Experimental Context Manager for ChatGPT Plus and Pro. The TUI Reconnect Story Is Underneath.

Hey guys, Mr. Technology here.

OpenAI shipped OpenAI Codex v0.153.0 on September 3, 2026 at 01:39 UTC. The changelog is two layers: a feature layer (Vim undo/redo with full draft preservation, a plugin CLI that can list / install / remove plugins from remote marketplaces, an earlier usage warning for Plus and Team users, a new features.context_management.experimental_mode flag that activates a token-budget context manager for eligible ChatGPT Plus / Pro / Pro Lite sessions) and a fix layer (TUI sessions now reconnect cleanly after an app-server connection drop, Full Access skips Guardian reviews for confirmation-only actions, Guardian review history survives compaction, remembered MCP tool approvals are now app-account-scoped, rollout compression includes shared histories). For builders running Codex as a daily driver, the Vim undo/redo + plugin CLI combination is the user-facing headline. For builders running it unattended or behind a flaky network, the TUI reconnect story is the operational headline. (openai/codex: Release rust-v0.153.0)

This is a documentation-surfacing report. Every claim below is verifiable verbatim in the v0.153.0 release notes or the linked PRs. I have not installed v0.153.0 in a production harness; treat the workflow and capability claims as documentation comparison, not firsthand test.

What Shipped

The v0.153.0 changelog splits into "New Features," "Bug Fixes," and "Configuration and API Updates."

1. Vim mode undo/redo with full draft preservation

Per the changelog: "Vim mode now supports undo with u and redo with Ctrl+R, preserving complete drafts including pasted content and attachments. (PR #41941, #42140)."

This closes the most-asked gap in the Vim mode work that v0.152.0 introduced. v0.152.0 (covered Sep 1 in [openai-codex-v0-152-0-vim-mode-mcp-package-names-app-server-timeouts-sep-2026](https://mr.technology/payloads/openai-codex-v0-152-0-vim-mode-mcp-package-names-app-server-timeouts-sep-2026)) landed Vim search (/ and ?, n/N repeat) and basic editing motions. v0.153.0 finishes the editing story by adding u for undo and Ctrl+R for redo, with a guarantee that pasted content and attachments are preserved through the undo stack.

The "preserves complete drafts" wording is the operational detail. An earlier draft of the Codex TUI's undo could drop pasted content or strip attachments because the undo state did not include the full buffer with attachments. v0.153.0's undo preserves the buffer-as-shown, so a developer who pasted a long error message, then made some edits, then hit u to back out, will still see the pasted content in the older state. For developers using Codex in normal-mode Vim with the u/Ctrl+R keys, the workflow is now coherent.

2. Plugin CLI can list / install / remove plugins from remote marketplaces

Per the changelog: "The plugin CLI can list, install, and remove plugins from remote marketplaces. (PR #42150)."

This turns the Codex plugin CLI from a local-only tool into a marketplace manager. Per the changelog wording, the CLI can now reach remote marketplaces, list what is available, install a plugin, and remove a previously installed one. For teams that operate internal Codex plugin marketplaces (the kind of artifact the v0.151.0 "extensions can inspect / replace MCP tool results" feature was designed to compose with), this is the operational capability. A marketplace author can publish a plugin and a developer can install it with a single command, without manually editing the local plugin manifest.

The exact CLI shape was not in the visible changelog excerpt — this is a documentation-surfacing report and I have not run the CLI. Builders who depend on the plugin CLI's flag and argument shape should consult the PR and the Codex docs page for the full command surface.

3. Earlier usage warning for Plus and Team users

Per the changelog: "Plus and Team users receive an earlier warning when less than half of their allowance remains in an approximately five-hour usage window. (PR #42142)."

The Codex rate-limit / usage window for Plus and Team plans is a sliding five-hour budget. v0.153.0 surfaces a warning when the user has consumed more than half of that budget — i.e., earlier than the existing "you're running low" prompt that presumably fired closer to zero. For a developer who kicks off a long-running Codex session at the start of their five-hour window and walks away, the new warning fires mid-session instead of at the end. This is a UX win, not a capability change; the rate-limit math is unchanged.

4. tui.auto_recap = false opt-out

Per the changelog: "Set tui.auto_recap = false to disable automatic recaps while keeping manual /recap available. (PR #42101)."

The Codex TUI has been auto-generating recaps at intervals; some builders find the recap interrupts their flow. v0.153.0 adds a per-session config that disables the auto-recap while preserving the manual /recap command. A small workflow knob, but the kind of thing a developer who has been quietly annoyed by mid-session recap interruptions will appreciate.

5. TUI history shows complete patches

Per the changelog: "TUI history shows complete patches, input sent to background terminals, and individual completed commands. (PR #41893, #42107)."

Three related improvements to the TUI history view. Patches (the diff-style operations Codex emits during a session) are now shown in full instead of truncated. Input sent to background terminals (the kind of long-running command that gets backgrounded) is recorded. Individual completed commands are listed rather than collapsed. For a developer who later wants to reconstruct what Codex did during a session, this is a meaningful audit-trail upgrade.

6. features.context_management.experimental_mode (disabled by default)

Per the changelog: "Adds the disabled-by-default features.context_management.experimental_mode configuration. When enabled for eligible ChatGPT Plus, Pro, or Pro Lite sessions using the Codex backend, it activates token-budget context, history notes, and the new_context tool. API-key sessions, custom providers, and temporary structured threads remain excluded. (PR #42385)."

This is the most significant capability in v0.153.0 for ChatGPT subscription users, with a critical caveat. Three components:

• Token-budget context. Codex now manages the active context against a token budget, presumably summarizing, evicting, or compressing older context as the budget fills. The exact strategy was not in the visible changelog excerpt; consult PR #42385 and the Codex docs for the policy.
• History notes. Codex can emit structured "history notes" — meta-records about prior turns that survive compaction.
• new_context tool. A new tool that the model can call to start a fresh context slice.

The flag is disabled by default. It applies only to ChatGPT Plus, Pro, or Pro Lite sessions using the Codex backend. API-key sessions, custom providers, and temporary structured threads are excluded. For builders running Codex against the OpenAI API (the mr.technology audience), this flag does nothing. For ChatGPT subscribers who want to test the experimental context management, it slots in via features.context_management.experimental_mode = true in their Codex config.

The "disabled by default" + "Plus / Pro / Pro Lite only" + "API excluded" combination is a deliberate scope reduction. OpenAI is shipping a new context-management surface to a subset of users, watching the signal, and gating the broader rollout on what it learns. For builders watching the Codex capability roadmap, this is a leading indicator of where the next major Codex TUI experience is going.

7. tui.disable_paste_burst replaces top-level setting

Per the changelog: "tui.disable_paste_burst replaces the top-level setting, which remains supported as a fallback. (PR #41976)."

A small configuration migration. The Codex config previously had a top-level disable_paste_burst setting; v0.153.0 moves it under tui. (i.e., tui.disable_paste_burst) and keeps the top-level path as a fallback for backward compatibility. A config-rename for builders who customize their Codex settings.

8. App-server thread metadata + request_user_input_async

Per the changelog: "App-server thread metadata includes nullable model and reasoningEffort fields. Structured asynchronous questions are supported through request_user_input_async when enabled by the model catalog. (PR #42151, #42178)."

The Codex app-server (the JSON-RPC surface that IDE plugins and external harnesses talk to) gets two protocol-level additions. Thread metadata now carries a nullable model and a nullable reasoningEffort field — the harness can read which model and which reasoning effort produced a given thread. request_user_input_async lets the app-server surface structured asynchronous questions to the user when the model catalog enables it. For builders integrating Codex into an IDE or a custom harness, the app-server surface gets a small capability bump.

What Shipped In The Bug-Fix Layer

Six items in the "Bug Fixes" section, plus the configuration changes above.

9. TUI sessions reconnect after app-server disconnect

Per the changelog: "TUI sessions reconnect after an external app-server connection drops, preserving drafts and transcripts while keeping uncertain or queued submissions paused for review. (PR #41911, #41916, #41918)."

Three PRs around one operational story. When the external app-server connection drops mid-session (a network blip, an IDE restart, a sleep/wake), the TUI now reconnects, preserves the local drafts and transcripts, and keeps uncertain or queued submissions paused for review. The "paused for review" is the important detail — Codex does not silently re-submit work whose status it is no longer sure about; the developer gets to decide whether to resume or discard. For a developer working through a flaky VPN or a sleeping laptop, this is the fix for "my work disappeared."

10. Full Access skips Guardian reviews for confirmation-only actions

Per the changelog: "Full Access skips Guardian reviews for confirmation-only actions. User approval mode skips background Guardian scoring and prewarming, while sensitive-action checks and requests for user input retain their existing handling. (PR #42147, #42256)."

Two related Guardian (Codex's review/permission layer) refinements. Full Access (the high-trust mode) no longer routes confirmation-only actions through Guardian for a review — confirmation-only actions are the "confirm and proceed" prompts that don't need a separate review pass. User approval mode skips background Guardian scoring and prewarming, but retains sensitive-action checks and user-input request handling. Net effect: less Guardian overhead in the steady state, with the security-critical paths still reviewed. For builders running long Codex sessions, the reduced background scoring is a measurable latency and cost win.

11. Guardian review history survives compaction

Per the changelog: "Guardian review history survives compaction, restarts, and user-created forks while respecting rollback boundaries and isolating subagent history. (PR #41879, #42065)."

The Guardian review log was being lost when Codex compacted its context, restarted, or the user forked the session. v0.153.0 makes the review log durable across all three, while still respecting rollback boundaries (a rolled-back portion of a session does not carry its Guardian history forward) and isolating subagent history (a subagent's Guardian log does not bleed into the parent's log). For audit and compliance workflows that depend on a complete Guardian trail, this is the durability upgrade.

12. MCP tool approvals scoped to app account; relative paths start more reliably on macOS

Per the changelog: "Remembered MCP tool approvals are scoped to the selected app account, and relative MCP executable paths start more reliably on macOS. (PR #42133, #42117)."

Two MCP plumbing fixes. The first scopes "remembered MCP tool approval" (the per-user "always allow this MCP tool" state) to the currently selected app account, so a developer who switches between Codex app accounts does not accidentally carry approvals across. The second makes relative MCP executable paths resolve more reliably on macOS — a stability fix for MCP servers configured with relative paths to their launch script.

13. Rollout compression includes shared histories; thread forks work with symlinked session roots

Per the changelog: "Rollout compression includes shared histories, codex exec resume handles compressed rollouts when selecting by working directory, and thread forks work with symlinked session roots. (PR #42039, #42135)."

Three operational improvements. Rollout compression (the per-session state-snapshot mechanism) now includes the shared histories between threads, so a compressed rollout preserves enough context to resume cleanly. codex exec resume (the CLI flag for resuming a session) handles compressed rollouts even when the user selects by working directory. Thread forks (the "fork this session into a new branch" operation) work when the session root is a symlink — previously refused on symlinked roots.

What Actually Changed For Builders

TUI experience: Vim undo/redo with full draft preservation finishes the Vim mode editing story that v0.152.0 started. The plugin CLI now manages remote marketplaces. The TUI history view shows complete patches and recorded background-terminal input. The tui.auto_recap = false opt-out exists. None of these are capability changes for the model's behavior — they are workflow quality-of-life upgrades.

Subscription-only capability: The features.context_management.experimental_mode flag is the only true new capability surface in v0.153.0, and it is gated to ChatGPT Plus / Pro / Pro Lite sessions using the Codex backend. API-key sessions, custom providers, and temporary structured threads are excluded. For builders running Codex against the OpenAI API, this flag does nothing. For ChatGPT subscribers, it is opt-in via the config.

Operational reliability: The TUI reconnect story is the operational headline. Sessions now reconnect after app-server drops, preserve drafts and transcripts, and pause uncertain or queued submissions for review rather than silently re-submitting. Guardian review history survives compaction. MCP tool approvals are scoped to the active app account. Rollout compression includes shared histories. These are the kinds of upgrades that make Codex safe to leave running overnight.

Configuration migration: tui.disable_paste_burst is the new home for the old top-level setting; the old path remains as a fallback.

Why Developers And Founders Should Care

Reason 1: If you use Vim mode in the Codex TUI, v0.153.0 makes it coherent. u and Ctrl+R with full draft preservation is the missing piece. A developer who switched to Vim mode after v0.152.0 and has been quietly missing undo can now use the workflow without the workaround.

Reason 2: If you operate or consume a Codex plugin marketplace, the plugin CLI now does the install / remove / list dance against a remote source. Internal-marketplace authors get a single command surface for their users. A developer who has been editing the local plugin manifest by hand can now codex plugin install <name> from a configured marketplace.

Reason 3: If you run Codex on a flaky network or a sleeping laptop, the TUI reconnect behavior is the fix. Drafts and transcripts survive an app-server drop, and uncertain or queued submissions pause for review instead of silently re-submitting. For a long-running unattended session, this is the difference between "I came back and my work was there" and "I came back and Codex had re-submitted things in a confused state."

Reason 4: If you watch the Codex capability roadmap, features.context_management.experimental_mode is the leading indicator. Token-budget context management, history notes, and a new_context tool are the building blocks of a longer-horizon Codex experience. The "disabled by default, ChatGPT-only, API excluded" scope is a deliberate narrow rollout. Builders running Codex against the API should watch the changelog for the broader rollout.

Reason 5: Full Access / User approval mode skip unnecessary Guardian reviews. Confirmation-only actions in Full Access no longer trigger a Guardian pass; background Guardian scoring and prewarming are skipped in user-approval mode. Sensitive-action checks and user-input requests are unchanged. For a team running Codex in a high-volume or latency-sensitive context, the reduced Guardian overhead is a real cost and latency improvement.

Evidence And Test Results

Primary source: the v0.153.0 release notes and the atom feed entry timestamp. Every claim above is verifiable verbatim in the release notes' bullet list or the linked PR descriptions. The atom feed updated timestamp is 2026-09-03T01:39:03Z, confirmed at fetch time 2026-09-03 14:08 UTC.

The prior stable was v0.152.0 (covered Sep 1 in [openai-codex-v0-152-0-vim-mode-mcp-package-names-app-server-timeouts-sep-2026](https://mr.technology/payloads/openai-codex-v0-152-0-vim-mode-mcp-package-names-app-server-timeouts-sep-2026)). The v0.151.0 release (covered Aug 30 in [openai-codex-v0-151-extensions-inspect-mcp-results-august-2026](https://mr.technology/payloads/openai-codex-v0-151-extensions-inspect-mcp-results-august-2026)) landed the extensions-can-inspect / replace MCP tool results capability. The three releases together are a coherent capability arc: v0.151.0 added extensibility primitives, v0.152.0 added TUI polish + app-server timeouts, v0.153.0 adds Vim finishing touches + a subscription-only context-management experiment + operational durability.

The full PR list in the v0.153.0 changelog spans roughly 80 PRs (the visible portion of the diff includes PRs #41870 through ~#42385). I have not enumerated every PR — the items I have called out as the "operational shortlist" are my editorial selection based on impact for production Codex usage.

No firsthand test was run. The verification level is "documentation comparison + verbatim changelog quotes + linked PR descriptions." I have not installed v0.153.0, not exercised Vim undo/redo, not run the plugin CLI against a remote marketplace, not enabled features.context_management.experimental_mode, and not tested the TUI reconnect behavior. If you have first-hand evidence from an install attempt or a workflow test, I will update this article.

Cost, Risk, And Limitations

Cost: No new paid tier, no pricing change. The features.context_management.experimental_mode flag is a config; it does not change API pricing for the excluded (API-key) sessions. For ChatGPT Plus / Pro / Pro Lite subscribers who opt in, the token-budget context manager presumably consumes more tokens per session (summarization, history notes) — the exact budget cost is not in the visible changelog and was not measured in this report.

Risk: TUI reconnection pauses uncertain or queued submissions for review rather than auto-resuming. Teams that have been running unattended Codex sessions and expecting auto-recovery after a network blip will see prompts where they used to see silent resumes. Plan for a brief adjustment period as long-running sessions hit the reconnect path for the first time.

The plugin CLI's remote-marketplace behavior is new surface area for supply-chain risk. A developer who installs a plugin from a remote marketplace is trusting the marketplace author. Internal-marketplace operators should review the plugin author model and the install command's verification posture before rolling out to a team.

The Guardian review-history durability change is a security win for audit, but the "respects rollback boundaries" wording means a developer who rolls back a session also rolls back the Guardian trail for that portion. If your audit workflow assumes Guardian trail continuity across rollback, that assumption is now wrong.

Limitations of this report:

• Documentation-surfacing report, not firsthand test. I have not installed v0.153.0.
• The full PR list (~80 PRs) is summarized above; the items I have called out as the "operational shortlist" are my editorial selection based on impact for production Codex usage. Items I omitted are real changes but not material to the capability or reliability story.
• The exact CLI shape for the plugin CLI (subcommands, flags, marketplace URL format) was not in the visible changelog excerpt. Builders integrating the CLI should consult PR #42150 and the Codex plugin docs.
• The token-budget context manager's exact policy (when it summarizes, when it evicts, what new_context does) was not in the visible changelog excerpt. Consult PR #42385 and the Codex docs.
• I have not tested whether tui.disable_paste_burst retains the old top-level fallback behavior, or whether the new path is required for some builds.

Mr. Technology verdict

v0.153.0 is a stable continuation of the Vim-mode work from v0.152.0, not a flagging release. The operational shortlist — Vim u/Ctrl+R undo/redo with full draft preservation, plugin CLI remote-marketplace list/install/remove, TUI reconnect pausing uncertain submissions for review rather than auto-resuming, and features.context_management.experimental_mode for ChatGPT Plus/Pro/Pro Lite — closes three real production gaps: (1) undo/redo completes the interactive-edit loop, (2) the plugin CLI opens a remote-marketplace surface with real supply-chain implications, and (3) the reconnect behavior replaces silent auto-resume with explicit review-on-reconnect. The remaining ~80 PRs are mostly incremental fixes and stability work. This is a release to upgrade to if you depend on Vim mode heavily, run unattended Codex, or plan to roll out plugins through a remote marketplace; otherwise it is a routine refresh.

Recommended action

Today: upgrade Codex to v0.153.0 if you use Vim mode heavily — u/Ctrl+R undo/redo completes the interactive-edit loop and is the headline operational improvement. Also enable features.context_management.experimental_mode if you are a ChatGPT Plus / Pro / Pro Lite subscriber with token-budget concerns (expect higher per-session token use from the context manager).

This week: audit your TUI reconnect expectations — reconnecting sessions now pause uncertain or queued submissions for review rather than auto-resuming. If your operational pattern assumes auto-recovery after a network blip, plan for a brief adjustment period when the reconnect path first triggers. Also review the plugin CLI's remote-marketplace surface for supply-chain implications; internal-marketplace operators should confirm the plugin-author verification posture before rolling out to a team.

Next week: if you previously rolled back a session and assumed Guardian review-history continuity across rollback, that assumption no longer holds — Guardian's "respects rollback boundaries" means the trail rolls back with the session. Update audit workflows accordingly.

Skip if not in scope: don't enable experimental_mode on API-key sessions (the flag is excluded for those); don't plan a marketplace rollout without reviewing your plugin-author trust model; don't rely on auto-resume after reconnect for unattended Codex sessions.

Article history and corrections

Originally published: 2026-09-03 14:08 UTC Last verified: 2026-09-03 16:13 UTC No corrections at this time.