GitHub Copilot / GitHub Copilot

GitHub Copilot CLI Auth Swallows REST Quota Errors — Session Was Not Created

Diagnose and fix GitHub Copilot CLI authentication failures caused by silent swallowing of REST quota exceeded and rate limit errors during token validation phase Includes evidence for GitHub Copilot troubleshooting demand.

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

Category: GitHub Copilot
Error signature: Session was not created with authentication info or custom provider (root cause: CLI auth flow silently swallows REST quota/rate-limit errors during token validation)
Quick fix: Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests.
Updated: June 10, 2026
Verification status: Source-backed
Evidence: 4 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

Session was not created with authentication info or custom provider (root cause: CLI auth flow silently swallows REST quota/rate-limit errors during token validation) is a GitHub Copilot failure pattern reported for developers trying to diagnose and fix github copilot cli authentication failures caused by silent swallowing of rest quota exceeded and rate limit errors during token validation phase. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Copilot-cli GitHub issue #3311 specifically reports that the CLI auth flow silently swallows REST quota/rate-limit errors, surfacing them as opaque 'Session was not created' messages instead of actionable quota errors. Related issue microsoft/vscode #263822 shows rate limit exceeded for user sign-in with explicit request IDs. Another issue #13702 documents quota_exceeded server error. Category mapping: GitHub Copilot → GitHub Copilot.

Common causes

Copilot-cli GitHub issue #3311 specifically reports that the CLI auth flow silently swallows REST quota/rate-limit errors, surfacing them as opaque 'Session was not created' messages instead of actionable quota errors. Related issue microsoft/vscode #263822 shows rate limit exceeded for user sign-in with explicit request IDs. Another issue #13702 documents quota_exceeded server error. Category mapping: GitHub Copilot → GitHub Copilot.

Quick fixes

Confirm the exact error signature matches Session was not created with authentication info or custom provider (root cause: CLI auth flow silently swallows REST quota/rate-limit errors during token validation).
Check the GitHub Copilot account, local tool state, and provider configuration involved in the failing workflow.
Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests.

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 Session was not created with authentication info or custom provider (root cause: CLI auth flow silently swallows REST quota/rate-limit errors during token validation) 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 Session was not created with authentication info or custom provider (root cause: CLI auth flow silently swallows REST quota/rate-limit errors during token validation) mean in GitHub Copilot?

Session was not created with authentication info or custom provider (root cause: CLI auth flow silently swallows REST quota/rate-limit errors during token validation) indicates the workflow described by "GitHub Copilot CLI Auth Swallows REST Quota Errors — Session Was Not Created" failed in a GitHub Copilot context. Start by confirming the exact signature and the component that emitted it.

What should I check first for Session was not created with authentication info or custom provider (root cause: CLI auth flow silently swallows REST quota/rate-limit errors during token validation)?

Check whether this cause matches your environment: Copilot-cli GitHub issue #3311 specifically reports that the CLI auth flow silently swallows REST quota/rate-limit errors, surfacing them as opaque 'Session was not created' messages instead of actionable quota errors. Related issue microsoft/vscode #263822 shows rate limit exceeded for user sign-in with explicit request IDs. Another issue #13702 documents quota_exceeded server error. Category mapping: GitHub Copilot → GitHub Copilot.

Is the Session was not created with authentication info or custom provider (root cause: CLI auth flow silently swallows REST quota/rate-limit errors during token validation) guidance source-backed?

The "GitHub Copilot CLI Auth Swallows REST Quota Errors — Session Was Not Created" page is labeled source-backed. It has 4 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 Session was not created with authentication info or custom provider (root cause: CLI auth flow silently swallows REST quota/rate-limit errors during token validation)?

For "GitHub Copilot CLI Auth Swallows REST Quota Errors — Session Was Not Created", avoid applying "Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests." 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 Session was not created with authentication info or custom provider (root cause: CLI auth flow silently swallows REST quota/rate-limit errors during token validation)?

For "GitHub Copilot CLI Auth Swallows REST Quota Errors — Session Was Not Created", 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.