Codex 0.148 runs on Amazon Bedrock; hooks now call MCP tools
The Aug 18 release also forks live sessions, surfaces per-run spend in your status line, exports chats to Markdown, and fails the sandbox closed.
Copy markdown
Bedrock as a built-in provider
Codex now routes through Amazon Bedrock Runtime as a first-class provider: point it at an AWS profile and region and run GPT-5.6 from your own account, no proxy layer. Teams locked to AWS can finally run Codex on-network.
Hooks go async and call MCP tools
Hooks can now run asynchronously and invoke MCP tools directly, so one hook can kick off a lint, hit an MCP server, or ping a service without blocking the turn. Codex hooks graduate from shell shims to real automation.
Fork and archive sessions
`codex exec fork` branches a session so you can chase two directions from the same context, and you can archive or restore sessions from the resume picker. Resumed sessions now also restore their working directory and approval policy.
See what a run costs, live
Estimated thread credits and dollar costs now surface in `/status`, the status line, and your terminal title for eligible workspaces. No more finishing a long agent run and guessing what it burned.
`/export` the whole conversation
Export a full TUI session to Markdown — clipboard or file — with `/export`. Drop an entire agent run straight into a PR description, an issue, or your notes.
The sandbox now fails closed
Sandbox restrictions now fail closed for denied or unreadable paths on Linux and Windows, and onboarding appears when auth is missing. If Codex can't confirm a path is allowed it blocks instead of guessing — a real tightening for restricted setups.