Continuity — Memory that belongs to your code — not your model

Stop losing decisions between AI sessions. Stop watching your AI contradict them when you do.

AI coding tools are stateless. They forget your architecture, your constraints, and your decisions every time you start a new session — and when they do remember, they ignore the parts that don't fit what they're about to write.

Continuity fixes both halves. Local, version-controlled decision records that any model reads — Claude, GPT, Cursor, Copilot, Cline, Gemini — paired with a governance layer that catches it when the AI contradicts what was recorded. Memory + receipts.

---

Who This Is For

• Developers using Cursor, GitHub Copilot, Claude Code, or Gemini
• Teams tired of re-explaining the same context every session
• Anyone building real systems with AI — not just prompts

---

Without Continuity vs With Continuity

Without Continuity	With Continuity
Re-explain decisions every session	Decisions automatically recalled
AI forgets architecture	Architecture stays consistent
Conflicting implementations	Conflicts detected and flagged
Context resets constantly	Context persists across sessions

AI goes from a forgetful intern to a staff engineer with memory.

---

See It In Action

Prefer full quality? Watch on YouTube.

Side-by-side: same codebase, same question, identical AI tool. The only difference is whether Continuity is active.

---

What It Does

Continuity adds a state layer to your AI tools:

• Remembers why decisions were made
• Recalls the right context at the right time
• Prevents conflicting or unsafe actions
• Carries context across sessions and tools

---

How It Works

1. Log decisions as you work — manually, via the continuity CLI, or auto-detected from git commits.
2. Stored locally in your repo — .continuity/decisions.json, committed alongside your code.
3. AI tools recover context automatically via instruction files (CLAUDE.md, .cursorrules, AGENTS.md, GEMINI.md) or optional MCP integration.
4. Only relevant context is injected — no prompt bloat, no wasted tokens.

Local-first. No cloud memory. You own everything.

---

Core Features

Decision Memory

Log once — your AI remembers forever.

Semantic Search

Find decisions by meaning, not just keywords.

Code Intelligence

Link decisions to files, symbols, and changes. Get refactor warnings when touching linked code.

Session Handoff

Resume work without losing context. Auto-generated handoff documents capture deltas between sessions.

Works Across Tools

• Claude Code (CLAUDE.md)
• Cursor (.cursorrules)
• GitHub Copilot (.github/copilot-instructions.md)
• Google Gemini (GEMINI.md)
• OpenAI Codex, Google Antigravity
• Any instruction-based AI assistant

Knowledge Graph

Visualize relationships between decisions with a force-directed graph.

Source Ingestion

Drop documents into .continuity/sources/ and ingest them into your knowledge base with automatic entity extraction and deduplication.

Reports

Generate summaries, comparisons, timelines, and deep-dive analyses from your decisions.

Wiki Health Check

Detect stale decisions, contradictions, orphaned records, and coverage gaps.

MCP Integration (Optional)

Unlock advanced capabilities for MCP-compatible tools:

• Tool interception
• Policy enforcement
• Context injection
• Automation workflows

A full MCP tool suite covers decision logging, search, code intelligence, governance, freshness, reports, and sources.

---

Getting Started

1. Install from the VS Code Marketplace
2. Open your project in VS Code
3. Choose your profile — Continuity supports software, writing, research, medical, legal, and general-knowledge profiles
4. Log your first decision — your AI will remember it next session

That's it — no cloud setup, no account required.

---

Pricing

14-Day Free Trial

• Full Pro access
• Unlimited decisions
• Every feature unlocked
• No credit card required

After the trial, your decisions are preserved (read-only). Upgrade to Pro to keep logging.

Pro Plans

Plan	Price
Monthly	$9 / month
Annual	$89 / year (save 18%)
Lifetime	$199 one-time

Upgrade to Pro

---

What This Actually Is

Continuity is not:

• A note-taking tool
• A prompt helper
• Just another extension

Continuity is:

The state management layer for AI coding tools.

---

Why It's Different

• Local-first — no vendor memory, no cloud dependencies
• Repo-owned — versioned with your code, reviewed in PRs
• Cross-tool — same memory serves every AI assistant you use
• Built for real work — production-grade, not demos

---

If This Helps You

If Continuity saves you time, please leave a review on the Marketplace — it helps others find it.

---

What's New

v3.0.18 — June 2026

