# GitHub Copilot CLI: known issues context pack (KnownFix)
Generated 2026-10-26T10:18:14Z from github.com/github/copilot-cli. Auto-extracted; verify via links. Source: https://knownfix.ai/issues/copilot-cli/
Fields: severity (auto-estimate) | symptom | versions mentioned | workaround (quoted from issue/comments, if any) | fixed-in (if referenced).

## Active
- [HIGH] Windows: plugin update fails with "Access is denied (os error 5)" while VS Code is running (Copilot extension holds watc (https://github.com/github/copilot-cli/issues/4095)
  - symptom: copilot plugin update (and the same flow triggered from the GitHub Copilot desktop app) fails on Windows with: The git fetch/checkout of the marketplace clone succeeds every time (the clone under %LOC
  - versions: 2.5.0, 3.0.0, 1.0.70
  - error: `Failed to update plugin: Error: Failed to install plugin: Error: Access is denied. (os error 5)`
  - workaround: none stated
- [MEDIUM] Windows: MCP Entra sign-in fails with "this server's advertised scopes could not be safely validated for the account bro (https://github.com/github/copilot-cli/issues/5068)
  - symptom: On Windows, authenticating to an Entra ID–protected MCP server (Microsoft's hosted Azure DevOps MCP server, https://mcp.dev.azure.com/{org} , server type http ) fails on every fresh interactive sign-i
  - versions: 1.0.93-2, 1.0.92, 1.0.81
  - error: `On Windows, authenticating to an Entra ID–protected MCP server (Microsoft's hosted Azure DevOps MCP server, https://mcp.dev.azure.com/{org} , server type http )`
  - workaround: none stated
- [MEDIUM] Copilot app blocked by macOS Gatekeeper under corporate security policy (https://github.com/github/copilot-cli/issues/970)
  - symptom: Everytime after upgrading copilot cli through HomeBrew the following message appears: Apple could not verify “copilot” is free of malware that may harm your Mac or compromise your privacy
  - versions: 0.0.381
  - error: `Everytime after upgrading copilot cli through HomeBrew the following message appears:`
  - workaround: none stated
- [MEDIUM] HTTP MCP server with Bearer token fails OAuth discovery instead of falling back to headers auth (https://github.com/github/copilot-cli/issues/3100)
  - symptom: When an HTTP MCP server is configured in .mcp.json with "type": "http" and "headers": { "Authorization": "Bearer " }, the CLI attempts OAuth discovery (/.well-known/oauth-authorization-server ) and fa
  - error: `MCPOAuthError: Failed to discover authorization server metadata`
  - workaround: Manually enabling the server via /mcp enable bypasses OAuth discovery and connects successfully using the Bearer token. [issue body]
- [MEDIUM] Azure MCP server fails sending HTTP request (https://github.com/github/copilot-cli/issues/4851)
  - symptom: This broke overnight
  - versions: 1.0.83, 1.2, 1.1
  - error: `[rust:hyper_util::client::legacy::connect::http] connected to ...:443`
  - workaround: none stated
- [MEDIUM] Voice server segfaults (signal 11) on WSL2 after updating to 1.0.100; /voice stuck on 'Fetching voice models' (https://github.com/github/copilot-cli/issues/5197)
  - symptom: After updating to Copilot CLI 1.0.100 (which also pulled a new voice runtime), voice input no longer works on WSL2
  - versions: 1.0.100, 1.0.98
  - error: `[INFO] voice server: boot pid=1708 endpoint=/run/user/1000/copilot-voice/<id>.sock`
  - workaround: none stated
- [MEDIUM] Support MCP resources/read primitive (https://github.com/github/copilot-cli/issues/1803)
  - symptom: MCP servers can expose data through the resources primitive (resources/list, resources/read)
  - versions: 2.2.2
  - error: `✓ search_topics: pekko kafka consumer actor ordering sharding entity`
  - workaround: none stated
- [CRITICAL] Desktop app: sessions die minutes after spawn — "GitHub credential registration is no longer available for this session" (https://github.com/github/copilot-cli/issues/4905)
  - symptom: GitHub Copilot desktop app 1.1.22 (commit c3daa01), macOS arm64, bundled CLI 1.0.84-5 (server mode, stdio, Rust JSON-RPC engine) Single github.com account signed in to the app; gh auth status (bundled
  - versions: 1.1.22, 1.0.84-5, 2.98.0
  - error: `MCP tool catalog changed before tool "github-mcp-server-web_search" could be invoked: Failed to verify cached MCP tools: MCP request failed: Transport send erro`
  - workaround: none stated
- [MEDIUM] ACP mode: MCP OAuth token is never persisted after successful sign-in — every new session re-opens the browser (https://github.com/github/copilot-cli/issues/5192)
  - symptom: In ACP mode (copilot --acp), the OAuth token for a remote HTTP MCP server is never written to disk or the OS keychain after a successful sign-in
  - versions: 1.0.98
  - error: `14:32:47.302Z [WARNING] [rust:copilot_runtime::session::mcp::agent_host] HTTP 401 challenge (...) {"server":"atlassian-cloud"}`
  - workaround: none stated
- [MEDIUM] CLI 1.0.103: persistent session-lock timeouts and unresponsive tasks amid host event acknowledgement failures (https://github.com/github/copilot-cli/issues/5253)
  - symptom: A long-lived Copilot CLI session becomes largely unresponsive
  - versions: 1.0.103, 1.0.96, 25.472
  - error: `Failed to refresh tasks: Error: session lock unavailable during is_session_generation_current: acquisition timed out`
  - workaround: none stated
- [MEDIUM] Built-in Slack MCP integration requests full scope superset even when only read tools are exposed (https://github.com/github/copilot-cli/issues/4935)
  - symptom: When authenticating the built-in Slack MCP server ( mcp.slack.com ) via Copilot CLI, the generated OAuth consent URL requests the full superset of Slack scopes — including write scopes ( chat:write , 
  - versions: 1.0.87-0
  - error: `When authenticating the built-in Slack MCP server ( mcp.slack.com ) via Copilot CLI, the generated OAuth consent URL requests the full superset of Slack scopes `
  - workaround: none stated
- [HIGH] Regression (1.0.88 → 1.0.89): MCP OAuth authorization page opens on every ACP session instead of the challenge being res (https://github.com/github/copilot-cli/issues/4994)
  - symptom: An OAuth-protected HTTP MCP server that has a valid, unexpired access token in ~/.copilot/mcp-oauth-config is answered with HTTP 401 on every new --acp session, and the CLI responds by opening the OAu
  - versions: 1.0.88, 1.0.89, 152.1
  - error: `[ERROR] [rust:rmcp::transport::worker] worker quit with fatal: Transport channel closed,`
  - workaround: none stated

## Recently closed (with fix/workaround info)
- MCP: Figma remote server (mcp.figma.com) fails to load — `-32601` on `server/discover` treated as fatal (works (https://github.com/github/copilot-cli/issues/4870); workaround: Update to a newer CLI build that supports Figma's `2026-07-28` MCP protocol handshake.
- Support refreshing the BYOK provider credential without restarting the CLI (https://github.com/github/copilot-cli/issues/3682); workaround: export COPILOT_PROVIDER_TYPE=azure export COPILOT_PROVIDER_BASE_URL=https://my-apim.azure-api.us/openai export COPILOT_MODEL=gpt-5.1 ### CLI runs this to get a