openclaw - 💡(How to fix) Fix OAuth refresh error surfaced to user on every message even when access token is valid [1 comments, 2 participants]

Bug: OAuth token refresh error surfaced to user on every message even when access token is still valid

The error appears even when the access token has 6-8 hours remaining (verified via auth-profiles.json → expires field). The agent still responds correctly after the error (fallback works), but the error message is sent to the user first, creating a poor UX. 5. The error is surfaced to the user via agent-runner.runtime-DEDCwJ0o.js line 632 as "Agent failed before reply"

• If refresh fails but access token is still valid, the error should NOT be surfaced to the user

1. Observe error message before the actual response None found. The error persists regardless of:

TL;DR

Modify the OAuth token refresh logic to skip refresh when the access token is still valid and suppress error messages when the refresh fails but the access token remains valid.

Guidance

• Review the auth-profiles-bVW1e9Dr.js file, specifically line 258, to ensure the condition if (Date.now() < cred.expires) correctly skips token refresh when the token is valid.
• Investigate modifying the agent-runner.runtime-DEDCwJ0o.js file, line 632, to prevent surfacing the "Agent failed before reply" error to the user when the access token is still valid, despite the refresh failure.
• Consider implementing a check to prevent probe-anthropic-* sessions from triggering token refresh independently, potentially by adding a flag or condition to skip refresh during these sessions.
• Examine the Cloudflare configuration for the Anthropic OAuth token refresh endpoint to understand the IP blocking behavior and potential workarounds.

Example

// Example of modified refresh logic in auth-profiles-bVW1e9Dr.js
if (Date.now() < cred.expires) {
  // Token is still valid, skip refresh
  return;
} else {
  // Token has expired, attempt refresh
  // ...
}

Notes

The provided workaround attempts may not be comprehensive, and further investigation into the Anthropic OAuth token refresh endpoint and Cloudflare configuration may be necessary to resolve the issue.

Recommendation

Apply a workaround by modifying the OAuth token refresh logic and error handling to suppress user-facing errors when the access token is still valid, as the root cause is related to Cloudflare blocking server IPs and the issue persists across different accounts and setups.