Improvements driven directly by field feedback from teams using Continuity in daily AI sessions:

• Honest connection status. Project context responses now reflect the live connection state instead of an older health snapshot — no more "disconnected" warnings inside a clearly working session.
• Session goals always come from the freshest source. When your session notes have just rolled over to a new day, stale goals from an older snapshot no longer appear alongside them.
• Your newest decisions always show up. The project memory file now lists your most recent decisions strictly by date, so the latest work is never pushed out of view.
• Less noise from automatic capture. Auto-captured commit drafts wait in their own review queue instead of crowding your recent decisions, and decisions you've already replaced are marked "ready to archive" rather than nagging for review.
• No more duplicate decisions from imports. Importing decisions from an instructions file now skips anything already in your project memory and reports what was skipped.
• Set several session goals in one step. Updating session notes accepts a list now — no more one-bullet-at-a-time round-trips.
• Decisions logged without tags get smart tags automatically, derived from the technologies and concepts in the decision text, so search and filtering keep working even when tagging is skipped.
• Leaner responses for AI assistants. Context payloads are trimmed (rounded scores, no empty fields, capped lists) so more of the conversation budget goes to your actual work.

v3.0.14 — June 2026

• Decision search finds the right answer for indirectly phrased questions. Asking your assistant something like "is it OK to add quick debug logging here?" now surfaces the relevant past decision instead of returning "no decisions found." In benchmark testing across 141 searches, queries that previously came back empty now return their best matches every time — with the correct decision ranked first.
• Search never strands you on small projects. When a search has no strong match and your project has a modest number of decisions, Continuity returns your full decision history instead of an empty result, so your assistant always has something to work from.
• Setup guides you instead of erroring when no folder is open. Running any Continuity command before opening a folder now shows a friendly prompt with an Open Folder button — previously some commands (including the setup wizard) could show a raw "command not found" error.

v3.0.13 — June 2026

• Smoother session resume. Your recorded decisions and context are now made available to your AI assistant at the start of a session, so you re-explain your project less often.
• File-linked decisions resurface when you work on that file. If a past decision is tied to a file, it's surfaced to your assistant when that file is being changed.
• Optional automatic capture on commit. Commits can be recorded into your project memory automatically.
• Clearer status. Continuity distinguishes "installed" from "active in this session."
• More reliable logging. Decision writes are hardened against duplicates and concurrent edits.

v3.0.11 — June 2026

• Security hardening across the board. A comprehensive security pass strengthened how Continuity handles untrusted content, protects your local decision history and license, and gates automated actions — safer by default.
• Updated dependencies. Refreshed bundled libraries to pick up the latest upstream security and stability fixes.
• Reliability improvements. Quality and test-coverage work behind the scenes for a more dependable experience.

v3.0.10 — May 2026

• Edit the tags on an existing decision. You can now refine how a past decision is categorized without re-creating it — handy for cleaning up or reorganizing your decision history by topic.
• Decisions logged right after a commit reach your task board. When you've connected Jira, Linear, or GitHub Issues, decisions you capture immediately after committing now flow through to the board as expected.
• Leaner project memory file. The project context file your AI assistant loads at the start of each session is now more concise and focused — it loads faster and spends less of the conversation budget on boilerplate.
• More consistent decision tagging. Tags are normalized predictably (case-folded and de-duplicated) so searching and filtering your decisions by topic behaves the same every time.

v3.0.9 — May 2026

• Internal telemetry improvements. No user-facing changes since v3.0.8. This release adds a property to one analytics event so the team can see which AI clients are exercising Continuity in aggregate, helping us prioritize auto-configuration coverage and detection fixes.

v3.0.8 — May 2026

• Your AI assistant connects automatically on install. Continuity detects Claude Code, Cursor, Cline, Roo Code, OpenAI Codex, Gemini CLI, and GitHub Copilot on your machine, then wires up the connection silently — install Continuity, open your AI tool, and the memory layer is already connected. No command palette step, no manual config edit. The AI can call Continuity's memory tools from session one.
• New AI client support: Cline and Roo Code. Both are now auto-detected alongside the existing roster of supported clients.

v3.0.7 — May 2026

