Comparison · Nov 2026

Limitcode Pro vs Continue

Continue proved that developers wanted an open, model-agnostic coding agent with BYOK keys, MCP servers, and local models — before Cursor acquired the project in June 2026. If you loved that philosophy and work in Sublime Text 4, here is how the two actually compare.

Short answer

Continue was an Apache 2.0 extension for VS Code, JetBrains, and its CLI (cn) — it never supported Sublime Text, and its official GitHub repository became read-only in mid-2026 after Cursor's acquisition and Hub shutdown. Limitcode brings that same bring-your-own-key, local-model, and MCP philosophy directly into Sublime Text 4, actively maintained as both open-source Limitcode OS and the packaged Limitcode Pro agent.

01 — At a glance

The short version.

Aspect Limitcode Pro Continue (Continue.dev)
What it is An active AI coding agent built natively inside Sublime Text 4 An open-source AI assistant (VS Code, JetBrains, CLI) archived in mid-2026 after Cursor's acquisition
Project status Actively maintained (Limitcode OS & Limitcode Pro) Repo read-only since June 2026; hosted Hub shut down after v2.0.0
Sublime Text support Native, first-class (builds 4050+) None — targeted VS Code, JetBrains, and cn CLI
Agent & tool model Tool-calling agent with native diff view, LSP diagnostics, MCP & subagents Agent mode, chat, inline edit, tab autocomplete & MCP (in VS Code / cn CLI)
Provider model BYOK across 40+ providers, Copilot/Codex/Antigravity sign-in, Ollama & LM Studio BYOK (OpenAI, Anthropic, Gemini, local Ollama, etc.)
Recovery & safety Per-edit file snapshots (Ctrl+Alt+U / Shift+R) + permission rules Editor checkpoints / git + tool approval prompts
Pricing Free open-source Limitcode OS, or one-time $29 Limitcode Pro license Apache 2.0 open source (paid Hub tiers shut down post-acquisition)
02 — The contender

What happened to Continue in 2026?

Continue earned huge goodwill among developers because it refused vendor lock-in: you could plug in Anthropic, OpenAI, Gemini, or local Ollama models inside VS Code or JetBrains, wire up MCP tools, and run chat, inline edits, tab autocomplete, or agent mode on your own keys.

In June 2026, Cursor (Anysphere) acquired Continue. Following the acquisition, Continue's hosted cloud services (Continue Hub) were shut down and the official continuedev/continue repository was frozen as read-only after a final v2.0.0 release with telemetry and authentication stripped out.

For Sublime Text developers, there was an even simpler blocker from day one: Continue's IDE architecture targeted VS Code's webview API, JetBrains plugins, and the cn terminal CLI. Sublime Text was never supported.

03 — The native alternative

What is Limitcode Pro?

Limitcode Pro is an actively maintained coding agent built natively for Sublime Text 4 (builds 4050+). Instead of running an Electron webview or asking you to leave Sublime, it lives inside Sublime's Python 3.8 plugin host with zero background daemon when using direct API keys.

It shares the exact model-ownership philosophy Continue pioneered: bring your keys across 40+ providers (OpenAI, Anthropic, Gemini, DeepSeek, OpenRouter, Mistral, Groq, xAI), sign in with eligible GitHub Copilot, OpenAI Codex, or Google Antigravity accounts, or run offline with Ollama, LM Studio, or LiteLLM.

04 — Architecture & agent tools

Same BYOK spirit, built around Sublime's buffers.

Developers migrating away from Continue often look closely at how the agent tool loop works: reading project files, applying clean diffs (edit_file / write_file), running commands, and gating destructive actions behind clear permissions.

Because Limitcode lives inside Sublime Text rather than a webview sidebar or standalone terminal, those tool calls integrate directly with editor primitives:

Editor-aware context

Highlight any unsaved snippet or function and hit Ctrl+Alt+A (Send to Agent) to pass it into the active conversation without saving or copy-pasting.

