[Codex App] IAB browser session IDs are resumed as remote SSH thread IDs

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

26.715.10079.0

What subscription do you have?

Not provided.

What platform is your computer?

Microsoft Windows NT 10.0.22000.0 x64

What issue are you seeing?

When using the Codex Desktop app with a managed remote SSH host, some sidebar entries appear as new/local conversations but cannot be resumed. Opening one produces:

no rollout found for thread id <id>

The failing IDs appear to be In-App Browser (IAB) / Browser Use session IDs, not Codex agent thread IDs.

For example, the desktop log first records the same ID as a Browser Use session route:

IAB_LIFECYCLE webview captured browser use session route
conversationId=019f8dc7-96b5-72b2-84d3-b299dbcdba4c

Later, the desktop registers that ID as a browser-sidebar thread under /local/<id>, associates it with a remote-ssh-codex-managed host, and calls thread/resume:

maybe_resume_started conversationId=019f8dc7-96b5-72b2-84d3-b299dbcdba4c
hostId=remote-ssh-codex-managed:<redacted>

Request failed ... method=thread/resume
error={"code":-32600,"message":"no rollout found for thread id 019f8dc7-96b5-72b2-84d3-b299dbcdba4c"}

I observed the same sequence for these IDs:

• 019f8dc3-91d7-7ca2-947f-6ebe52c08b07
• 019f8dc6-9a79-74b0-b2f2-f98db1487877
• 019f8dc7-96b5-72b2-84d3-b299dbcdba4c
• 019f8dc9-c3ab-7731-a8bb-bdeb27e50f46

For each ID, there was no matching row in Codex's local threads state table and no matching rollout JSONL file. The app is therefore attempting to resume an ID that was never a rollout-backed Codex thread.

What steps can reproduce the bug?

I do not yet have a single deterministic click sequence, but the observed flow is consistent:

1. Open Codex Desktop and connect to a managed remote SSH host.
2. Use a workflow that causes an In-App Browser / Browser Use session route to be captured.
3. A sidebar entry is later registered with the IAB session's conversationId at a /local/<id> route.
4. Open that entry.
5. The app invokes thread/read and then thread/resume with the IAB session ID, which fails with no rollout found for thread id <id>.

The issue occurred on two separate managed remote SSH hosts.

What is the expected behavior?

Browser Use/IAB session IDs must not be persisted or registered as normal local Codex conversations, and must never be passed to thread/read or thread/resume as a Codex thread ID.

For remote SSH conversations, the sidebar should retain the actual rollout-backed thread ID. If no such thread exists, the UI should not create a resumable conversation entry.

Additional information

I searched existing open issues and did not find one that matched this specific IAB-session-ID-to-remote-SSH-thread-ID mismatch.

I can provide a redacted excerpt of the desktop log if useful.