Codex sessions get redirected back to “new session” a few seconds after first prompt

[tchirou]

Image Variant

Full (latest / dev)

Image Tag / Version

1.1.7

Host OS

Linux

What happened?

When starting a new Codex session, the session is created and the first
prompt is sent successfully, but shortly after that the UI returns to the
“new session” page instead of staying on the active session.

The session itself is not lost and can still be reopened manually.

From debugging, the likely cause is that Codex emits a complete event without
exitCode: 0, while the frontend only finalizes navigation for newly created
sessions when j.exitCode === 0.

Claude includes exitCode: 0 in its complete event, so it does not have this
issue.

What did you expect?

After sending the first prompt in a new Codex session, the UI should stay on
the active session and finalize navigation to the real session ID, just like
it does for Claude.

The frontend should not fall back to the “new session” page after completion.

Steps to reproduce

1. Open HolyClaude / CloudCLI.
2. Start a new chat with Codex.
3. Send the first prompt.
4. Wait a few seconds for the first turn to complete.
5. Observe that the UI returns to the “new session” page.
6. Reopen the created session manually and confirm it still exists.

Technical note :

Likely root cause: update 1.27.1 in siteboon/claude-code-ui

• openai-codex.js sends:

{ kind: 'complete', actualSessionId: thread.id, sessionId: currentSessionId }

• Claude sends:

{ kind: 'complete', exitCode: 0, actualSessionId: ..., sessionId: ... }

• frontend completion logic appears to require:

j.exitCode === 0

Suggested fix:
add exitCode: 0 to the Codex complete event in openai-codex.js, to match
Claude’s behavior.

Docker Compose / Run command

Logs / Error output

[CoderLuii]

Thanks. This one was real.

The important part was that the Codex session was not actually getting lost. It got created, the first prompt went through, and then the UI kicked you back to the new session page. That pointed at session completion and navigation handling, not session creation.

I checked the CloudCLI side and the completion path really was treating successful completion too narrowly.

This is fixed in v1.1.9.

What changed:

Successful completion no longer depends on an explicit exitCode === 0 just to finalize the pending session view.

That keeps the UI on the active Codex session after the first prompt instead of bouncing back to new session.

Short version: the session existed before, and now the UI should stop mishandling completion.

If you still hit this on v1.1.9, reply here and I’ll reopen it.

[CoderLuii]

Closing as fixed in v1.1.9.

[tchirou]

Hi
No it’s not fixed on my end. Tried with a private session too just in case.
Also, there is a cloudcli update request, I don’t now if we need to do it ?
Thanks