GitHub Copilot / GitHub Copilot

OpenRouter Auth Token Expires Mid-Session — AADSTS90009 After ~60 Min Silent Refresh

Developers using GitHub Copilot CLI via MCP sessions experience silent OAuth token expiration after ~60 minutes. The silent refresh sends outdated OAuth v1 resource format instead of v2 scope format, causing Azure AD rejection (AADSTS90009). Long-running coding sessions die unexpectedly without re-auth flow. Includes evidence for GitHub Copilot troubleshooting demand.

Source-backed Last updated June 10, 2026 3 sources Needs local verification

Category: GitHub Copilot
Error signature: MCP silent token refresh sends v1 resource=<clientId> instead of v2 scope= → AADSTS90009 after ~60 min / GitHub Copilot API token expires mid-session with no proactive refresh, causing 401 errors in long-running subagents
Quick fix: Verify the account session, API key, provider settings, and environment where the failing tool is running.
Updated: June 10, 2026
Verification status: Source-backed
Evidence: 3 public source URLs

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for GitHub Copilot, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

MCP silent token refresh sends v1 resource=<clientId> instead of v2 scope= → AADSTS90009 after ~60 min / GitHub Copilot API token expires mid-session with no proactive refresh, causing 401 errors in long-running subagents is a GitHub Copilot failure pattern reported for developers trying to developers using github copilot cli via mcp sessions experience silent oauth token expiration after ~60 minutes. the silent refresh sends outdated oauth v1 resource format instead of v2 scope format, causing azure ad rejection (aadsts90009). long-running coding sessions die unexpectedly without re-auth flow.. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Three distinct but related GitHub issues: copilot-cli#3583 (AADSTS90009 after ~60min silent refresh v1 vs v2 format), openclaw/openclaw#31132 (Copilot API token expires mid-session with no proactive refresh, 401 errors in long-running subagents), copilot-sdk#867 (authentication error on Debian Bookworm but same setup works on Windows). The v1→v2 OAuth transition is causing production-reliability issues for teams using Copilot CLI in CI/coding agents. Category: GitHub Copilot (Copilot-specific).

Common causes

Three distinct but related GitHub issues: copilot-cli#3583 (AADSTS90009 after ~60min silent refresh v1 vs v2 format), openclaw/openclaw#31132 (Copilot API token expires mid-session with no proactive refresh, 401 errors in long-running subagents), copilot-sdk#867 (authentication error on Debian Bookworm but same setup works on Windows). The v1→v2 OAuth transition is causing production-reliability issues for teams using Copilot CLI in CI/coding agents. Category: GitHub Copilot (Copilot-specific).

Quick fixes

Confirm the exact error signature matches MCP silent token refresh sends v1 resource=<clientId> instead of v2 scope= → AADSTS90009 after ~60 min / GitHub Copilot API token expires mid-session with no proactive refresh, causing 401 errors in long-running subagents.
Check the GitHub Copilot account, local tool state, and provider configuration involved in the failing workflow.
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

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
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.

Diagnostic flow for this page

Match MCP silent token refresh sends v1 resource=<clientId> instead of v2 scope= → AADSTS90009 after ~60 min / GitHub Copilot API token expires mid-session with no proactive refresh, causing 401 errors in long-running subagents exactly before applying the quick fix.
Compare the failing environment with GitHub Copilot versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does MCP silent token refresh sends v1 resource=<clientId> instead of v2 scope= → AADSTS90009 after ~60 min / GitHub Copilot API token expires mid-session with no proactive refresh, causing 401 errors in long-running subagents mean in GitHub Copilot?

MCP silent token refresh sends v1 resource=<clientId> instead of v2 scope= → AADSTS90009 after ~60 min / GitHub Copilot API token expires mid-session with no proactive refresh, causing 401 errors in long-running subagents indicates the workflow described by "OpenRouter Auth Token Expires Mid-Session — AADSTS90009 After ~60 Min Silent Refresh" failed in a GitHub Copilot context. Start by confirming the exact signature and the component that emitted it.

What should I check first for MCP silent token refresh sends v1 resource=<clientId> instead of v2 scope= → AADSTS90009 after ~60 min / GitHub Copilot API token expires mid-session with no proactive refresh, causing 401 errors in long-running subagents?

Check whether this cause matches your environment: Three distinct but related GitHub issues: copilot-cli#3583 (AADSTS90009 after ~60min silent refresh v1 vs v2 format), openclaw/openclaw#31132 (Copilot API token expires mid-session with no proactive refresh, 401 errors in long-running subagents), copilot-sdk#867 (authentication error on Debian Bookworm but same setup works on Windows). The v1→v2 OAuth transition is causing production-reliability issues for teams using Copilot CLI in CI/coding agents. Category: GitHub Copilot (Copilot-specific).

Is the MCP silent token refresh sends v1 resource=<clientId> instead of v2 scope= → AADSTS90009 after ~60 min / GitHub Copilot API token expires mid-session with no proactive refresh, causing 401 errors in long-running subagents guidance source-backed?

The "OpenRouter Auth Token Expires Mid-Session — AADSTS90009 After ~60 Min Silent Refresh" page is labeled source-backed. It has 3 public source URLs from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for MCP silent token refresh sends v1 resource=<clientId> instead of v2 scope= → AADSTS90009 after ~60 min / GitHub Copilot API token expires mid-session with no proactive refresh, causing 401 errors in long-running subagents?

For "OpenRouter Auth Token Expires Mid-Session — AADSTS90009 After ~60 Min Silent Refresh", avoid applying "Verify the account session, API key, provider settings, and environment where the failing tool is running." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging MCP silent token refresh sends v1 resource=<clientId> instead of v2 scope= → AADSTS90009 after ~60 min / GitHub Copilot API token expires mid-session with no proactive refresh, causing 401 errors in long-running subagents?

For "OpenRouter Auth Token Expires Mid-Session — AADSTS90009 After ~60 Min Silent Refresh", collect the failing GitHub Copilot command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.