### What happened? When I start a conversation from the Zed Codex agent integration, that session does not appear in the Codex CLI `/resume` list. ### Steps to reproduce 1. Start a Codex session from Zed (Codex agent integration). 2. Open Codex CLI and run `/resume`. 3. Observe that the Zed-started session is missing. ### Expected behavior Sessions started via Zed integration should be discoverable in `/resume`, so they can be continued from the CLI. ### Actual behavior Only CLI-started sessi

/resume does not list sessions started via Zed Codex agent integration

Resolved 💬 3 comments Opened Feb 9, 2026 by ThePlenkov Closed Feb 10, 2026

💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

What happened?

When I start a conversation from the Zed Codex agent integration, that session does not appear in the Codex CLI /resume list.

Steps to reproduce

Start a Codex session from Zed (Codex agent integration).
Open Codex CLI and run /resume.
Observe that the Zed-started session is missing.

Expected behavior

Sessions started via Zed integration should be discoverable in /resume, so they can be continued from the CLI.

Actual behavior

Only CLI-started sessions are listed; Zed-started sessions are not, so continuation is not possible.

Impact

Breaks conversation continuity across clients and makes earlier discussions effectively non-resumable from CLI.

Related context

A similar issue was reported and resolved in cagent: https://github.com/docker/cagent/issues/1591

Could Codex align behavior so sessions from integrations are also resumable via /resume?

View original on GitHub ↗

3 Comments

etraut-openai contributor · 6 months ago

This is because the Zed Codex Agent uses Codex as an MCP server. Sessions created through this interface are consisted non-interactive sessions. Only interactive sessions are displayed in the /resume command.

For IDEs and editors that want to integrate with Codex, we recommend using the Codex App Server interface. This is what we used for our own VS Code Extension and the new Codex App. It's also used by JetBrains for their PyCharm Codex extension and Apple for their Xcode Codex extension. Sessions created with this interface are considered interactive and will show up across in the TUI when you run /resume.

ThePlenkov · 6 months ago

@etraut-openai are you sure about this? I thought they are using ACP capbility https://github.com/zed-industries/codex-acp. And in ACP mode zed can be just one of agents using codex as a client. QUestion - do you support history for ACP mode then, not MCP? thanks!

etraut-openai contributor · 6 months ago

There is no special "ACP mode" in codex. ACP relies on running codex as an MCP server.