openai / openai/codex

[Windows] Signing out shows “Oops, an error has occurred” after AppServer RPC disconnect

Open
#40,312 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Summary

Signing out of the Codex desktop app completes successfully, but the app does not transition to the normal signed-out screen. Instead, it immediately reaches the global error boundary and displays:

Oops, an error has occurred

The application log reports:

AppServerManager RPC is not connected

Environment
  • App: OpenAI Codex desktop app
  • Version: 26.818.5229.0
  • Installation source: Microsoft Store
  • Package status: OK
  • OS: Windows 25H2, OS build 26200.9168
  • Architecture: x64

Microsoft Store currently reports that this is the latest version available for my release channel.

Steps to reproduce
  1. Open the Codex desktop app.
  2. Sign in with a ChatGPT account.
  3. Open the account menu/settings.
  4. Select Sign out.
  5. Wait for the app to switch to the signed-out screen.
Expected behavior

After signing out, the app should display the normal signed-out screen with the option to continue and sign in again.

Actual behavior

The sign-out operation succeeds, but the UI displays a generic error page:

Oops, an error has occurred

A Try again button is shown.

Reproduction frequency

This has reproduced consistently during recent sign-out attempts. Local logs indicate that the same AppServerManager RPC is not connected error has occurred immediately after multiple sign-out operations since approximately August 19, 2026.

Sanitized log excerpt

The following timestamps are in UTC:

2026-08-24T01:43:22.615Z
AppServerConnection response_routed
method=account/logout
errorCode=null

2026-08-24T01:43:23.127Z
desktop_fetch_auth_401
hadToken=false
skipRetryReason=no_token_attached

2026-08-24T01:43:23.225Z
error boundary
errorMessage="AppServerManager RPC is not connected"
errorName=Error

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 tracing the account/logout flow and the AppServerManager RPC connection state around the reported error boundary. Reproduce sign-out on Windows and inspect the sanitized sequence showing account/logout, desktop_fetch_auth_401, and the RPC disconnect. Done means successful sign-out reaches the normal signed-out screen instead of the generic error page.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
authentication, desktop, operating-systems
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.