Continue.dev (harness)
OSS in-IDE coding-assistant plugin — supports VS Code and JetBrains. Customisable: any model, any context provider, any slash-command. "Agent mode" added 2024 for multi-step plan + execute. Memory layer = .continue/rules; separate Memory MCP. Built by Nate Sesti and Ty Dunn.
At a glance
- Type
- OSS agentic IDE plugin (VS Code + JetBrains)
- Tier
- T2
- Section
- Agent IDEs & coding harnesses
- Created
- 2023-07
- Latest release
- Continue 1.x rolling
- License
- Apache-2.0
- GitHub
- ~20k★, TypeScript
- Pricing
- Free + paid
- Funding
- $7.5M Seed · 2024-03 (Heavybit, Y Combinator W23)
Taxonomy
- storage
- file
- retrieval
- injection
- persistence
- cross-session
- update
- user-edit
- unit
- document
- governance
- inspectable
- conflict
- human-arbitrate
When to use
Optimised for: model-agnostic in-IDE assistant; Continue Hub shared assistants
Anti-fit: smaller agent capability than Cursor/Cline; UI less polished than Cursor
Pros & cons
Pros
Only major OSS plugin with first-class JetBrains and VS Code parity; "bring your own model" philosophy is unmatched.
Cons
Agent surface is less mature than Cursor / Cline; smaller ecosystem of pre-built rules / assistants.
Claims & capabilities
~20k★ GH; broad IDE support (only major OSS harness with first-class JetBrains parity); $7.5M seed 2024.
Technical surface
- API surface
- VS Code + JetBrains plugins
- Backend storage
- local + Continue Hub (optional)
- Deployment
- Self-host (IDE plugin) + Continue Hub for shared assistants
- Embedding model
- not applicable — not a memory product
- Multi-tenancy
- per-user
- MCP
- native — Continue MCP client
- A2A
- searched not found
- OpenTelemetry
- searched not found
Similar systems
Other agent ides & coding harnesses in the catalog, ranked by inbound references.
- Bedrock AgentCore (AWS) T2
AWS Bedrock AgentCore — managed runtime to deploy + scale + observe agents. Multi-component: Runtime, Identity, Memory, Gateway, Browser, Code Interpreter, Observability. Distinct from Bedrock Agents (older fixed-config product); AgentCore is the 2025 framework-agnostic runtime for any agent (LangGraph, CrewAI, Strands, OpenAI Agents SDK).
- Claude Code (Anthropic) T1
Anthropic's official agentic coding CLI — runs Claude as a long-running coding agent in the developer's terminal. Memory layer = CLAUDE.md (project + user scoped), agent skills, MCP servers. Released GA October 2024; widely adopted as the reference harness for Claude-as-coder. Plan Mode and Compute Use surfaces extend it from coding to broader desktop automation.
- GitHub Copilot (Agent Mode) T1
The original AI coding assistant (Copilot in editor; 2021). 2025 evolved into a full agentic surface: chat, completions, Agent Mode (multi-step), and Copilot Workspace. Backed by Microsoft. Distinct row from Workspace — this row covers the everyday in-editor + agent mode product, Workspace covers the hosted spec-driven workflow.
- Aider (harness) T2
OSS terminal coding agent by Paul Gauthier — one of the original AI-pair-programmer CLIs (2023). Architect/Editor modes; repo-map for context; uses any LiteLLM-compatible model. Memory via CONVENTIONS.md and .aider.conf.yml — author-edited markdown. Distinct from the separate Aider memory-row in "Coding-agent memory"; this row characterises the harness itself.
- Amazon Q Developer T1
Amazon's developer-focused agent — formerly CodeWhisperer (renamed 2024-Q4). Available as IDE plugins (VS Code, JetBrains, Visual Studio, Eclipse), in AWS Console, and CLI. Strong AWS-tooling integration: Q can read CloudWatch, troubleshoot IAM, suggest AWS-SDK code. Companion to Kiro for spec-driven flows.
- Anthropic Computer Use T1
Anthropic's API-surface capability that lets Claude control a virtual desktop — see screenshots, type, click. Launched 2024-10 as a public beta. Not a finished IDE itself; it's the substrate that other harnesses (and Anthropic's own Claude apps) use to operate a computer.
Related systems
References (2)
- Model Context Protocol (MCP spec) depends on at runtime — adjacent-infrastructure cell: any OpenAI-compatible API; MCP
- OpenAI GPT family (GPT-5 / GPT-4o / o3 / o4) depends on at runtime — adjacent-infrastructure cell: any OpenAI-compatible API; MCP