Codex 0.148.0

Need to hand a Codex conversation to a teammate? You no longer have to select and copy it piece by piece.

Type /export in the TUI, the text-based interface, to turn the complete conversation into Markdown. Put it on the clipboard for pasting elsewhere, or save it as a new file. Questions, replies, and code that were spread across the screen now have a shareable copy.

Halfway through a task, you may want to try another path without losing the original thread. Run codex exec fork to split off a session, the record of one continuous piece of work.

The original session remains available while you explore the new one. You can also archive an inactive session from the TUI resume picker and restore it there later.

With the question already in mind, you no longer need to leave the keyboard idle while the TUI initializes: start drafting the prompt, the instruction for AI.

Startup also shows progress for resuming and forking work. You can tell whether the screen is still preparing, restoring a session, or creating a branch instead of watching an unexplained wait.

In an eligible workspace, you can check an estimate of this thread's credits or cost without leaving the terminal for a billing page.

Run /status for the estimate; terminal status lines and titles can show it too. It remains an estimate rather than a final bill, and availability depends on workspace eligibility.

If your company already runs AI through Amazon Bedrock Runtime on AWS, Codex now includes it as a built-in provider, a source of model connections.

It supports AWS profiles and regions. It also supports routing for GPT-5.6. That lets it use your existing AWS identity, location, and routing choices rather than requiring another external provider connection.

When an event should trigger an automatic follow-up, hooks, small programs triggered by specific events, no longer have to wait for their commands to finish. They can run commands asynchronously and invoke MCP tools, where MCP is a protocol that connects AI to external tools.

A hook can start a command or external tool after an event without tying the same execution path to that wait.

When returning to an earlier session, starting in the wrong folder or losing its approval rules is disruptive. Resumed sessions now restore the persisted working directory, the folder used for that work, and approval policy, the rules for actions that need consent. Transcript previews are also more accurate.

The TUI resume choice better shows what you are about to pick up and its original working context.

A temporary provider outage, where the source of model service connection has trouble, no longer means the current turn must end there. Turns reconnect through temporary provider outages. MCP servers, with MCP being the protocol connecting AI to external tools, also recover after OAuth reauthentication, where an existing account authorizes a third-party service.

Neither recovery requires restarting Codex.

Before you can read the TUI, the text-based interface, buffered terminal keystrokes no longer unexpectedly activate prompts or choices on screen. That prevents a prompt, a question waiting for input or selection, from being triggered before you can read it.

You can inspect the question first, then decide what to enter or select.

If Codex lacks authentication, the login check that proves identity, it no longer leaves you only at that missing-authentication state. It shows onboarding, guidance through the steps needed for first use. This connects the missing check to the required first-use steps.

Pasting text into the composer, the area for writing prompts, can bring CRLF, a two-symbol line-break format used by some text systems. Wrapped whitespace and long URLs, or web addresses, can also make the display render incorrectly. The composer and transcript, the conversation record display, now handle them correctly.

Pasted special line breaks, wrapped spaces, and long URLs should now stay readable.

A sandbox is an isolated environment that limits what a program can do. When it meets a denied or unreadable path, it now fails closed: it refuses access when safety cannot be confirmed.

This restriction applies across Linux and Windows. A denied or unreadable path is not allowed through; the sandbox keeps the boundary by rejecting it.

When you create a skill, an instruction guide that teaches Codex a particular way of working, its bundled skill-creator guide is now more focused. That guide concentrates on creating this kind of instruction.

Use the more focused guide when writing a skill.

Before a skill can pass validation, unfinished TODO placeholders, text left to complete later, can no longer remain in its contents. Validation, the check that content meets requirements, now rejects those placeholders.

A skill that passes validation cannot keep unfinished TODO placeholders.