Sourcegraph Cody

Verdict: choose Sourcegraph Cody when an enterprise already needs Sourcegraph search and wants an IDE assistant grounded across many repositories. It remains supported for Sourcegraph Enterprise, but it is no longer an individual product: Cody Free, Pro, and Enterprise Starter access ended July 23, 2025. Individuals seeking a $10-style coding subscription should look elsewhere.

Cody combines repository-aware chat, inline completion, auto-edit, shared prompts, and selected code application. Its distinctive decision factor is retrieval: Sourcegraph Search and the code graph can supply context from local and remote repositories while enforcing the user’s existing repository permissions. That makes Cody most credible for questions that cross service or repository boundaries, rather than as another general-purpose autonomous coding agent.

Decision snapshot

Context is the reason to buy it

Cody can use keyword search, Sourcegraph Search, and code-graph relationships to retrieve relevant code. Enterprise users can explicitly add files, directories, symbols, web URLs, and remote repositories with @ mentions. VS Code, JetBrains, Visual Studio, and Cody Web support multi-repository context; the CLI does not.

This is useful for tracing a request across services, locating an internal API’s consumers, or drafting documentation from several repositories. Retrieved files remain inspectable in the interface. For a repeatable investigation process, pair Cody with the unfamiliar-codebase workflow and preserve accepted findings through repository-derived technical documentation.

Retrieval still needs steering. A broad code estate does not fit wholesale into one prompt, and Sourcegraph’s token documentation says limits vary by model and deployment. Administrators can configure larger windows or bring their own model keys, but more context also raises latency and cost. Ask a bounded question, inspect the retrieved sources, and add explicit files or repositories when the automatic set misses a dependency.

IDE assistance, with real client differences

Chat, agentic context fetching, and repository context filters are available across the documented clients. Model selection is available in VS Code, JetBrains, Visual Studio, and Web, but not the CLI. Smart Apply and command execution are VS Code-only in Sourcegraph’s feature matrix. JetBrains lacks symbol mentions; the CLI lacks chat history, explicit file and symbol mentions, multi-repository context, and prompts. Auto-edit requires Sourcegraph 6.0+, Cody Gateway, and Fireworks; self-hosted customers without Gateway receive autocomplete instead.

Cody is therefore a poor fit when the main requirement is unattended issue-to-PR execution. It is closer to a retrieval-backed pair programmer: find relevant code, explain it, suggest a change, then let the developer review and apply it. Compare that fit with the broader AI coding-agent shortlist.

Pricing, limits, and deployment

Sourcegraph’s current Enterprise plan starts at $16,000 as a minimum annual contract and includes pooled credits for AI features. The pricing page does not publish a Cody seat price or universal request allowance. Model Provider quotas, concurrency throttling, and model availability are tied to the Enterprise license, so buyers need a written quote covering expected active users, chat, completions, auto-edit, and overage handling.

The Enterprise plan lists single-tenant cloud and self-hosting. BYOK is supported. Cody Gateway requires outbound access to Sourcegraph’s hosted model service, while self-hosted deployments can configure other providers. Do not treat “self-hosted Sourcegraph” as automatically meaning offline inference.

Privacy and administrative controls

Sourcegraph says Enterprise code is not used for training unless the customer explicitly enables finetuning. Its Model Provider documentation says partner LLMs retain no input or output beyond response generation, while Sourcegraph records rate-limit consumption and high-level diagnostics rather than customer content. Retrieval applies Sourcegraph repository permissions, and admins can enable Cody role-based access controls plus repository context rules.

Those commitments depend on the selected provider and configuration. Review the Enterprise AI terms, deployment path, enabled models, outbound connections, and BYOK agreement before sending proprietary code.

What users report

Community evidence is thin and mixed. Reddit user u/simwai said Cody worked better when they manually selected files and kept the supplied set small. In a retirement discussion, u/proximitysurge missed Cody’s speed for single-file fixes, while u/adampatterson believed the plugin had become difficult to maintain. These are individual reports from public threads, not controlled comparisons or evidence about the current Enterprise release.

Cody is a narrow enterprise choice in 2026: strong when Sourcegraph already indexes the organization’s code and developers need explain-and-edit help across repositories; hard to justify as a standalone assistant purchase.

Sources & further reading

• Sourcegraph Cody documentation
• Sourcegraph pricing
• Sourcegraph Cody plan retirement FAQ
• Cody client feature reference
• Cody context documentation
• Cody chat documentation
• Cody auto-edit documentation
• Cody token limits
• Sourcegraph Model Provider documentation
• Cody model configuration
• Reddit report on Cody context selection
• Reddit report on Cody single-file workflow
• Reddit report on Cody plugin maintenance