Continuity Ultimate
Memory that belongs to your code — not your model.
The Problem
You have explained your architecture to Claude four times this week. Copilot just suggested the exact pattern you rejected last month — and you spent twenty minutes remembering why. Your AI assistant burns tokens rediscovering context, contradicts past decisions, and leaves no trail when things break.
This is not a model problem.
It is a memory problem.
AI assistants forget everything when the session ends. Architectural decisions, constraints, and context vanish. You are not just losing productivity — you are losing control.
The Solution
Continuity creates synthetic memory — a persistent, local-first AI context layer that remembers architectural decisions and feeds them back to Claude, Cursor, or Cline automatically.
Stop re-explaining your codebase.
Start building.
Why This Is Different
Decisions are stored in your repo — not in chat history, not in vendor-managed memory. Your .continuity/ folder travels with your code.
Works with your AI tools today — native MCP integration lets Claude Code, Cursor, and Cline read and write decisions without copy-paste.
Core Capabilities
Persistent Decision Memory — Log architectural decisions once; AI recalls the why across sessions
Code-Linked Context — Bind decisions directly to code locations so AI understands changes in context
Seamless AI Handoff — Auto-generate session context with delta tracking for any MCP-compatible tool
Synthetic Memory Control — Own institutional knowledge locally with zero telemetry and full portability
Continuous Context Sync — Surface decision debt as architecture evolves
What Is Synthetic Memory?
AI sessions are stateless by default. Context evaporates when the tab closes. Some vendors offer "memory," but that state lives outside your control with unclear retention and no auditability.
Synthetic memory inverts this model.
Continuity persists architectural decisions as structured, versioned state inside your repo. You control retention, audit changes over time, and delete state without vendor coordination.
This is owned state for your codebase — not convenience memory for a model.
Privacy & Ownership
100% local. Zero telemetry. Your decisions never leave your machine unless you commit them yourself.
- No cloud dependencies
- No vendor lock-in
- Full git integration
Free vs Pro
Start free with 10 decisions. Verify your email for 5 more. Upgrade for unlimited.
|
Free |
Pro |
| Decisions |
10 (15 w/ email) |
Unlimited |
| MCP Integration |
✓ |
✓ |
| Semantic Search |
✓ |
✓ |
| Code Intelligence |
— |
✓ |
| Team Features |
— |
✓ |
| Pricing |
$0 |
From $15/month |
Pro Plans:
- Monthly: $15/month
- Annual: $139/year (save 23%)
- Lifetime: $399 one-time
Upgrade to Pro →
Get Started
- Install from the VS Code Marketplace
- Setup → Command Palette →
Continuity: Setup MCP
- Log decisions — your AI remembers the rest
Works With
- Claude Code
- Cursor
- Cline / Roo
- GitHub Copilot
- OpenAI Codex
- Google Gemini
- Any MCP-compatible AI tool
What's New in v2.5.5
Decision Coverage Auditing (v2.5.5)
audit_decision_coverage tool — compares git commits against logged decisions to find gaps- Startup coverage checks — MCP server scans recent commits on every session start and reminds you about unlogged decisions
- Auto-draft decisions — optionally create draft decisions from uncovered commits with a single flag
- Progressive disclosure memory — context is delivered in layers instead of dumping everything at once, reducing token waste
Background Mode & Git Integration (v2.5)
- Silent operation — Continuity runs in the background with zero interruptions
- Git commit detection — auto-detects commits and reminds you to log related decisions
- Persistent decision reminders across sessions
Multi-Agent Support
- Agent-specific instruction files — AGENTS.md (Codex), CLAUDE.md, .cursorrules, copilot-instructions.md, GEMINI.md
- Tuned per agent — imperative style for Codex/Copilot, suggestive for Claude/Cursor
- OpenAI Codex integration with terminal detection and fallback config
- Full process lifecycle management on Windows (wmic/PowerShell + taskkill)
- Zombie and orphan MCP process cleanup now works on Windows
- Cross-platform signal handling and temp directory resolution
Security & Reliability
- 35 advanced security detection types including multi-turn manipulation, TOCTOU race conditions, and covert channel detection
- 620+ security tests across ~5,500 lines of security code
- Hardened stdio bridge lifecycle for background operation
- SIGPIPE and broken pipe handling to prevent zombie processes
Previous (v2.3)
- Fluent AI Memory — auto-generated instruction files, first-call context injection, pattern-based reminders
- Fixed semantic search cosine similarity scoring
- MCP Tool Profiles — Core (12), Standard (29), or Full (92) tools
Documentation
Support
Memory that belongs to your code — not your model.
