Authentication token expiration causes request failures even after re-authentication

Resolved 💬 7 comments Opened Dec 23, 2025 by matthieu-labs Closed Feb 21, 2026

Description:

Since approximately 3 days ago, I'm experiencing a critical authentication issue where session token expiration consistently causes request failures, even after successful re-authentication.

Bug Behavior:

  1. Session token expires during normal usage (403 error: "The security token included in the request is expired")
  2. Claude Code automatically attempts to re-authenticate (shows retry attempts: 1/10, 2/10, etc.)
  3. Re-authentication appears to succeed
  4. However, the original request still fails with the same token expiration error
  5. This pattern repeats on every session expiration

Expected Behavior:
After successful re-authentication, the original request should be retried and succeed, not continue to fail with the same token expiration error.

Frequency:
This happens every single time a session expires - 100% reproduction rate.

Timeline:

  • Started: Approximately 3 days ago (around December 20, 2025)
  • Prior behavior: This issue did not occur before; re-authentication worked correctly

Environment:

  • Tool: Claude Code CLI
  • Model: claude-sonnet-4-5-20250929 (EU)
  • Platform: macOS (Darwin 24.6.0)
  • Date: December 23, 2025

Impact:
This forces manual intervention on every session expiration, significantly disrupting workflow and making the tool unreliable for longer sessions.

Suspected Cause:
The re-authentication mechanism appears to refresh the token, but the original failed request may not be properly retrying with the new token, instead continuing to use the expired token.

View original on GitHub ↗

This issue has 7 comments on GitHub. Read the full discussion on GitHub ↗