Codex App GitHub CLI auth preflight times out too aggressively

Open 💬 0 comments Opened Jun 23, 2026 by zhuhaow

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

Codex Desktop 26.616.51431 (bundle build 4212)

What subscription do you have?

N/A

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

The Codex App Environment/Summary panel reports:

GitHub CLI not authenticated

But GitHub CLI is installed and authenticated. The failing condition is not authentication; it is that Codex gives the local gh auth status preflight only 5 seconds to complete.

A successful gh auth status can take slightly longer than 5 seconds. In my environment, repeated successful runs took about 5.8-6.2 seconds.

After increasing the local gh auth status timeout from 5 seconds to 10 seconds, the false authentication error stopped appearing.

What is the expected behavior?

Codex should not treat a successful gh auth status command as failed just because it takes slightly longer than 5 seconds.

The local GitHub CLI auth preflight should either use a longer timeout, such as 10 seconds, or distinguish timeout from authentication failure in the UI.

Additional information

The packaged app code appears to use a 5 second timeout for local gh auth status, while remote-ish hosts get 10 seconds:

async function Q0({ appServerClient: e, signal: t }) {
  let n = G(e.hostConfig) ? 5e3 : 1e3,
      r = G(e.hostConfig) ? 1e4 : 5e3;

  let i = await F0([`--version`], {
    appServerClient: e,
    signal: t,
    timeoutMs: n
  });

  return i.success
    ? {
        isInstalled: true,
        isAuthenticated: (await F0([`auth`, `status`], {
          appServerClient: e,
          signal: t,
          timeoutMs: r
        })).success
      }
    : { isInstalled: false, isAuthenticated: false };
}

For local hosts, r is 5e3. Changing that local value to 1e4 resolved the false status.

View original on GitHub ↗