Is Sourcegraph Cody Down?

If Prismix shows Sourcegraph Cody as "Operational" but you're having issues:

• Embeddings index stale or missing — Cody's codebase context feature relies on vector embeddings of your repository files. The index is built incrementally when you first connect a repo and updated on each push. If the indexing pipeline is lagging, Cody answers from stale context or falls back to the LLM's training data. Check the "Cody context" panel in VS Code to see index freshness.
• Context fetching slow on large repositories — Repos with hundreds of thousands of files take longer to build and query the embeddings index. Cody's context retrieval can add several seconds to each chat response on large monorepos. You can improve speed by restricting Cody's context scope to a specific directory using the @ mention syntax in the chat.
• VS Code extension token expired — Cody authenticates with Sourcegraph.com or your self-hosted instance via an access token. Tokens expire based on your Sourcegraph instance's security policy. When expired, Cody shows a red dot in the status bar and refuses to respond. Re-authenticate via the Cody sidebar panel (Command Palette → "Cody: Sign In").
• Self-hosted Sourcegraph connection failed — Enterprise Cody users connecting to self-hosted Sourcegraph need to configure the site URL and a valid admin-issued access token. Common failures include expired TLS certificates on the self-hosted instance, firewall rules blocking the IDE's outbound connection, or the Sourcegraph instance version being older than the minimum required by the current Cody extension.
• Claude or Anthropic backend error in chat — Cody's Pro and Enterprise plans use Anthropic Claude models as the generation backend. When Anthropic's API is degraded, Cody chat returns generic error messages ("Unable to get response from Cody") rather than identifying the upstream cause. Check the Anthropic status page in parallel with Sourcegraph's status page.
• Chat history not syncing across devices — Cody syncs chat history to Sourcegraph.com when you are signed in. If you sign in to Cody in VS Code and JetBrains with different accounts, or if the sync request fails due to a network error, chat sessions appear locally only. Ensure you are signed in to the same Sourcegraph account on all devices and verify network connectivity to sourcegraph.com.