OPENAI PUB_DATE: 2026.03.06

CODEX V0.111.0: FAST MODE BY DEFAULT, STRUCTURED MCP, AND A WINDOWS APP LANDS

OpenAI Codex v0.111.0 turns on Fast mode by default, tightens MCP integration, expands image workflows, and debuts an early Windows app with mixed first impress...

Codex v0.111.0: Fast mode by default, structured MCP, and a Windows app lands

OpenAI Codex v0.111.0 turns on Fast mode by default, tightens MCP integration, expands image workflows, and debuts an early Windows app with mixed first impressions.

The release makes Fast mode the default, adds dynamic local .js/.mjs imports in js_repl, and shares enabled MCP apps and skills with the model at session start release notes. App‑server v2 now exposes MCP elicitation via a structured request/response API, image workflow handling is expanded, and resuming threads preserves git context and app enablement.

A Windows build of the Codex app is out, with community reports of stutter and some confusion about how to quit the app (Windows announcement, stutter report, quitting thread). There is also feedback asking for message editing and proper undo in the VS Code plugin plugin request.

Plan for app‑server v2’s structured MCP flow in clients and validate Fast mode’s performance, cost, and rate limits in CI or agent workflows.

[ WHY_IT_MATTERS ]
01.

Faster default execution and structured MCP calls can shorten feedback loops in codegen and tool‑use pipelines.

02.

Windows support and plugin UX gaps affect rollout plans for mixed OS developer fleets.

[ WHAT_TO_TEST ]
  • terminal

    Benchmark Fast vs Standard mode for latency, quality, and cost in your CI/agent paths.

  • terminal

    Validate MCP plugin discovery and app‑server v2 request/response handling, including thread resume preserving git context.

[ BROWNFIELD_PERSPECTIVE ]

Legacy codebase integration strategies...

  • 01.

    Map migrations from event‑stream MCP integrations to app‑server v2’s structured API and update clients accordingly.

  • 02.

    Exercise codex resume on legacy repos to confirm git context and app enablement remain intact.

[ GREENFIELD_PERSPECTIVE ]

Fresh architecture paradigms...

  • 01.

    Adopt app‑server v2 from day one and design skills around MCP‑aware startup instructions.

  • 02.

    Use js_repl dynamic imports and artifact workflow samples to standardize reusable workspace scripts.

SUBSCRIBE_FEED
Get the digest delivered. No spam.