• More reliable Setup MCP for HTTP-mode users. If you've opted into the optional HTTP daemon transport, the Setup MCP wizard now writes correctly-discriminated configuration entries for Claude Code, Claude Desktop, Cursor, Gemini CLI, and Antigravity. Stdio mode (the default for almost every install) was never affected.
• Clearer guidance for AI assistants on where project decisions go. The auto-generated project instructions now explicitly tell AI assistants to route project-scoped decisions (architecture, tradeoffs, "we chose X because Y") through continuity log rather than the assistant's private session memory. Cross-project context like user preferences and environment quirks still belongs in private memory, but project decisions belong in Continuity where teammates and other AI tools can see them.

v3.0.6 — May 2026

• Marketplace listing cleanup. README streamlined for clarity — plain text headers, simpler bullets, no decorative glyphs. No functional changes from v3.0.5; the credential-safety improvements and Pro launch shipped in earlier 3.0.x releases.

v3.0.5 — May 2026

Credential safety across the AI workflow. Credential-shaped values that show up in your assistant's context, in conversation memory, in persisted decisions, or in scanned file content are redacted before they leave the boundary or hit disk. Coverage includes Atlassian, GitHub, GitLab, OpenAI, Anthropic, Slack, AWS, Google, Stripe, Twilio, SendGrid, Mailgun, NVIDIA, Perplexity, JSON Web Tokens, private-key blocks, and NAME=VALUE environment-style assignments.

• OS keychain for tracker credentials. continuity tracker connect <provider> now stores Jira / Linear / GitHub Issues tokens in your OS keychain (macOS Keychain, Windows Credential Manager, Linux libsecret) instead of a plaintext file. Existing setups keep working; new connects show [keychain] or [file] so you can see which backend handled it.
• New: continuity credentials migrate. Scans .env, .env.local, and the existing tracker credentials file for credential-shaped values, reports what would move to the keychain, and — with --apply — actually migrates them. Originals are saved as .backup files first. Companion commands: continuity credentials list and continuity credentials clear.
• Redaction across input, output, and persistence. Credentials that appear in tool arguments, model output, persisted decisions / notes / memory, or tool result content are replaced with structured <REDACTED:…> markers. Sub-5 ms on typical payloads, idempotent, and resistant to false positives on UUIDs and hashes.
• One-click audit of existing memory. A new audit surfaces credential hits in your existing decision history and session notes, so anything written before this release can be reviewed and cleaned up.

v3.0.4 — May 2026

• "Test MCP server" reports a meaningful result in both transport modes. The diagnostic button in the Continuity sidebar detects which transport mode you're using and reports the appropriate health check: a list of configured AI clients in stdio mode, or the daemon health probe in HTTP mode.

v3.0.3 — May 2026

• Claude Code CLI is set up on fresh installs. Setup MCP creates the Claude Code CLI config when needed, so brand-new Claude Code users on Windows and elsewhere have Continuity wired up immediately after first install.

v3.0.2 — May 2026

• Setup MCP shows per-tool results. After running Setup MCP from the Continuity Setup Wizard, the notification lists each AI tool individually (Claude Desktop, Cursor, Claude CLI, GitHub Copilot, Gemini CLI, Antigravity, Codex) with its configuration status, so you can see exactly what was configured.

v3.0.1 — May 2026

• Windows install reliability. Fixed an issue where Setup MCP could fail on Windows with a permission error when trying to install the bundled CLI launcher. The launcher now installs to a user-writable location and never tries to write into protected system directories.

v3.0.0 — May 2026

Continuity 3.0 — the paid-Pro launch.

After a long beta, we're moving Continuity into a sustainable paid model. A 14-day Pro trial still ships with every install — full access, every feature, no credit card. When the trial ends, your workspace stays usable in read-only mode (search, view, export everything you've already logged), and a Pro license unlocks writing again.

• All Pro features included in trial. The 14-day trial gives you the same experience as a Pro user: unlimited decisions, semantic search, knowledge graph, code intelligence, native Jira / Linear / GitHub Issues integrations, MCP server, and the full CLI.
• Read-only mode after trial. Your data doesn't disappear when the trial ends. Search, list, and export keep working. New decisions, edits, and integrations require a Pro license.
• Pro pricing. $9/month, $89/year, or $199 lifetime. Activate at app.hackerware.com/pricing.
• Existing trial users: if your trial has already ended on a previous version, this update will move you into read-only mode. Your decisions remain searchable while you decide whether to upgrade.

v2.20.125 — May 2026

