LiteLLM GitHub Copilot authenticator does not invalidate stale access token on 401, causing auth loop

What this error means

LiteLLM GitHub Copilot authenticator: stale access token causes unrecoverable auth loop is a LiteLLM failure pattern reported for developers trying to fix litellm github copilot auth loop when access token becomes stale. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

3 reactions. _refresh_api_key() reads cached token from ~/.config/litellm/github_copilot/access-token without validation. On 401, retries with same stale token 3 times, then raises RefreshAPIKeyError. No code path to delete stale token and re-run device flow.

Common causes

• When GitHub OAuth token expires or is revoked, LiteLLM retries with same stale token 3 times then loops indefinitely without clearing cached token
• 3 reactions. _refresh_api_key() reads cached token from ~/.config/litellm/github_copilot/access-token without validation. On 401, retries with same stale token 3 times, then raises RefreshAPIKeyError. No code path to delete stale token and re-run device flow.

Quick fixes

1. Confirm the exact error signature matches LiteLLM GitHub Copilot authenticator: stale access token causes unrecoverable auth loop.
2. Check the LiteLLM account, local tool state, and provider configuration involved in the failing workflow.
3. Verify the account session, API key, provider settings, and environment where the failing tool is running.

Platform/tool-specific checks

• Verify the command, editor, extension, or API client that produced the error.
• Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
• Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. Keep the working fix documented for the team or deployment environment.

How to prevent it

• Keep provider/tool configuration documented.
• Record non-secret diagnostics such as tool version, provider name, model name, and command path.
• Add a lightweight check before CI or production workflows depend on the tool.

Sources checked

• https://github.com/BerriAI/litellm/issues/25312

Evidence note: 3 reactions. _refresh_api_key() reads cached token from ~/.config/litellm/github_copilot/access-token without validation. On 401, retries with same stale token 3 times, then raises RefreshAPIKeyError. No code path to delete stale token and re-run device flow.

Related errors

• Claude Code 401 Auth Loop
• LiteLLM BudgetExceededError

FAQ

What should I check first?

Start with the exact LiteLLM GitHub Copilot authenticator: stale access token causes unrecoverable auth loop text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed LiteLLM workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without LiteLLM GitHub Copilot authenticator: stale access token causes unrecoverable auth loop.