Move from Sourcegraph Cody to Continue

Take it out

1. 1

   Step 1

   Read the end date, and do not wait for an export button

   Dan Adler's November 9, 2026 post says Sourcegraph Cody reaches end of life on January 31, 2027. The post tells customers to contact their Sourcegraph account team. It says Deep Search and Sourcegraph's MCP integrations can cover some code-understanding workflows, and that they are not one-for-one replacements. It does not describe an export, a file format, or a date when chats are deleted. This guide did not find a Cody export in the docs checked the next day.

2. 2

   Step 2

   Copy the prompts and the ignore list while you can still open Cody

   The Cody docs describe a prompt library and repository context filters. Nothing in the end-of-life post says those move. If a prompt still matters, copy the text into a file you control. Write down any repository you had excluded. Chat history is not part of a documented download. Do this while the account still signs in. The post does not set a cutoff before January 31, 2027.

3. 3

   Step 3

   Leave the code where it already is

   Cody does not take the repository with it. The code stays in GitHub, GitLab, or whichever host you already use. Continue edits that checkout. There is no Cody-to-Continue importer in the Continue docs checked for this guide.

Put it in

1. 1

   Step 1

   Install the final Continue release

   The Continue README, checked November 10, 2026, says 2.0.0 was the final release of the VS Code extension, the CLI, and the JetBrains plugin, and that the repository is read-only. It links the VS Code marketplace item Continue.continue, the Open VSX listing, and the npm package @continuedev/cli. The docs call the CLI cn. The same README recommends the CLI instead of the JetBrains plugin. The homepage says Cursor acquired Continue and that the codebase remains available. This guide did not run an install.

2. 2

   Step 2

   Point autocomplete at a model you control

   The autocomplete guide shows a config entry with a provider, a model name, and the autocomplete role. One example is Codestral through the Mistral API, which needs that provider's key. Another is Ollama on the same computer, with ollama run qwen2.5-coder:1.5b and a matching config block. The guide says a huge chat model is a poor fit for autocomplete. Continue does not include Cody's models. We have not checked the provider prices.

3. 3

   Step 3

   Recreate one prompt, then the ignore list

   The prompts guide says a markdown file with invokable set to true becomes a slash command in Chat, Plan, and Agent mode. Paste one Cody prompt there if you still want it. The codebase doc, which marks @Codebase as deprecated, says a .continueignore file uses .gitignore rules to keep files out of the index. That is a file list, not Cody's switch to drop a whole repository. Copy only the paths you still mean to hide.

What you lose

• Nothing imports the Cody account

  Continue does not open Cody chats, Cody prompts, or Cody context filters. A new chat starts empty unless you paste what you saved.

• The project is frozen

  The README says the repository is no longer maintained and is read-only, and that 2.0.0 was the final release. Bugs after that release do not have a Continue team shipping a fix. Cursor's homepage is a separate paid editor. The acquisition is not a migration of your Cody settings into Cursor.

• Autocomplete is a second model

  The autocomplete guide treats completion as its own model role. If you only configure a chat model, the guide's own troubleshooting says completions may not appear. Turn off another completion plugin, such as Copilot, if both try to draw inline suggestions.

• Repository filters do not survive

  Cody's feature reference includes repo-based context filters on the IDE clients. Continue's .continueignore file is a list of paths for the index. An admin switch that drops an entire remote repository is not in the Continue pages checked here.

• January 31 is the end, not a documented export deadline

  The post does not tell you to finish an export before a date earlier than the end of life. Sign-in can still fail before January 31, 2027 if the account team turns a seat off. Copy what you need while Cody still opens.