Codex UI always switches to tab 1 upon tab 1 task completion.

Resolved 💬 1 comment Opened Oct 1, 2025 by martinambrus Closed Jan 10, 2026

What version of Codex is running?

OpenAI Web

Which model were you using?

OpenAI Web

What platform is your computer?

Windows

What steps can reproduce the bug?

  • task Codex with anything and request at least 3 versions
  • let's say the thread in tab 2 finishes first
  • switch to tab 2, create pull request, maybe request changes etc. - all this while tab 1 thread still works
  • switch to tab 2, wait for thread in tab 1 to complete
  • UI auto-switches to tab 1

This is not just annoying but also very bad because of the overall design of Codex UI. I can only chat and request changes on a single tab. However, when the UI switches to tab 1, I loose any possible continuation of tab 2 (where I already have a pull request) because I have something in chat already and don't realize my tabs have switched - and I just press the "Code" button (on tab 1 now).

Secondly, this also creates a bug where - even though I already HAVE chat history in tab 2 - I'm still auto-switched to tab 1, where chat is still enabled. When I press "Code" button now, I am no longer able to return to tab 2 to continue, since tab 1 now has chat history and is considered the latest thread!

What is the expected behavior?

Never auto-switch tabs when any of them completes :)

What do you see instead?

Always switched to tab 1 whenever it finished.

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