Adopt named sessions, thread forks, and plugin marketplaces in Codex CLI
Use session naming, pinned threads, and temporary forks to keep parallel work organized, and adopt Agent Plugins plus expanded marketplaces so skills and tools stay discoverable without restarting healthy MCP connections.Why this loop
Codex CLI rust-v0.146.0 makes parallel agent work first-class: /new and /clear name sessions, threads can be pinned, and side conversations can be switched without closing them. Forks carry paginated history, including temporary forks that stay off thread listings. Agent Plugins manifests, workspace plugin publishing, and marketplaces for Amazon Bedrock and Claude Code keep skills and tools discoverable; executor-provided skills and associated resources can be read securely, including explicitly selected skills. MCP connections and Apps tools update when authentication or configuration changes, reconnecting closed servers without restarting healthy connections. Configured proxies apply across authentication, plugin downloads, MCP authorization, remote execution, WebSockets, redirects, and LM Studio. Submitted messages, final responses, failed-turn errors, imported timestamps, and approval settings survive interruptions, replay, imports, and forks. Skill catalogs warn when truncated under tight context. Fifty-five changelog items were omitted from this signal; do not assume extra features.
Proposed actions
- Upgrade this machine to Codex CLI rust-v0.146.0 from https://github.com/openai/codex/releases/tag/rust-v0.146.0 using OpenAI-hosted release artifacts (GitHub fallback). On macOS, confirm bundled helper executables are signed and notarized before packaging.
- Stop using untitled Codex sessions. Start each workstream with
/new <short-slug>or/clear <short-slug>, pin the primary thread, then open a side conversation and switch back without closing the pinned thread. - For speculative work, fork the active thread so paginated inherited history is available, and create it as a temporary fork that does not appear in thread listings. After the fork, verify the approvals reviewer, submitted messages, final responses, failed-turn errors, and imported timestamps are still present.
- Add an Agent Plugins manifest, publish the workspace plugin, and enable the Amazon Bedrock and Claude Code plugin marketplaces. Discover executor-provided skills and securely read their associated resources for explicitly selected skills; if the catalog looks stale, issue a plugin list request with forceRefetch.
- Route authentication, plugin downloads, MCP authorization, remote execution, WebSockets, redirects, and LM Studio through the existing configured proxy (including CARGO_HTTP_CAINFO / system proxy). After an MCP auth or config change, reconnect only closed servers and leave healthy MCP connections and Apps tools running.
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 named sessions, thread forks, and plugin marketplaces in Codex CLI Summary: Use session naming, pinned threads, and temporary forks to keep parallel work organized, and adopt Agent Plugins plus expanded marketplaces so skills and tools stay discoverable without restarting healthy MCP connections. Primary source: https://github.com/openai/codex/releases/tag/rust-v0.146.0
Why it matters
Codex CLI rust-v0.146.0 makes parallel agent work first-class: /new and /clear name sessions, threads can be pinned, and side conversations can be switched without closing them. Forks carry paginated history, including temporary forks that stay off thread listings. Agent Plugins manifests, workspace plugin publishing, and marketplaces for Amazon Bedrock and Claude Code keep skills and tools discoverable; executor-provided skills and associated resources can be read securely, including explicitly selected skills. MCP connections and Apps tools update when authentication or configuration changes, reconnecting closed servers without restarting healthy connections. Configured proxies apply across authentication, plugin downloads, MCP authorization, remote execution, WebSockets, redirects, and LM Studio. Submitted messages, final responses, failed-turn errors, imported timestamps, and approval settings survive interruptions, replay, imports, and forks. Skill catalogs warn when truncated under tight context. Fifty-five changelog items were omitted from this signal; do not assume extra features.
Suggested actions
- Upgrade this machine to Codex CLI rust-v0.146.0 from https://github.com/openai/codex/releases/tag/rust-v0.146.0 using OpenAI-hosted release artifacts (GitHub fallback). On macOS, confirm bundled helper executables are signed and notarized before packaging.
- Stop using untitled Codex sessions. Start each workstream with
/new <short-slug>or/clear <short-slug>, pin the primary thread, then open a side conversation and switch back without closing the pinned thread. - For speculative work, fork the active thread so paginated inherited history is available, and create it as a temporary fork that does not appear in thread listings. After the fork, verify the approvals reviewer, submitted messages, final responses, failed-turn errors, and imported timestamps are still present.
- Add an Agent Plugins manifest, publish the workspace plugin, and enable the Amazon Bedrock and Claude Code plugin marketplaces. Discover executor-provided skills and securely read their associated resources for explicitly selected skills; if the catalog looks stale, issue a plugin list request with forceRefetch.
- Route authentication, plugin downloads, MCP authorization, remote execution, WebSockets, redirects, and LM Studio through the existing configured proxy (including CARGO_HTTP_CAINFO / system proxy). After an MCP auth or config change, reconnect only closed servers and leave healthy MCP connections and Apps tools running.
Config surfaces this release may change
- MCP servers (high confidence) — check your repo before applying
- skills — 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-146-0-adopt-named-sessions-thread-forks-and-plugin- and mark Applied, Skipped, or Failed. Proposal id: c9112d15-bc55-4151-ad80-23e1e2932e92
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.