/fork inside codex expected to fork and create a new session UUID

What version of the Codex App are you using (From “About Codex” dialog)?

0.120.0

What subscription do you have?

plus

What platform is your computer?

Ubuntu

What issue are you seeing?

I used '/fork' and was expected to have a new session UUID that I can resume (and really have a 'tree' starting to grow that I can play with). What I got instead is the same UUID is kept, I am told I can resume the session where I am in codex like "To continue this session, run codex resume 019d83ff-6220-71d2-adc3-4e17ba25e7e1" and that doen't work.

What steps can reproduce the bug?

1. create and start a session with anything
2. run '/fork' and note the 'codex resume <UUID>'
3. send another message right away
4. go into another terminal and run 'codex resume <SESSION_UUID>'
5. Expect to see the last message you sent to the fork which is not what we want, we expect the last message to be the one at the moment we forked.

What is the expected behavior?

• [ ] we expect the last message to be the one at the moment we forked.
• [ ] We expect the new fork to probably have a new UUID generated

Additional information

_No response_