Deep Search is moving out of free research preview

Since its launch in version 6.5, Deep Search has been free to use. Starting October 15, 2025, each Code Search seat will include 3 Deep Searches per month, shared across your organization. Unused searches expire at month-end, and extra usage will incur charges. Contact your AE for pricing details.

GPT-5 brings significant reasoning and coding improvements. IDE support includes: VS Code, Visual Studio, JetBrains, and the web app.

Syntax highlighting for SQL enhances readability, making complex queries easier to scan and understand.

Template variables such as repository.search_result_paths and previous_step.modified_files allow you to chain operations and optimize batch changes by processing only relevant files. The templating engine supports Go's text/template features including conditionals, loops, and custom helper functions, providing programmatic control over changeset generation and execution flow.

This feature is available on Enterprise plans and enables more sophisticated automation workflows for large-scale code modifications.

Inventory Stats, launched last month, make it easy to track how your codebase evolves over time, no search required. We’ve now added support for grouping metrics to help you create cleaner, more focused visualizations.

Grouped charts are especially useful for tracking migrations, understanding repo composition, or comparing multiple teams or projects in one view.

We’ve introduced a new Inventory Stats Code Insight that makes it easy to track how your codebase evolves over time, no search required. This insight complements existing Insights like Track Changes and Language Usage, but brings a more scalable and reliable way to monitor inventory-style metrics across repositories.

With Inventory Stats, you can [...]

Auto-edit, previously available in VS Code, is now rolling out to JetBrains and Visual Studio for Cody Gateway customers. This update enables auto-edit by default - providing inline code edits instead of autocomplete - with the option to opt out.

Enterprise customers can now use OAuth 2.0 to securely connect apps and scripts to Sourcegraph APIs, just like you would with GitHub or GitLab. This includes full support for OIDC, PKCE, device auth, and M2M tokens.

With short-lived access tokens, your tools can act on behalf of users, making it easier to build custom automations and workflows on top of Sourcegraph. If you’ve been blocked from integrating because auth was missing or hard to manage, this clears the path.

Developers increasingly want to work with more context, whether it's reviewing all files in a pull request, generating a new Dockerfile based on all others in a repo, or reasoning across a large set of project resources. But context limits have traditionally capped how much they can reference in a single request, leading to fragmented workflows or lower quality responses.

To help with this, we're expanding both input and output context windows in Cody Chat for Cody Enterprise customers.

We’ve introduced service sccounts, a new way for administrators to create Sourcegraph actors that are designed specifically for API access without UI access or user credentials.

As of July 23, 2025, we will no longer offer the following plans:

• Cody Free
• Cody Pro

We’ve shipped several updates to Sourcegraph Analytics to give you deeper and more flexible insights into how your teams are using Sourcegraph:

Time filters added to the analytics CSV export API

Sometimes you want to automate large-scale code changes without triggering a merge request, like updating internal tooling, modifying generated code, or experimenting with refactors. Until now, Batch Changes always assumed you wanted to open a merge request.

This update introduces a new type of changeset that doesn’t require a merge request. It simply [...]

When using AI-generated steps (like LLMs) in Batch Changes, results can vary run to run. Until now, re-running those steps meant re-executing the entire batch spec. That’s no longer necessary.

You can now re-execute changeset creation logic for individual workspaces, making it easier to regenerate or revise changesets without restarting from scratch.

Anthropic's new Claude 4 models are now available for Cody users, with the following models available for each plan:

Cody Free and Pro:

We’ve added a new option for site admins to set a default search context for all users on their instance. Previously users could set their own default context used when searching their codebase, but this update now allows admins to set this globally.

This helps teams improve onboarding and search quality by focusing searches on the most relevant parts of the codebase, rather than the entire indexed set of repositories.

File and directory filtering has been added to the compare page in Code Search to make large diffs easier to navigate, manage and share. When comparing branches with thousands of changed files, you can now use the file picker to select specific files or directories to focus on. You can also filter files directly by constructing a URL with multiple file paths, or use a compressed file list for even larger selections.

This update gives you much greater control over which changes you view, helping teams review only the files relevant to them without endless scrolling.

Originally announced as an experimental feature, Cody's agentic context gathering is now generally available across all IDEs and the web.

The context gathering experience evaluates the provided context in a prompt, and fetches any additional context (via Sourcegraph search, terminal, etc.) to provide enhanced, context-aware capabilities. It aims to reduce the need to provide context manually, and at the same time improve the quality of prompt responses.

We've added support for service access tokens for Sourcegraph Analytics, enabling admins to programmatically access user-level analytics data without relying on browser-based authentication. These long-lived tokens are tied to individual accounts.sourcegraph.com users and allow customers to pull analytics data into their own systems securely and continuously.

Previously, customers had to manually extract session credentials to automate analytics access - this update eliminates that workaround and supports a more secure, standards-based integration with customer data pipelines.

Note: This page describes how MCP tools are used within Cody.

If you're looking for the Sourcegraph MCP Server (for connecting external AI agents and applications), see: Sourcegraph MCP server.

Cody now supports MCP tools via its agentic context gathering, enabling automated tool use to gather and inject context directly into Cody's responses.