Cody End of Life: Audit Decisions Before You Switch

John Rood··4 min read

Sourcegraph announced Cody's retirement on November 9. Cody reaches end of life on January 31, 2027. Sourcegraph says Code Search remains a core product, including code intelligence for agents through MCP. Its announcement directs affected customers to their Sourcegraph account team for transition planning.

If you are replacing Cody, treat code search and remembered decisions as separate problems. Finding a symbol in your repository proves code access works. It does not prove the replacement can explain a requirement settled in an old conversation.

Before signing off on the switch, inventory the decisions you still need. Give each one a destination and a question the replacement must answer.

Find decisions with no surviving home

Start with one active project. Review the Cody conversations you can still access alongside your issue tracker and architecture records. Look for choices that still constrain the work but never made it into those records.

For each choice, fill out a row like this:

Decision Durable source today Destination Acceptance question
Example: queued exports must finish after account suspension Cody conversation only Reviewed project note What happens to an export already queued when an account is suspended?
Example: the public endpoint keeps its old field name API compatibility document Keep the existing document Which field name must this endpoint return?

The first row needs preservation work. The second already has a source; check that the replacement can read it rather than creating another copy.

A conversation link alone is a weak destination for a retiring product. Preserve the approved decision itself in a place your team controls. Keep the original reference for provenance, but do not make continued Cody access a requirement for understanding the note.

Review the answer before saving it

For a decision that exists only in chat, write a short note with the requirement, its reason, and the person responsible for confirming it. Mark the review date. If the conversation contains a discarded proposal, label it as discarded instead of copying it as an instruction.

Resolve uncertainty with the owner before the note becomes input to another agent. An assistant's earlier suggestion does not establish team approval. Put mandatory implementation constraints in the repository's maintained instructions or design records.

Use MemoryRouter for approved context that should travel

MemoryRouter keeps reviewed decisions in one vault that your replacement agent can recall in every new session. The same vault works with Codex and other MCP clients if you switch again. It is not a code graph, so code navigation stays with Sourcegraph or your agent's own tools. There is no Cody importer. You upload the notes you reviewed.

Install the MemoryRouter CLI, authenticate with a Memory Key for your vault, and upload the approved file:

memoryrouter upload ./cody-exit-notes.md

If Claude Code replaces Cody, MemoryRouter for Claude Code recalls and captures context through lifecycle hooks, so a new session can pull up the uploaded decisions without you pasting them in. Follow the Claude Code setup guide to point it at the same vault.

Make the replacement answer without the old chat

Start a new conversation with your selected replacement. Ask the acceptance question from each inventory row without pasting in the answer. Check the response against the reviewed source, including any exception that changes implementation.

For the export example, an answer that explains account suspension but cancels already queued exports fails the check. Finding the relevant code is not enough. The answer must preserve the approved behavior.

Record a miss against that row, then check whether the note was saved and whether the new tool can reach it.

Sign up for MemoryRouter and upload the first reviewed note before Cody's January 31 cutoff.