• CLI now fires native trackers. continuity log, task, and note push to Jira / Linear / GitHub Issues directly when you've connected credentials — no middleware required. Manage credentials with continuity tracker connect <provider>, tracker list, and tracker disconnect. Tokens live in ~/.continuity/credentials.json with 0600 permissions. CLI-only users now have full parity with the Settings → Integrations panel.
• Comments on existing tickets. continuity note --ticket CO-12 "..." adds a comment to the linked Jira / Linear / GitHub issue. The working ticket is auto-detected from feature/co-12-... branch names or set explicitly via continuity working CO-12.
• Brand font rolled out. Sidebar webview now ships JetBrains Mono via bundled @font-face, ensuring the brand-correct mono rendering everywhere — no system-font dependency.
• Reliability fix for MCP decision logging. Resolved an intermittent issue where logging could fail even with a connected MCP server.

v2.20.122 — May 2026

• Tagline restored. Marketplace subtitle reverted to "Memory that belongs to your code — not your model." No code changes from v2.20.121.

v2.20.121 — May 2026

• Documentation refresh. Release notes streamlined for clarity. No code changes from v2.20.120.

v2.20.120 — May 2026

• Calendar view on the Decisions tab. A month-grid calendar at the top of the panel makes it easier to navigate large decision logs. Days with decisions show a count; click any day to filter the list below.
• Welcome panel telemetry. First-run experience now correctly measures how often users complete setup.

v2.20.117 — May 2026

• Native GitHub Issues integration (Pro). A new Connect GitHub Issues wizard joins Connect Jira and Connect Linear — paste a token, pick a repo, optional default labels, and decisions automatically become issues. No middleware required.
• Disconnect actually disconnects. Native-tracker Disconnect buttons (Jira / Linear / GitHub Issues) now use a proper VS Code modal and clear all state on confirm.
• Google Gemini provider. The Gemini option in the AI Provider dropdown is now fully wired, with a Test connection button to verify your setup end-to-end.
• Settings panel polish. Test connection buttons for AI Provider, MCP daemon, and license server. Section descriptions moved to themed hover tooltips for a cleaner panel.
• Native tracker hardening. Better Jira issue type inference, support for team-managed projects, auto-mapping after Load projects, and decisions auto-transition to Done.

v2.20.98 — May 2026

• continuity webhook CLI command. Configure generic-URL webhook fanout (n8n, Zapier, Make, custom endpoints) from the command line — add / list / remove / test subcommands.

---

Credential Safety

Continuity reduces accidental credential leakage in AI-assisted coding workflows. Credential-shaped values that appear in tool arguments, model output, persisted decisions and notes, or tool result content are redacted before crossing system boundaries.

• 27 provider formats covered — Atlassian, GitHub (full PAT family), GitLab, OpenAI, Anthropic, AWS, Google, Stripe, Slack, Twilio, SendGrid, Mailgun, NVIDIA, Perplexity, JSON Web Tokens, PEM private keys, and env-style NAME=VALUE assignments. Plus a tunable entropy fallback for unknown formats.
• Tracker credentials in the OS keychain — continuity tracker connect <provider> writes Jira / Linear / GitHub Issues tokens to your OS keychain (macOS Keychain, Windows Credential Manager, Linux libsecret) with a file fallback when the keychain is unavailable. Run continuity credentials migrate (dry-run by default) to move any existing plaintext tokens.
• Audit existing memory — the audit_secrets command surfaces credential-shaped strings in your existing decision history so anything written before this release can be reviewed and cleaned up.
• Scope: accidental, not adversarial — this is a hygiene-and-defense-in-depth layer. It reduces the probability of credentials accidentally ending up in long-lived memory. It is not a guarantee, and deliberately-obfuscated credentials, semantic references (e.g. "the production AWS key"), and prompt-injection payloads stored in memory remain open problems. See SECURITY.md for the full scope and threat model.

Privacy

• All data stays local — decisions, sources, and session notes live in .continuity/ in your workspace.
• No cloud storage — Continuity never sends your decisions to any server.
• Anonymous analytics — opt-out via continuity.analytics.enabled: false in VS Code settings.
• Tracker tokens stored in the OS keychain — Jira / Linear / GitHub Issues credentials use the platform keychain by default (file fallback only when keychain is unavailable, with 0600 permissions).

---

Support

• Issues: GitHub
• Email: support@hackerware.com
• Website: hackerware.com