Is Continue.dev Down?

If Prismix shows Continue.dev as "Operational" but you're having issues:

• Model provider connection failed — Continue.dev is model-agnostic and connects to whichever provider you configure in ~/.continue/config.json. If the provider (Anthropic, OpenAI, Mistral, etc.) is down or your API key has expired, Continue shows a red error banner in the sidebar. Check your provider's status page alongside Prismix.
• Local Ollama server not running — When using local models via Ollama, Continue connects to http://localhost:11434. If Ollama is not started or crashed, every completion request fails with a connection refused error. Run ollama serve in a terminal to start the daemon.
• Context file too large for the model — Continue sends highlighted code or entire files as context. Files with thousands of lines can exceed the model's context window, causing silent truncation or a 400 error from the provider. Reduce context by selecting only the relevant function or class before triggering a completion.
• Extension not loading in JetBrains IDE — The Continue JetBrains plugin requires JetBrains IDE 2023.1 or later and a compatible JDK. After plugin updates, the IDE sometimes needs a full restart (not just a plugin reload) to pick up the new version. Check Help → Show Log to diagnose plugin initialization errors.
• Keybinding conflicts with other extensions — Continue's default shortcut (Cmd+I / Ctrl+I) is used by many other VS Code extensions. If Continue does not respond to the keyboard shortcut, open the Keyboard Shortcuts editor and search for "continue" to confirm no other extension has claimed the binding.
• Codebase indexing fails on large repos — Continue's codebase context feature indexes your repository using embeddings. On repos with hundreds of thousands of files, indexing can time out or crash the extension host. Exclude large generated directories (node_modules, .git, dist) in config.json under the contextProviders ignore list.