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

## Active
- [MEDIUM] Integration: would a runtime governance proxy in front of MCP servers be in scope for third-party integrations? (https://github.com/continuedev/continue/issues/12492)
  - symptom: Hi maintainers, Opening an issue first to gauge appetite before any code work, in the same shape as #12423
  - versions: 3.0-or, 1.0, 1.5
  - error: `, with optional Ed25519-signed OVERT 1.0 envelopes for the same set. Operator allowlist and denylist flags filter tools, resources, and prompts at the perimeter`
  - workaround: none stated
- [HIGH] IntelliJ IDEA 2026.2.1 : Continue crashes (https://github.com/continuedev/continue/issues/13119)
  - symptom: Continue plugin crash : IntelliJ IDEA 2026.2.1 Build #IU-262.9437.185, built on August 9, 2026 Source revision: 5ced7b0cd2861 Licensed to CNRS / DSI / David Marques You have a perpetual fallback licen
  - versions: 2026.2.1, 262.9437.185, 25.0.3+9
  - error: `Exception reporter ID: 08102517e5fe3e1-0b26-4cb6-aae8-64d6c2092562`
  - workaround: none stated
- [HIGH] fix(openai): Stream parser crashes on extra unknown JSON fields (extra_content / usage payload) in CLI (cn) & IDE (https://github.com/continuedev/continue/issues/13417)
  - symptom: I've tried finding an answer on the Continue docs site I'm not able to find an open issue that reports the same bug I've seen the troubleshooting guide on the Continue Docs When using an OpenAI-compat
  - versions: 1.0.67, 2025.2.4, 1.0.0
  - error: `- Model: Google Gemini OpenAI-compatibility endpoint`
  - workaround: none stated
- [MEDIUM] Windows absolute paths are parsed as remote package slugs (https://github.com/continuedev/continue/issues/13372)
  - symptom: Windows absolute paths are classified as remote package slugs by decodePackageIdentifier
  - error: `On main (`5522c6f`), `C:\project\rule.yaml`, `C:/project/rule.yaml`, and `\\server\share\rule.yaml` all return `uriType: "slug"`. The forward-slash drive path e`
  - workaround: none stated
- [MEDIUM] CLI 1.5.47: on a 401 the interactive CLI starts `npx -y mcp-remote` with no version pinned, in every OAuth profile we te (https://github.com/continuedev/continue/issues/13429)
  - symptom: What happens @continuedev/cli 1.5.47 is the current release on npm
  - versions: 1.5.47, 9.8, 0.15.1
  - error: `classifies an error as authentication, an interactive session falls back to`
  - workaround: none stated
- [HIGH] edit_existing_file tool is unusable and crash VSCode. (https://github.com/continuedev/continue/issues/13076)
  - symptom: I've tried finding an answer on the Continue docs site I'm not able to find an open issue that reports the same bug I've seen the troubleshooting guide on the Continue Docs I tried to let my agent use
  - versions: 2.0.0, 1.0.0
  - error: `"arguments": "{\"filepath\":\"index.html\",\"changes\":\" // ... existing code ...\\n let moveSpeed = player.running ? 350 : 500;\\n let accel = 1800;\\n let fr`
  - workaround: none stated
- [MEDIUM] Optional pre-connect TrustScore signal for MCP servers? (https://github.com/continuedev/continue/issues/13345)
  - symptom: continue lets users wire in MCP servers as tools, which raises a before-you-connect question: can we show how trustworthy a given MCP server is first? there's a public TrustScore for ~19.7K MCP server
  - workaround: none stated
- [MEDIUM] VS Code agent cannot capture terminal output in WSL workspace (https://github.com/continuedev/continue/issues/13335)
  - symptom: Windows with WSL2 (Ubuntu) VS Code opened from a WSL directory using code 
  - versions: 2.0.0, 1.140.0
  - error: `Continue VS Code extension installed under both Local and WSL: Ubuntu`
  - workaround: none stated
- [MEDIUM] Add service-specific Ace media MCP entries to official examples (https://github.com/continuedev/continue/issues/13395)
  - symptom: Users look for Suno, Seedance, HappyHorse, GPT Image and Nano Banana by service name
  - error: `Users look for Suno, Seedance, HappyHorse, GPT Image and Nano Banana by service name. Current Continue source removed Hub package/slug loading, so a local MCP f`
  - workaround: none stated
- [MEDIUM] Registry entry `dev.continue/docs` points at a docs-site path, not an MCP server (https://github.com/continuedev/continue/issues/13051)
  - symptom: I probed every remote endpoint advertised in the official MCP registry (10,513 of 10,542 reached)
  - versions: 2.0, 14.4, 12.2
  - error: `POST https://docs.continue.dev/mcp -> 405`
  - workaround: none stated
- [MEDIUM] Docs scope question: Arcmira remote MCP example (https://github.com/continuedev/continue/issues/13352)
  - symptom: Would a concise Arcmira remote-MCP configuration example fit the existing Example MCP Servers page? I am Arcmira's founder
  - error: `Would a concise Arcmira remote-MCP configuration example fit the existing Example MCP Servers page?`
  - workaround: none stated
- [HIGH] CLI: runTerminalCommand "should handle non-existent commands" intermittently hangs to vitest's 30s timeout on windows-la (https://github.com/continuedev/continue/issues/13273)
  - symptom: I've tried finding an answer on the Continue docs site I'm not able to find an open issue that reports the same bug I've seen the troubleshooting guide on the Continue Docs src/tools/runTerminalComman
  - error: `extensions/cli, vitest, windows-latest GitHub runner`
  - workaround: none stated