[Bug]: Codex usage check times out after 3 seconds despite a valid response #36180

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/server

Steps to reproduce

1. Use the desktop app with an authenticated Codex CLI.
2. Refresh or wait for the Codex usage limits check when account/rateLimits/read takes more than three seconds.
3. Observe the usage limits status. The delay is intermittent in this environment; it is not deterministic without a delayed response.

Expected behavior

A valid usage response that takes more than three seconds should be displayed, without blocking provider availability. A slow response should not be reported as if Codex never answered.

Actual behavior

T3 shows “Codex did not answer the usage request.” The installed server code applies a 3,000 ms timeout to account/rateLimits/read and maps a timeout to that message. Server traces show the request interrupted after approximately 3,002 ms. The reason for the variable response time is not established.

In a separate direct codex app-server test, five sequential account/rateLimits/read requests returned responses in 8.07, 2.38, 2.11, 3.76, and 2.75 seconds. Two exceeded T3's timeout but completed successfully. Codex conversations work while the usage check fails.

Consider allowing the usage request a longer independent timeout or updating the usage result asynchronously, while keeping provider discovery responsive.

Impact

Major degradation or frequent failure

Version or commit

0.1.8-nightly.20261109.4399

Environment

macOS 27.2, Apple Silicon, T3 Code desktop nightly, Codex CLI 0.167.0.

Logs or stack traces

CodexAppServerProtocol.request.awaitResponse
rpc.method: account/rateLimits/read
durationMs: 3001.697
exit: Interrupted

Workaround

No reliable workaround found. No application files were changed.

Related report

#27873 also reports missing Codex limits, but describes a managed token-sharing setup that only shows a link to the usage website. This report concerns an intermittent three-second timeout and the specific warning above.