Native diffs & snapshots

Proposed file changes open in Sublime's native diff view (Accept / Reject), and every touched file gets a pre-edit backup so Ctrl+Alt+U undoes agent changes cleanly.

LSP loop & Agent Skills

Sublime's LSP diagnostics feed errors straight back to the agent after edits. You can extend behavior with AGENTS.md rules, .agents/skills, MCP servers, and focused subagents.

05 — Feature by feature

Side by side.

Feature Limitcode Pro Continue (v2.0.0 Archive)
Native Sublime Text 4 support ✓ —
Actively maintained in late 2026 ✓ —
VS Code / JetBrains extension ✓
Bring your own API keys (BYOK) ✓ ✓
Local models (Ollama, LM Studio) ✓ ✓
MCP servers ✓ ✓
Multi-step agent tool loop (read, edit, shell) ✓ ✓
Inline tab autocomplete (ghost text) ✓
Send unsaved selection with one shortcut (Ctrl+Alt+A) ✓ —
Native Sublime diff review + snapshot undo/redo ✓ —
Sublime LSP diagnostics fed back to the agent ✓ —
Open-source core + one-time Pro license ✓ Apache 2.0 archive
06 — The honest verdict

Which one makes sense now?

Continue v2.0.0 still works if…

  • You already work in VS Code and want a frozen, telemetry-free Apache 2.0 extension.
  • You rely heavily on inline ghost-text tab autocomplete inside VS Code.
  • You do not mind maintaining your own fork or living without future model adapter updates.
Active for Sublime Text 4

Limitcode makes sense if…

  • You code in Sublime Text 4 and want an agent that actually lives inside Sublime.
  • You want the same BYOK, local Ollama, and MCP freedom Continue stood for — in an actively maintained tool.
  • You value native diff review, LSP diagnostic feedback, and per-edit undo snapshots.
  • You want to start free with open-source Limitcode OS or get Limitcode Pro with a one-time $29 license.
07 — FAQ

Questions people actually ask.

Does Continue.dev work in Sublime Text?

No. Continue was built for VS Code, JetBrains IDEs, and its terminal CLI (cn). There was never an official Sublime Text plugin. If you want a BYOK coding agent with MCP and local model support inside Sublime Text 4, Limitcode is built specifically for Sublime's Python 3.8 plugin host.

What happened to Continue.dev in 2026?

In June 2026, Cursor (Anysphere) acquired Continue. Continue's hosted cloud/Hub plans were wound down, and the official continuedev/continue repository became read-only (no longer actively maintained) after a final v2.0.0 release that removed telemetry and authentication dependencies.

How do Limitcode's agent tools compare to Continue's?

Both follow a clean, explicit tool-calling philosophy rather than opaque black-box loops. Continue's agent mode used file/terminal tools inside VS Code or the cn CLI. Limitcode provides built-in project inspection, file editing, approved command execution, web search, Agent Skills, MCP servers, and subagents — wired directly into Sublime Text's native diff view, LSP diagnostics, and per-edit backup snapshots.

Is there a free open-source option like Continue for Sublime Text?

Yes. Limitcode OS is free and open source on GitHub for BYOK pair programming inside Sublime Text 4. If you want the full autonomous agent workflow, subagents, MCP integration, and packaged updates, Limitcode Pro is a one-time $29 license (up to 3 devices, no subscription).

Should I switch from Continue v2.0.0 in VS Code to Limitcode?

If you already live in VS Code and only need a frozen Apache 2.0 client against your own API keys or Ollama, Continue v2.0.0 still runs locally. If you use Sublime Text 4 — or want an actively maintained, lightweight native editor agent that is not tied to an archived repo or an Electron IDE — Limitcode is the direct fit.

Own your keys. Stay in Sublime.

Limitcode Pro: an actively maintained BYOK coding agent inside Sublime Text 4, with a one-time $29 license.