Skip to main content
AI Choice Engine
← All setup guides

Continue · Setup guide

How to set up Continue

Continue's README declares a final 2.0.0 open-source release and a read-only, unmaintained repository after Cursor acquisition. CLI, VS Code and JetBrains surfaces support agent workflows. Verify the installed release and provider configuration; older account-login docs conflict with the final release's removal of authentication.

Continue

editor plugin · checked October 2, 2026

~10 minBeginner
Start installOpen ContinueCompare itBuyer guide

The “Open Continue” link goes to the vendor site. It is not an affiliate-tracked link on this page — no commission is claimed for that click. Affiliate disclosure.

Before you begin

  • VS Code for the extension, or the Continue CLI cn; maintainers recommend the CLI instead of the JetBrains plugin. The npm CLI path requires Node.js 20+, while the shell installer bundles a runtime.
  • An API key for at least one model provider (or a local model server such as Ollama).
  • A project folder you can open safely.
  • The current repository is read-only and no longer actively maintained. Verify provider compatibility and hosted features; acquisition does not itself establish a dated cloud shutdown.

Authentication

Provider API keys via Continue UI or ~/.continue/.env secrets

Account: Model provider account and API key (or local Ollama)

For IDE secrets, use ${{ secrets.KEY }} in config.yaml: resolution is workspace .env, workspace .continue/.env, global ~/.continue/.env, then process environment. A shell export is available to the CLI, not independently launched IDE extensions. Native provider ollama uses port 11434 without a required /v1 suffix; provider lmstudio defaults to localhost:1234/v1. The final README removes account auth, while CLI docs still describe login; use explicit local config and verify the installed version.

Install or open it

1. Get the harness ready

These steps are written for beginners. On Mac, Terminal is the black/white text window where you type commands. On Windows, use PowerShell or Terminal. Use the OS tabs to hide steps that are not for your computer, then copy one command at a time.

  1. 01

    Choose the documented Continue surface

    Official pages confirm Cursor acquisition and the final stable 2.0.0 release. The README says read-only/unmaintained, while GitHub's archived flag is false and a 2.1.0 VS Code prerelease is also listed. Confirm stable versus prerelease installation; these facts do not establish a dated shutdown of every hosted service.

    Continue homepage
  2. 02

    Open VS Code

    Launch VS Code from Applications (Mac) or the Start menu (Windows).

  3. 03

    Open Extensions

    Mac

    Press ⌘ + Shift + X (or click the Extensions icon).

  4. 04

    Open Extensions

    Windows

    Press Ctrl + Shift + X (or click the Extensions icon).

  5. 05

    Install Continue from the Marketplace

    Search for Continue and install the extension published by Continue (Continue.continue). Drag the icon to the right sidebar if you prefer chat on the right.

    Continue install docs
  6. 06

    JetBrains path (optional, demoted)

    Settings → Plugins → Marketplace → Continue → Install → restart. Maintainers recommend the Continue CLI (cn) beside JetBrains rather than relying on the plugin alone.

    Continue install docs
  7. 07

    Not the default: GitHub CLI install script (last resort)

    Do not start here. Marketplace installs the IDE extension; this official script installs the separate CLI. The command is cn, not continue. `npm install -g @continuedev/cli` remains an alternate.

    bash
    curl -fsSL https://raw.githubusercontent.com/continuedev/continue/main/extensions/cli/scripts/install.sh | bash

    You should see: The installer finishes without an error. Open a new terminal before the verify step so PATH updates apply.

    If this fails
    • The install command errors, or the next verify step says “command not found”. Re-run the official install command with network access, then open a brand-new terminal window before verifying.
    Continue CLI quickstart
  8. 08

    Verify the Continue CLI

    Confirm the CLI is on PATH before using it beside JetBrains or from a repository folder.

    bash
    cn --version

    You should see: A version string. Open a new terminal or check npm’s global bin directory if the command is missing.

    If this fails
    • cn: command not found after install. Open a new terminal so PATH updates. Confirm the installer directory (often ~/.local/bin or npm’s global bin) is on PATH, then re-run the Marketplace or last-resort CLI install. A missing binary is an install/PATH problem, not an API-key problem.
    Continue CLI quickstart

