Sourcegraph Cody end of life: what to switch to

Quick answer

Sourcegraph Cody reaches end of life on January 31, 2027, under a notice Sourcegraph published on November 9, 2026. The same notice confirms that Amp is independent of Sourcegraph. Sourcegraph itself now centers on code search and context for agents. So split the decision in three: keep Sourcegraph if you need code search, look at Amp for an agent, and choose Nori when a whole team needs agents in Slack, on schedules, with shared memory and any harness, Amp included.

What Sourcegraph announced

These facts come from Sourcegraph's notice, Sunsetting Cody and the future of code intelligence, and its pricing page, both read on November 11, 2026.

• Cody's end of life is January 31, 2027. The notice is dated November 9, 2026.
• Amp is independent. The notice confirms it. Buying Amp is a separate decision with a separate vendor, not a renewal of Cody.
• Sourcegraph now emphasizes code context and search for agents. Its Enterprise plan starts at a $16,000 annual contract and is offered as single-tenant cloud or self-hosted.

What the pages we read do not establish: whether Cody seats convert to anything, what happens to Cody features between now and January 31, and whether any Cody configuration can be exported. Ask your Sourcegraph account team and get the answer in writing.

Three jobs, three different answers

Teams used an assistant like Cody for more than one thing. The end of life is a good moment to name each job and replace it on purpose.

Finding and understanding code across many repositories

This job stays with Sourcegraph if you want it to. Code search and context for agents is what Sourcegraph now leads with, and its Enterprise plan is the product for it. How your plan exposes that context to agents on other platforms is not documented in the pages we read, so ask Sourcegraph which interfaces your contract includes.

An agent that writes the change

This is the job Amp does, as an independent product. As of November 2026 Amp's pages document a free Hobby subscription, an Individual plan at $20 per month with 45,000 hosted-Orb minutes, a team layer at no extra charge, per-minute Orb pricing, and schedules that resume the same thread. Amp also documents subscription reuse, your own keys, and no Amp token fees. The full comparison is in Nori vs Amp Orbs.

An agent the whole team shares

This is a different job from either of the first two, and it is where Nori fits. Requests arrive in Slack from engineers, product and support. Cron schedules and webhooks start the same sessions. An org skillset and shared memories mean every session knows how your team ships. Nori runs any harness for this, including Amp, Claude Code, Codex and Gemini CLI, and ships its own teammate, Jiro.

Replacement options compared

Amp's enterprise own-runner billing changes on November 13, 2026, according to its cost docs. If you plan to run Orbs on your own infrastructure, read that page after the change. A wider field is in cloud coding agents compared.

When to choose Amp or stay with Sourcegraph

• Keep Sourcegraph Enterprise if code search across a large estate is the thing your engineers would miss, and a contract starting at $16,000 a year fits. It does not conflict with any agent choice.
• Choose Amp if what you want is one strong agent for individual engineers, with your own model accounts and no token fee from the vendor.
• Choose both if you used Cody mainly as an assistant on top of Sourcegraph search and want the closest like-for-like setup.

When to choose Nori

• People outside engineering should be able to ask for a fix or an answer in Slack and get a pull request back in the thread.
• You have recurring work to automate: CI triage, dependency updates, documentation checks, webhook-driven fixes.
• You want one org skillset and shared memory, not instructions scattered across each engineer's editor settings.
• You do not want the next end-of-life notice to be a migration. On Nori the harness is a setting: run Amp today and Claude Code or Codex tomorrow, with the same Slack threads, schedules and memory.
• You want inference on accounts you already hold, with no token charge from the platform.
• Security wants single-tenant or self-hosted, which is what Sourcegraph Enterprise gave them. Hosted Nori customers get a dedicated, single-tenant control plane and data store, and for Enterprise Nori deploys the full stack, control plane included, into your AWS VPC or Azure VNet, or on-prem.

How to switch from Cody

1. Count real usage. List who used Cody in the last 30 days and for what: questions about code, edits in the editor, or longer tasks. This tells you which of the three jobs you are replacing.
2. Collect the instructions. Gather every prompt, rule and repository note your team wrote for Cody into one file. Start with a plain AGENTS.md in a repository you control.
3. Decide on code search separately. Talk to Sourcegraph about Enterprise if search is the job. Do not let that decision block the agent decision.
4. Stand up the team agent. Start a Nori trial, connect GitHub and Slack, connect your model accounts, and load the AGENTS.md into the org skillset.
5. Replay real questions. Take five questions people asked Cody last month and ask them in Slack. See the example below.
6. Move one recurring chore to a schedule. Pick something a person does by hand each week and give it a cron line.
7. Set an internal cut-off before January 31, 2027. Pick a date in mid-January, announce it, and remove the Cody extension from your managed editor configuration on that day.

Worked example: a Cody-style question, asked in Slack

#eng-help

Dana: @nori where do we validate webhook signatures for the
      payments provider, and is there a test for a replayed event?

Nori: Validation is in services/payments/webhooks/verify.ts
      (verifySignature, called from handler.ts line 41).
      There is no replay test. I can add one that sends the same
      event id twice and expects a 409. Want a PR?

Dana: yes please

Nori: PR: payments#208 (1 test added, suite green).

The answer cites files, and the follow-up is a pull request, not a suggestion in one person's editor. A scheduled version of the same idea: 0 7 * * 1-5 with the prompt List pull requests on main merged yesterday without a linked test change and post them to #eng-quality.

Frequently asked questions

Sources

Vendor pages were read on November 11, 2026. Dates and prices change; check the linked pages before you decide.

• Sourcegraph blog: Sunsetting Cody and the future of code intelligence
• Sourcegraph: Pricing
• Amp: Pricing
• Amp docs: Orb sizes and costs
• Amp docs: Orb automations
• GitHub Docs: Copilot plans
• GitHub Docs: Create automations for Copilot cloud agent
• Cursor: Pricing
• Cursor docs: Self-hosted cloud agent workers