Skill Agents
IDE · Open source

Continue: open-source IDE agent hub

Continue is an open-source extension for VS Code and JetBrains that combines chat, autocomplete, and custom agents defined in `config.yaml`—a lightweight way to package skill-like workflows.

Open Continue

How to set up

  1. 01
    Install Continue

    Add Continue from the marketplace; open the Continue panel in VS Code or JetBrains.

  2. 02
    Configure models

    Add API keys or local model endpoints in config—never commit secrets.

  3. 03
    Add agents to config

    Create named agents with system prompts and allowed tools for one workflow each.

  4. 04
    Share via git

    Store config in the repo (minus secrets) so everyone uses the same agent definitions.

How to use it as a skill agent

  1. 01
    Pick an agent

    Select the agent that matches your task (fix, review, docs) from the Continue UI.

  2. 02
    Provide `@` context

    Reference files, docs, or git diff so the agent stays precise.

  3. 03
    Run slash workflows

    Use bundled commands for repetitive checks your team defined.

  4. 04
    Evolve config

    When output drifts, update the agent prompt or rules in YAML and PR it.

Core capabilities

Config-driven agents

Define agents with prompts, tools, and models in YAML—check into git for team sharing.

Rules & context

Pull rules from files and `@` context providers so each agent stays scoped.

Model flexibility

Run local models (Ollama) or cloud APIs from one extension surface.

Slash commands

Quick-invoke packaged workflows from the chat input—handy for reviews and doc updates.

Typical use cases

Team agent library

Commit `config.yaml` agents for “security review” and “write tests.”

Air-gapped dev

Use local models when code cannot leave the network.

Polyglot monorepos

Different agents per language with rules in each package.

FAQ — Continue

Is Continue free?

The extension is open source; you still pay for cloud model APIs or run local models yourself. There is no vendor-hosted agent runtime like Copilot’s cloud.

How is this different from Cline or Cursor?

Continue emphasizes YAML-defined agents and model choice in an extension. Cline and Cursor ship deeper autonomous agent UX; many teams use Continue for configurable, git-tracked agent presets.

Can Continue use MCP?

Continue’s tool surface has expanded over time—check current docs for MCP or built-in context providers versus pairing with external tools.

Note: Continue config formats evolve—pin extension versions in team docs and read continue.dev/docs when upgrading.