Codex desktop falsely reports “GitHub CLI not authenticated” on macOS

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

26.707.31428 (build 5059)

What subscription do you have?

PRO

What platform is your computer?

Darwin 27.0.0 arm64 arm

What issue are you seeing?

The Environment panel displays GitHub CLI not authenticated even though GitHub CLI authentication works correctly from the same Codex task environment.

Verified from the Codex environment:

gh version 2.96.0 (Homebrew, /opt/homebrew/bin/gh)
gh auth status --active --hostname github.com  -> authenticated
gh api user --jq .login                       -> succeeds
gh repo view                                  -> succeeds
gh pr status                                  -> succeeds

Additional checks:

• Credentials are securely stored in macOS Keychain.
• The Codex app-server process has the correct HOME and includes /opt/homebrew/bin in PATH.
• No GH_TOKEN, GITHUB_TOKEN, GH_HOST, or GH_CONFIG_DIR override is set.
• Git is already configured to use gh auth git-credential.
• The repository remote is a normal https://github.com/... URL.

Despite all of these checks succeeding, the Environment panel continues to classify the CLI as unauthenticated.

<img width="662" height="1000" alt="Image" src="https://github.com/user-attachments/assets/b524e7f4-3e6f-4827-9646-bdc091111770" />

What steps can reproduce the bug?

1. Authenticate GitHub CLI on macOS using its normal browser flow and macOS Keychain storage.
2. Confirm from a Codex task that gh auth status --active --hostname github.com and gh api user --jq .login succeed.
3. Open a local GitHub repository in Codex desktop.
4. Expand the Environment panel for the task.
5. Observe the disabled row: GitHub CLI not authenticated.

The incorrect status has been observed repeatedly even though authenticated GitHub CLI commands continue to work.

What is the expected behavior?

Codex should recognize the valid GitHub CLI authentication. The Environment panel should not show an unauthenticated warning, and GitHub/PR status features should use the authenticated CLI.

Additional information

The installed Codex UI maps an internal gh-cli-status response to missing, unauthenticated, or available. In this case the UI is receiving unauthenticated, while direct CLI and GitHub API checks succeed. This suggests a false negative in the app's status-check execution context or refresh path.

GitHub suggested #31017 as a potential duplicate, but the behavior here is distinct: in #31017, gh auth status fails inside the Codex task environment. In this report, authenticated gh and GitHub API commands succeed inside Codex; only the Environment-panel status is incorrect.

Possibly related:

• https://github.com/openai/codex/issues/31017
• https://github.com/openai/codex/issues/19262
• https://github.com/openai/codex/issues/10695

A screenshot of the incorrect Environment-panel state is attached above.