Repository or project

2. Start in the right place

Keep the first repository small, clean, and easy to roll back while you learn the harness’s permissions and context model.

  1. 01

    Open your folder

    File → Open Folder and pick a practice project.

  2. 02

    Open Continue and add a model

    Click the Continue icon and select an explicit local config.yaml. For native provider ollama, match the model tag and use a reachable port-11434 endpoint without adding /v1. LM Studio's documented provider uses port 1234/v1. Review Chat, Plan and Agent mode and its tool policy before permitting writes.

    Continue FAQ — secrets

First run

Chat and explain only

Use this task to test the workflow before handing over a larger repository or production responsibility.

  1. 01Highlight a small function and ask Continue to explain it in plain language.
  2. 02Ask for a suggested improvement without applying an edit.
  3. 03Only then try an inline edit on a comment or docstring and review the diff.

Why this is safe: Continue’s chat/explain loop teaches context selection before agentic edits change behaviour.

Stop and review if

  • Autocomplete or agent mode starts rewriting large files without a clear diff.
  • API keys are written into a committed config file.
  • Local Ollama models are referenced but ollama serve is not running.

The operating boundary

Privacy, data, and cost

The setup is incomplete until you know what the harness can see, what account pays for it, and who approves a risky action.

Privacy

Prompts go to the configured provider or local server, whose training/retention terms apply. The final 2.0.0 README says anonymous telemetry was removed; this is release-specific and does not prove older builds or every extension has identical behavior. Provider data use is separate.

Training on code: tier dependent

Depends entirely on the configured providers or local models.

Sensitive repos: Use local models for sensitive code when possible; otherwise scrub secrets and confirm provider terms.

Pricing

The Continue extension remains free OSS; you pay providers or run local models. Current hosted-product pricing and availability were not established by the captured acquisition/repository pages.

Model: usage based

Watch out: Misconfigured autocomplete models can quietly generate large billable traffic.

Estimate a seat stack

When setup goes wrong

  • cn: command not found after install.

    Open a new terminal so PATH updates. Confirm the installer directory (often ~/.local/bin or npm’s global bin) is on PATH, then re-run the Marketplace or last-resort CLI install. A missing binary is an install/PATH problem, not an API-key problem.

  • Continue installed but never responds.

    Confirm a model is selected, the API key is in ~/.continue/.env (not only a shell export), and restart the IDE after changing secrets.

  • Hub marketplace blocks or Continue account login fail.

    Check the current service status, account access and docs. A login failure alone does not establish a service shutdown. If using manual models, follow the current provider configuration docs.

  • You expected an autonomous agent like Cline.

    Continue supports Agent mode with edit/terminal tools, Plan mode with read-only tools, and Chat without tools. Check tool-use capability and policy on the selected provider. The final upstream is unmaintained, so assess compatibility and maintenance before adopting it.

  • JetBrains plugin missing after install.

    Restart the IDE, enable the Continue tool window, or use the Continue CLI (cn) as the supported JetBrains-adjacent path.

  • Local Ollama models never appear or hang.

    Verify the local endpoint and exact model tag. Use native provider ollama at port 11434 or lmstudio at localhost:1234/v1; a generic /v1 suffix is not required for Ollama. Continue resolves IDE secrets from documented .env files; the CLI can also use process environment variables. Reduce configured context if the exact local model exceeds available memory.

Next steps

After the first successful run

Keep the pilot small, then compare surfaces and budget before a team rollout.

Compare harnessesBuyer guideLocal LLM coding setupOpen-source agents hubAI stack cost calculatorGPU inference (rent)Local GPU sizingBuyer guidesLocal open-source AI guide

Setup details change quickly. The page was checked October 2, 2026; use the official source below before installing in a managed or production environment.

Continue install docsCompare all harnesses