What is the status of experimental_resume in proto mode?

[Doraemonwei]

Background

While reviewing the CLI, I noticed that the documentation marks experimental_resume as an internal experimental flag . When I launch proto mode (codex proto -c experimental_resume=<...>),
nothing seems to happen: the session_configured event still reports history_entry_count as a fresh session, and no log entries acknowledge the key.

Questions

1. Can someone confirm that proto mode currently ignores experimental_resume, and that this is working as intended?
2. Is there any plan or tentative timeline to support session resume in proto mode (perhaps by reusing the codex resume <rollout_id> flow)?

Thanks!

[jazzyalex]

It appears proto mode currently ignores that flag by design. Do you happen to know if there’s any roadmap to re-enable it (or support a resume flow in proto mode)?

Also, for visual session browsing + resume, you might check out Agent Sessions — it reads Codex & Claude session logs locally and offers a searchable UI plus menu-bar usage tracking.

[Doraemonwei]

Thank you for your recommendation.
It seems that the official codex has completely removed support for Codex Proto.
Currently, I am using the codex app-server to implement my application. You can refer to codex-rs/app-server.