Continue

What is Continue?

Continue is an open-source coding assistant that ships as a VS Code extension and a JetBrains plugin. Cursor, Copilot, and most rivals hand you an opinionated stack you cannot fully see into. Continue does the opposite: the model for chat, the model for autocomplete, the model for edits, the context providers, and the slash commands are all declared in a config file you own. That is the entire product thesis, and whether it is a feature or a chore depends on one thing about your team.

The differentiator is the config artifact

Because the stack is a file, it is shareable, reviewable, and enforceable. A team can pin one assistant definition and everyone runs the same models against the same context, instead of ten engineers each on a different tool with different defaults:

# A team-pinned assistant: same models and context for everyone
models:
  - name: chat
    provider: anthropic
    model: claude-sonnet
  - name: autocomplete
    provider: deepseek
    model: deepseek-coder       # cheap model where quality matters least
context:
  - provider: code
  - provider: docs
  - provider: terminal

The autocomplete-on-a-cheap-model, chat-on-a-strong-model split is the move most teams cannot make in a single-model tool, and it is where Continue's cost story actually lives. Continue Hub extends the same idea: assistant configs become shareable artifacts across the org, with paid team tiers adding governance and analytics on top.

Who should pick it, and who should not

Pick Continue if you have the org-fragmentation problem: multiple teams, mixed IDEs, no agreed stack, and a real reason to standardize (cost control, a privacy-driven model choice, a self-hosted model). The config-as-artifact model is the cleanest answer to that specific problem in the category.

Skip it if you are a solo developer or a small team without that problem. The configurability is a setup tax you pay whether or not you need what it buys, and Cursor's opinionated defaults will get a single developer productive faster. Continue's edge is organizational, not individual; bought for the wrong reason it is just a slower start.

Pricing

IDE extensions are free; you bring your own API keys, so model spend is your only floor cost and you control it directly through the config above. Continue Hub has a free tier. Paid team plans add shared assistants, governance, and usage analytics, which matter only once the standardization use case is the reason you are here.