Codebases are growing and changing faster than ever, but the problem of maintaining systems - old and new - is not going away for codebase owners. If anything, it is becoming more important than ever. Today, we're taking the next step to meet this new era of software development with Agentic Batch Changes, available now in Beta: the frontier agent for code change at scale, built on technology designed for the world's largest codebases.

We are removing the need to manually manage your context window limits!

Compaction runs in the background, so there is nothing new to configure or learn. Keep asking follow-up questions, and Deep Search will make room when older conversation history starts to crowd the context window.

Deep Search can now use a dedicated subagent specialized for finding files relevant to your query in case a specific code domain needs to be researched. This subagent performs scoped searches and presents a summary to the main agent. Since the main Deep Search agent only needs to read this summary, this saves tokens in its context window.

This means Deep Search can explore more of your codebase while using fewer tokens, so you get more focused context and longer conversation. We expect this feature will significantly alleviate issues with deep single-question research - for multi-question, we just shipped auto-compaction.

Deep Search conversation history now has a Shared with me tab. It lists conversations you opened from a shared Deep Search link, separate from conversations you created yourself.

From the shared list, you can reopen, export, fork, or remove a conversation from your shared history without deleting the owner's original conversation.

Administration on Sourcegraph has historically been an all-or-nothing decision: either a user was an administrator and could do everything, or they weren't and couldn't access any admin surface. We've replaced this with a set of fine-grained RBAC permissions that map onto distinct admin responsibilities. Now you can grant users exactly the access they need and nothing more.

Eight new permission namespaces are available in the role editor (Site admin → Users & auth → Roles), each grantable independently to any role.

We are introducing a new compare page for viewing changes between two revisions.

Deep Search has always been good at finding and explaining code. It can now also count, rank, and aggregate it without blowing up the context window.

A new sandboxed scripting tool lets the agent run programmatic aggregations across many searches in a single turn. Questions that don't fit into a single query, e.g. top-N rankings, cross-search joins, distributions across many files, can now be answered end-to-end, with every underlying search still cited so you can verify how the answer was assembled.

When precise code intelligence is available, you now get a summary of the meaning of the symbol, and usage of the symbol across the codebase. In combination with the precise code intelligence hover information, this often saves the need to jump to a symbol and back which interrupts the flow of reading, and simplifies understanding complex codebases. Linked citations can even serve as an alternative to traditional code navigation.

Search contexts are used to scope searches in code search. Now, you can do the same for Deep Search to guide the response to a specific domain. The users default search context is pre-selected.

Deep Search can now search Git tags, ancestry, and commits on any branch to pinpoint where a change lives in your Git history.

For example, ask Deep Search: "In Kubernetes v1.29, a regression was introduced where the apiserver_watch_events_sizes metric stopped reporting total outgoing watch event traffic. How many versions shipped with the bug before it was resolved?"

You can now rename your Deep Search conversations to keep your workspace organized! Click directly on the conversation title to edit it inline, or use the rename option from the conversation's options menu.

While syncing individual changesets was already possible, Batch Changes now supports syncing changesets as a bulk action. For batch changes with hundreds or thousands of changesets, this means you can refresh the state of all changesets from the code host in a single click—without having to load and sync each one individually.

This is especially useful when changesets have been updated externally (e.g., merged or closed on the code host) and you want Sourcegraph to reflect the latest state immediately across the entire batch change.

Batch Changes now supports OAuth-based authentication for GitHub, joining the existing support for GitLab, Bitbucket Server, and Bitbucket Cloud. Users can now authorize Batch Changes to act on their behalf using OAuth instead of manually creating and pasting personal access tokens.

When adding a credential for a GitHub code host, users will see a new OAuth option in the authentication strategy dropdown. Clicking through initiates a standard OAuth flow that automatically provisions the credential with the correct scopes.

In Code Search, you can now describe what you're looking for in plain English — press # in the search bar to activate query assist, type something like TODO comments in python files or what did alice work on last week?, and our custom-trained model will translate it into a precise Sourcegraph search query.

Use Deep Search to create architecture diagrams, technical documentation, or research summaries, then export and share them with your team.

As previously announced, the default Sourcegraph MCP endpoint at /.api/mcp now exposes a smaller, more focused set of tools for common context-gathering workflows.

This reduces tool-list noise for MCP clients and avoids spending context window budget on lower-frequency tools that most agents do not need by default.

Batch Changes now supports OAuth-based authentication for Bitbucket Server and Bitbucket Cloud, joining the existing support for GitHub and GitLab. Users can now authorize Batch Changes to act on their behalf using OAuth instead of manually creating and pasting personal access tokens.

When adding a credential for a Bitbucket Server or Bitbucket Cloud code host, users will see a new OAuth option in the authentication strategy dropdown. Clicking through initiates a standard OAuth flow that automatically provisions the credential with the correct scopes.

If your organization makes use of multiple Slack workspaces, or Slack Enterprise Grid, you may want Sourcegraph to act as the central code understanding platform where anyone across your organizations can use Sourcegraph to understand your entire codebase.

The Sourcegraph Slack integration now supports connecting any number of Slack workspaces, including Enterprise Grid workspaces, to the same Sourcegraph instance - enabling your Slack users to ask @Sourcegraph questions about your codebase directly in their Slack workspace and get Deep Search answers.