codex - 💡(How to fix) Fix Codex CLI 0.124.0 misreports `gh auth status` as invalid inside Codex session [1 comments, 2 participants]

What version of Codex CLI is running?

0.124.0

What subscription do you have?

Unknown

Which model were you using?

gpt-5.4 xhigh

What platform is your computer?

Darwin 25.3.0 arm64 arm

What terminal emulator and version are you using (if applicable)?

tmux (TERM=tmux-256color)

What issue are you seeing?

Inside Codex CLI 0.124.0, running gh auth status incorrectly reported that the active GITHUB_TOKEN and the saved skshim-reco account were invalid.

On the same machine and same repo, running gh auth status in a normal terminal session succeeded.

The failing Codex output was effectively:

• Failed to log in to github.com using token (GITHUB_TOKEN)
• The token in GITHUB_TOKEN is invalid.
• the saved default account was also reported as invalid

After downgrading to 0.122.0, gh auth status succeeded again.

What steps can reproduce the bug?

1. Start Codex CLI 0.124.0.
2. Use Full Access mode.
3. Run gh auth status inside the Codex session.
4. Observe that Codex reports the active GITHUB_TOKEN and saved account as invalid.
5. Run gh auth status in a normal terminal on the same machine and repo.
6. Observe that GitHub auth succeeds there.
7. Downgrade Codex CLI to 0.122.0 and rerun gh auth status.
8. Observe that it succeeds again.

Uploaded thread: 019dbd61-a8a7-78d0-8444-322d2b838a42

What is the expected behavior?

gh auth status inside Codex should match the normal terminal result on the same machine and report valid authentication.

Additional information

• The active GitHub account was skshim-reco.
• The GITHUB_TOKEN value was unchanged between the successful and failing checks.
• This looked like a Codex runtime/environment regression rather than an actually invalid GitHub token.