Codex CLI forking stability and alternative better context sharing

Hi,

My original thread was today closed, with a suggestion implying it’s maybe already solved or not universally experienced, plus a suggestion to contact support. Well, how to contact support is very well finely hidden in the support pages, and support interactions are often tedious anyway.

So I’m posting here to learn if anyone has solved this yet.

On my machine, even with today’s new CLI version, forking doesn’t show a fork when listing available sessions. Not before nor after exiting the original session.

Is it only me?

The /side feature is by the way nice.

If forking happens to be at impedence mismatch to the rest of the feature set or CLI architecture, maybe consider just dropping it from being a feature (?)

Why not design and introduce a better context reuse feature?

It might just save some time, tokens and planet heat.

Hey @matanox, the original thread closing without a clear answer wasn’t ideal.

A fork should create a separate session with its own ID, so not seeing it afterward isn’t expected. As a workaround, try codex fork --last, then check the All scope in /resume. For a temporary detour, /side may also help.

If it’s still happening, please open a private support request using the chat bubble at the bottom-right of help.openai.com. Include your codex --version, OS, and /feedback details, then share only the case ID here. Please leave out any account information or logs.

Simar

Thank you. It’s really much better in recent versions already. I’d call it simply working now.