Two parallel threads running with the same thread id #34034

Activity

1. nbros

   added

   appIssues related to the Codex desktop appIssues related to the Codex desktop app

   on Jul 18, 2026
2. github-actions

   added

   bugSomething isn't workingSomething isn't working

   remote

   sessionIssues involving session (thread) management, resuming, forking, naming, archivingIssues involving session (thread) management, resuming, forking, naming, archiving

   subagentIssues involving subagents or multi-agent featuresIssues involving subagents or multi-agent features

   on Jul 18, 2026
3. github-actions commented on Jul 18, 2026

   

   github-actionsbot

   on Jul 18, 2026 – with GitHub Actions

   Contributor

   More actions

   Potential duplicates detected. Please review them and close your issue if it is a duplicate.

   • Open in app allows two app-server processes to write the same rollout, merging divergent histories after restart #33241
   • Codex Desktop fork aborts duplicated active turn while parent rollout completes, hiding the reply #32980
   • [Windows][Mobile] Turns completed from Codex mobile are missing from the Desktop transcript #32976

   Powered by Codex Action
4. nbros commented on Jul 18, 2026

   

   nbros

   on Jul 18, 2026

   Author

   More actions

   It's really bad! I started a goal in a thread from Codex Desktop (in a local thread) and it was progressing normally.
   Then I just opened the thread in ChatGPT Remote on my Android phone and immediately (without me prompting anything), it started doing parallel work from what my desktop was doing and stepping on each other!

   👍React with 👍1Reacted by sirouk
5. nbros commented on Jul 19, 2026

   

   nbros

   on Jul 19, 2026

   Author

   More actions

   ChatGPT thinks that the issue is that concurrent turns are being created in the same thread when steering from another Remote SSH client.

   Additional diagnostic details from the local session log:

   Thread/session id:
   019f78a1-a176-7a73-bcfa-3cb05f93e6cd

   Two turns were running concurrently inside that same thread:

   • 04:29:11Z — turn 019f78a2-9f21-71a1-9f9b-fc08e3cc70da started a long-running command.
   • 04:30:03Z — while that turn was still active, a message sent from the other client started a separate turn:
     019f78a3-6c50-7883-9229-658765ef425d
   • 04:30:07Z — the second turn completed.
   • 04:30:26Z — the first turn continued producing output.
   • 04:30:55Z — the first turn was eventually aborted.

   The UI merged the streamed output from both turns chronologically, but later model context did not contain the same history shown in the UI.

   The two concurrent turns also received different contexts/settings:

   • different personality settings;
   • different workspace root lists;
   • developer instructions present in one turn but absent from the other.

   Expected behavior:

   • A thread should have only one active turn, unless parallel turns are explicitly supported and represented as separate branches.
   • A message sent from another client should either steer the active turn or be queued for the next turn.
   • All clients viewing the same thread should receive the same canonical transcript and turn state.
   • Messages addressed to the main thread must never be routed to a subagent thread.

   Codex App version: 26.715.31925
   Embedded CLI/app-server version from the session log: 0.145.0-alpha.18

   👍React with 👍1Reacted by sirouk
6. phulin commented on Jul 20, 2026

   

   phulin

   on Jul 20, 2026

   Last edited by phulin

   More actions

   I am also seeing this issue. Quite frustrating. I then stopped the main thread, while the thread started from my phone continued working without me (and ended up using my entire weekly limit).

   👍React with 👍1Reacted by sirouk