codex - 💡(How to fix) Fix Codex Desktop App uses credits from the original account even after switching to a different Plus account [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#21314Fetched 2026-05-07 03:42:10
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×4commented ×1unlabeled ×1
RAW_BUFFERClick to expand / collapse

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

Version 26.429.61741 (2429)

What subscription do you have?

Plus

What platform is your computer?

Linux 6.8.0-110-generic x86_64 x86_64

What issue are you seeing?

I am currently connected to a remote SSH server(Linux 6.8.0-110-generic x86_64 x86_64) through Codex desktop app in macOS(Darwin 25.3.0 arm64 arm). I switched accounts after reaching usage limits in my first account. Even after switching the account, all requests are still attributed to the first account. Creating a new thread and starting a a conversation also atrributes the credits to the first account. But /status points to the latest account.

<img width="404" height="385" alt="Image" src="https://github.com/user-attachments/assets/6887af57-f496-4b90-bfb3-740f9da89ce6" />

What steps can reproduce the bug?

(Connected to an ssh server through Codex Desktop)

  1. Log in to Account A.
  2. Start a chat thread and send a message. Usage is correctly billed to Account A.
  3. Log out or switch to Account B.
  4. Continue the conversation in the same thread from Step 2.
  5. Observed Behavior: Usage for the new messages is still attributed to Account A. But /status shows account B status

What is the expected behavior?

Usage and telemetry should be attributed to the currently logged-in account (Account B).

Additional information

I have logged into Account B in codex desktop app, ssh server directly and codex cli as well. This issue doesn't occur if I use codex cli in the ssh server but happens when using Codex Desktop app connected to ssh server. Crating a new conversation in the local machine attributed the usage to Account B while all new and old conversations in the ssh project attributed it to account A.

I have already checked the issue #14730 but the solution in the thread did not help as this is specific to ssh connections through codex.

Session ID - 019dfb0a-87e9-7f42-9919-c2c49ba519f4

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING