openai / openai/codex

Codex Desktop repeatedly logs me out after completing responses

Open
#40,664 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app auth bug windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

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

26.819.11345

What subscription do you have?

plus

What platform is your computer?

OS Name: Microsoft Windows 11; 10.0.22631 Build 22631; Microsoft Corporation; Multiprocessor Free; System Type: x64-based PC

What issue are you seeing?

A repeated sign-in screen appears whenever an
assistant response completes or I open an existing conversation.

The issue occurs in either of these situations:

An assistant response finishes in the currently open conversation.
I select an existing conversation from the sidebar.
Immediately afterward, the desktop UI switches to a logged-out state and displays the sign-in screen.

Signing in succeeds, but it appears to create another login/device session. The app then loses authentication again
after completing a response or opening an existing conversation. This loop is consistently reproducible.

What steps can reproduce the bug?

Feedback ID: no-active-thread-01a03a08-e949-7b50-986d-c7fe38d27dab

What is the expected behavior?

The desktop app should remain authenticated after completing a response or opening an existing conversation.

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the logout loop in Codex Desktop 26.819.11345 on Windows 11, using the reported feedback ID no-active-thread-01a03a08-e949-7b50-986d-c7fe38d27dab. Check authentication behavior after a response completes and after opening an existing conversation; done means the app remains signed in in both cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
authentication, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.