Is it only me or is the /fork feature of Codex CLI not always consistently working in its latest version?

• The fork itself issues its success message and how to resume the pre-fork conversation, but the pre-fork conversation fails to be resumed as if it’s still active in another session.
• The conversations list often doesn’t show the fork or forked-from, but just one conversation after the /fork command as if succeeded. Not immediately nor after waiting some time.
• The resume command doesn’t really enable honing in on the right conversation after the fork, the conversation id doesn’t show in its conversations list, so it’s a trial and error.

It would be nice if the fork message gave the actual one-liner all-included command for resuming the pre-fork conversation and not prose about how to do it, if that command would simply work.

I guess this is all simpler with the native Codex App but I’m not currently using a supported OS for that.

I’m on codex-cli 0.147.0. I think it always auto-upgrades.