sitdraw

How to install and use Continue in VS Code: extension, config.yaml provider, first Chat/Edit task

Install Continue, wire a provider in config.yaml, Chat read-only on the current file, Edit one reviewable docstring diff.

To finish your first Continue coding task in VS Code, complete four steps: install the Marketplace Continue extension, wire a model provider in config.yaml, run a read-only Chat prompt on the current file, then use Edit on a selection for one reviewable change.

Facts follow docs.continue.dev/ide-extensions/install, docs.continue.dev/customize/model-providers/overview, and docs.continue.dev/customize/deep-dives/configuration. Queries: Continue VS Code install, Continue config.yaml model provider. Continue is an open-source, BYOK IDE assistant (Chat, Edit, Agent, Autocomplete)—not the same UX as Roo Code’s multi-mode agent panel; see our Roo Code guide for that lineage. For a short huddle see sitdraw and create and join a room.

Installconfig.yamlChat → Edit

Chat, Edit, and Autocomplete

Chat

Sidebar conversation with @file / @codebase context. Hour one: read-only questions before Agent mode.

Edit

Generate a patch for the current selection with diff preview before Apply—good for your first write to the repo.

config.yamlModels & roles
Cmd/Ctrl+LOpen Chat
BYOKYour API keys
GoalEntryFirst-hour check
InstallExtensions → ContinueActivity Bar icon; ext install Continue.continue
ProviderContinue sidebar ⚙️ → configA model with roles: [chat, edit] sends messages
Read-only taskChat + @current fileAnswer cites real paths; no surprise file edits
First changeSelect code → EditPreview diff → Accept → git diff

Install, provider, Chat, and Edit

  1. 01
    Install Continue

    Extensions Cmd+Shift+X / Ctrl+Shift+X, search Continue, publisher Continue, id Continue.continue → Install. Marketplace web install also works—confirm inside VS Code. Reload Window. Quick Open: ext install Continue.continue.

  2. 02
    Configure a model provider

    Open Continue (Cmd+L / Ctrl+L) → gear / Configure to edit config.yaml (workspace .continue/config.yaml or user config per UI). Add a models entry with provider, model, and apiKey (prefer ${{ secrets.ANTHROPIC_API_KEY }} env refs—never commit keys). Set roles for chat and edit. Optional: sign in to hub.continue.dev for assistants; BYOK local config is enough to start.

  3. 03
    Chat: first read-only task

    File → Open Folder on the repo. In Chat, @ the current file and ask: “In three sentences, explain this file’s main exports and responsibilities.” Confirm no pending Apply patches.

  4. 04
    Edit: first small change

    Select a small function, run Edit (sidebar or Command Palette—label varies by version): “Add a docstring only; no behavior change.” Preview the diff, Accept, then git diff. Disable competing inline autocomplete (Copilot, Codeium) for hour one if ghost text clashes.

# First hour · Continue · VS Code · 2026-10-20
# ext install Continue.continue · Open Folder workspace
# config.yaml → models[] with provider + apiKey + roles [chat, edit]
# Chat: @file → read-only explain exports
# Edit: selection → docstring only → review diff
# docs.continue.dev/ide-extensions/install
# docs.continue.dev/customize/model-providers/overview
How is Continue different from Roo Code or Cline?
Continue centers on config.yaml + Hub model roles; Roo/Cline are sidebar autonomous agents with Code or Plan/Act modes. For that pattern see Roo Code or Cline.
Chat errors or no model?
Validate config.yaml syntax, apiKey, and model IDs. Remote SSH needs outbound HTTPS to your provider. Reload Window; check Continue logs in Output.
Local Ollama?
Yes—set provider: ollama and the model name per docs.continue.dev Ollama guide.
Whiteboard product?
No—open sitdraw for diagrams.

Config before Chat

Empty replies and 401s usually mean no provider in config or a single-file workspace instead of Open Folder.

Start the picture