Feature removals and deprecations

A lot has happened in the field of software development over the past couple of years. Overnight, LLMs became good enough that actual products could be built on them. Cody was born.

Then, in early 2025 the whole landscape changed again when Anthropic's Claude Sonnet 3.7 was released, and had tool calling capabilities so good that a whole new category of products suddenly became possible. Some problems have quite literally disappeared over night. Some problems, however, did not: what we learned from working with enterprises for the past decade building Sourcegraph, the Code Understanding Platform, is that they face challenges truly unseen in small codebases.

Since the beginning, Sourcegraph has been committed to enabling customers to ship fast and with confidence. With the technology of today, we are better equipped than ever to create some great tooling in this space - for humans and agents alike.

To focus on supporting this mission with all our capacity, and be able to move fast alongside our customers to adapt to the latest technologies as things evolve, we are doubling down on our product direction, and making some changes to directions we have explored in the past:

Cody Web for Deep Search customers

If you are already a Deep Search customer, you probably found yourself staring at the navigation before, trying to decide if you want a Code Search, Chat, or Deep Search. Effectively, Deep Search and Chat (also known as Cody Web) are trying to solve the same problem. Deep Search however can answer much more sophisticated problems, with its deep integrations into the entire Sourcegraph ecosystem; combining code search, code navigation and more.

Thus, Deep Search is replacing Cody in the browser. This does not affect Cody as a coding agent in your editor.

Sourcegraph Own and teams

In early 2023, we started an experiment to solve code ownership. Almost every company has a concept of it, but existing tooling today provides too limited options to work with them. So we set out to sketch out what a proper code ownership tool could look like.

We have decided that this direction from 2023 no longer make sense in 2026. With agents in the mix, ownership is blurrier than ever, and managing that would require a drastically different approach, which we want to revisit in the future. For now, ownership management in Sourcegraph will be simplified:

• The experimental team mapping feature for Own has been removed
• Suggestions for owners has been removed
• Explicit assignment of ownership and uploaded CODEOWNERS has been removed

We continue to support standard in-repository CODEOWNERS files: ownership derived from CODEOWNERS remains available in code navigation, as well as the file:has.owner(...) and select:file.owners code search predicates.

Search Notebooks

Search Notebooks pick up on the idea that most searches are not just one search. In a common workflow, you run multiple searches, gather several pieces of information, and then you compile your final answer from all these sources. Back in 2022, Notebooks solved a real need to be able to document and share that research trail.

Sound familiar? The premise of Notebooks reflect the same steps a Deep Search now takes to compile its answer. Deep Search conversations collect findings and citations in a central place. We believe that the future lies much more in this type of agent-driven code exploration and future iterations of it than the manual Notebooks idea that predates the AI era. With that, we’ve decided to remove Search Notebooks from Sourcegraph: Notebooks can no longer be viewed or created directly in Sourcegraph.

Existing Notebooks can be exported by administrators in Administration → Debug console using the notebookExports GraphQL query, available in Sourcegraph 7.0:

query { notebookExports(...) { ... } }

Self-hosted deployment options

To provide a world-class experience where we can support our customers in the best way possible, we will focus on our two hugely popular and well-supported deployment methods for Self-hosted Sourcegraph going forward:

• Our official Helm Chart for production-grade, scalable deployments of Sourcegraph
• Our official docker-compose manifests for production-grade deployments of Sourcegraph up to medium size

For that, we are deprecating the following deployment methods, and we plan to eventually stop supporting them:

1. Kustomize deployment method

We also have decided to sunset the following deployment methods:

1. AMI install script
2. AMI
3. Single container “Sourcegraph server”
4. Legacy Kustomize (already deprecated)

Our deployment methods documentation has also been updated with this information. Reach out to your account team if you have questions about migrations. We're committed to making this transition smooth.

We also provide a fully managed solution where Sourcegraph handles all of the maintenance, monitoring, and upgrading tasks to give you an optimal Sourcegraph experience while immediately getting the latest features into your users' hands. We have a well-supported migration process and if you are interested, please reach out to your account team.