Continue.dev .continue/rules alternatives

.continue/rules/*.md at workspace root, loaded lexicographically; YAML frontmatter name, globs, regex, description, alwaysApply. Continue was acquired by Cursor in June 2026 and the extension is no longer maintained. Full Continue.dev .continue/rules record →

What the maintainers say

Continue was acquired by Cursor (June 2026) and continuedev/continue is no longer actively maintained and read-only after a final 2.0.0 release; no official migration path for .continue/rules is named.

  1. Treat the final 2.0.0 release of the VS Code extension, CLI and JetBrains plugin as the last upstream version
  2. JetBrains users are told to use the Continue CLI instead of the JetBrains plugin
  3. The open-source codebase remains freely available, so teams that rely on .continue/rules can fork it

Sources: continue.dev · github.com · thenewstack.io · checked 2026-10-26

Other live alternatives

  1. 1 AGENTS.md File-backed / editor paradigms

    also in File-backed / editor paradigms · same storage (file) · same retrieval (injection) · same conflict handling (manual) · same memory unit (document) · also open source · also self-hostable

    OSS ✓ Self-host ✓ Managed ? MCP ? ★ 25k MIT Compare with Continue.dev .continue/rules →

  2. 2 CLAUDE.md File-backed / editor paradigms

    also in File-backed / editor paradigms · same storage (file) · same retrieval (injection) · same conflict handling (manual) · same memory unit (document)

    OSS ? Self-host ? Managed ? MCP ? Compare with Continue.dev .continue/rules →

  3. 3 GitHub Copilot custom instructions File-backed / editor paradigms

    also in File-backed / editor paradigms · same storage (file) · same retrieval (injection) · same conflict handling (manual) · same memory unit (document)

    OSS ? Self-host — Managed ✓ MCP ? Compare with Continue.dev .continue/rules →

  4. 4 Aider CONVENTIONS.md / .aider.conf.yml File-backed / editor paradigms

    also in File-backed / editor paradigms · same storage (file) · same retrieval (injection) · same conflict handling (manual) · same memory unit (document)

    OSS ? Self-host ? Managed ? MCP ? Compare with Continue.dev .continue/rules →

  5. 5 Cline .clinerules File-backed / editor paradigms

    also in File-backed / editor paradigms · same storage (file) · same retrieval (injection) · same conflict handling (manual) · same memory unit (document)

    OSS ? Self-host ? Managed ? MCP ✓ Compare with Continue.dev .continue/rules →

  6. 6 Cline Memory Bank File-backed / editor paradigms

    also in File-backed / editor paradigms · same storage (file) · same retrieval (injection) · same conflict handling (manual) · same memory unit (document)

    OSS ? Self-host ? Managed ? MCP ✓ Compare with Continue.dev .continue/rules →

  7. 7 Replit replit.md File-backed / editor paradigms

    also in File-backed / editor paradigms · same storage (file) · same retrieval (injection) · same conflict handling (manual) · same memory unit (document)

    OSS ? Self-host ? Managed ? MCP ✓ Compare with Continue.dev .continue/rules →

  8. 8 Zed .rules File-backed / editor paradigms

    also in File-backed / editor paradigms · same storage (file) · same retrieval (injection) · same conflict handling (manual) · same memory unit (document)

    OSS ? Self-host ? Managed ? MCP ✓ Compare with Continue.dev .continue/rules →

Ranked by shared memory design (storage, retrieval, conflict handling, memory unit), same section and shared must-haves (open source, self-hosting, MCP), with adoption as a tie-breaker. ✓ confirmed · — no · ? not in the catalog yet. Want picks for your own requirements? Use the chooser. Checking a whole project? Check your stack.