Adopt Codex `/export`, `codex exec fork`, and thread cost status
Codex CLI rust-v0.148.0 adds Markdown export via/export, session fork/archive/restore, startup prompt drafting, thread credit/cost in /status, Bedrock Runtime, and async/MCP hooks—use them to make session reuse, cost visibility, and automation first-class.Why this loop
rust-v0.148.0 makes session reuse and cost visible in the TUI and exec path. /export writes a complete conversation to Markdown (clipboard or a new file), so handoffs no longer depend on terminal scrollback. codex exec fork plus resume-picker archive/restore let you branch a thread and park the parent; resumed sessions restore persisted cwd and approval policy with more accurate transcript previews. You can draft the next prompt while the TUI initializes, with resume/fork progress shown at startup. Eligible workspaces show estimated thread credits/cost in /status, status lines, and terminal titles. Amazon Bedrock Runtime is a built-in provider (AWS profile, region, GPT-5.6 routing). Hooks can run commands asynchronously and invoke MCP tools. Model/settings updates no longer leave stale instructions or mutate an in-flight turn; turns reconnect through temporary provider outages; MCP recovers after OAuth reauth without restarting Codex; sandbox path denials fail closed on Linux and Windows. Treat export, fork/archive, and cost status as default workflow.
Proposed actions
- In the Codex TUI, run
/exportand write the full conversation Markdown to./codex-exports/<session-id>.md(or the clipboard); attach or commit that file on any PR or handoff from this thread. - From the repo, run
codex exec forkon the current session to branch a new thread; in the TUI resume picker archive the parent, then restore it only when you need the original persisted working directory and approval policy. - While the TUI is still initializing, draft the next prompt (resume/fork progress is shown at startup). After attach, run
/statusand confirm estimated thread credits/cost appear in/status, the status line, and the terminal title for this eligible workspace; record those numbers before and after a fork. - Switch this workspace to Codex’s built-in Amazon Bedrock Runtime provider using the local AWS profile and region, with GPT-5.6 routing enabled; remove any custom Bedrock HTTP/proxy shim.
- Update project hooks so command hooks run asynchronously and invoke MCP tools from the hook; verify a hook can call an MCP tool without blocking the turn, and that a mid-session model or settings change does not rewrite stale instructions or alter the active turn.
Agent prompt
Paste into your agent or query via MCP (get_agent_prompt) — free, no extra AI costCodex / agent CLI task
DevAgentRadar → OpenAI Codex
Task: evaluate and optionally implement follow-ups from this coding-assistant release.
Context
Assistant: OpenAI Codex CLI
Proposal: Adopt Codex /export, codex exec fork, and thread cost status
Summary: Codex CLI rust-v0.148.0 adds Markdown export via /export, session fork/archive/restore, startup prompt drafting, thread credit/cost in /status, Bedrock Runtime, and async/MCP hooks—use them to make session reuse, cost visibility, and automation first-class.
Primary source: https://github.com/openai/codex/releases/tag/rust-v0.148.0
Why it matters
rust-v0.148.0 makes session reuse and cost visible in the TUI and exec path. /export writes a complete conversation to Markdown (clipboard or a new file), so handoffs no longer depend on terminal scrollback. codex exec fork plus resume-picker archive/restore let you branch a thread and park the parent; resumed sessions restore persisted cwd and approval policy with more accurate transcript previews. You can draft the next prompt while the TUI initializes, with resume/fork progress shown at startup. Eligible workspaces show estimated thread credits/cost in /status, status lines, and terminal titles. Amazon Bedrock Runtime is a built-in provider (AWS profile, region, GPT-5.6 routing). Hooks can run commands asynchronously and invoke MCP tools. Model/settings updates no longer leave stale instructions or mutate an in-flight turn; turns reconnect through temporary provider outages; MCP recovers after OAuth reauth without restarting Codex; sandbox path denials fail closed on Linux and Windows. Treat export, fork/archive, and cost status as default workflow.
Suggested actions
- In the Codex TUI, run
/exportand write the full conversation Markdown to./codex-exports/<session-id>.md(or the clipboard); attach or commit that file on any PR or handoff from this thread. - From the repo, run
codex exec forkon the current session to branch a new thread; in the TUI resume picker archive the parent, then restore it only when you need the original persisted working directory and approval policy. - While the TUI is still initializing, draft the next prompt (resume/fork progress is shown at startup). After attach, run
/statusand confirm estimated thread credits/cost appear in/status, the status line, and the terminal title for this eligible workspace; record those numbers before and after a fork. - Switch this workspace to Codex’s built-in Amazon Bedrock Runtime provider using the local AWS profile and region, with GPT-5.6 routing enabled; remove any custom Bedrock HTTP/proxy shim.
- Update project hooks so command hooks run asynchronously and invoke MCP tools from the hook; verify a hook can call an MCP tool without blocking the turn, and that a mid-session model or settings change does not rewrite stale instructions or alter the active turn.
Config surfaces this release may change
- skills (high confidence) — check your repo before applying
- sandbox settings — check your repo before applying
- MCP servers — check your repo before applying
After you finish
Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.
Tell the human: open https://devagentradar.com/proposals/openai-codex-rust-v0-148-0-adopt-codex-export-codex-exec-fork-and-thread and mark Applied, Skipped, or Failed. Proposal id: f393d661-2216-4375-92f3-a8b41b69756e
Deliverables:
- Short impact assessment
- Optional patch plan (files + steps)
- Do not invent APIs not in the source notes
Your loop
This browser · no sign-in · not shared as “you”After you run the prompt
Only you can mark this. Agents cannot write your loop.
Your decision stays on this device. A public tally appears after a few votes.