Does SnapBack replace Git?

No. SnapBack complements Git by adding AI-aware intelligence that Git doesn't have. Git tracks what changed, when, and in which commit. SnapBack tracks who changed it (AI vs human), why (context, prompts), workspace state, and learned patterns. Think of SnapBack as an intelligence layer on top of version control, not a replacement.

Does my code leave my machine?

No. SnapBack runs entirely locally. The daemon processes and stores data in .snapback/ (gitignored by default). No telemetry, no cloud uploads, no external API calls. Your code, your machine, your control. Optional cloud sync for team learnings is planned as opt-in, not required.

Which AI assistants does SnapBack work with?

Via MCP protocol: Cursor, Claude Desktop, Continue.dev, Windsurf, and any MCP-compatible client. Via extension: Detects AI-generated changes from Cursor, GitHub Copilot, Codeium, and other editor-integrated assistants.

How much overhead does the daemon add?

Minimal. ~50-100MB RAM in typical repos, 10k files), the daemon indexes incrementally.

Can I use SnapBack without the extension?

Yes. You can use the CLI and MCP server standalone: snap daemon start, then snap status, snap analyze src/auth.ts, etc. The extension just provides a nicer UI and automatic daemon management.

Is SnapBack open source?

Open core. Core contracts, CLI, and MCP protocol implementation are open source. VS Code extension and proprietary learning algorithms are closed source. You can audit the architecture and wire format before using.

Currently free during alpha/beta. Future pricing will likely be: Free tier for individual developers (unlimited local use), Team tier for shared learnings and cloud sync (optional), Enterprise for SSO, audit logs, and compliance features. Early adopters get locked-in pricing.

Stop re-explaining your codebase to AI.

SnapBack learns what breaks your code — patterns compound, mistakes don't repeat, and your AI tools get smarter every session.

Install Extension — Free See How It Works ↓

94% accuracyacross Cursor, Copilot & Claude

<50ms overheadinvisible to your workflow

<1s context loadfull intelligence loaded instantly

Local-firstyour code never leaves your machine

auth.ts

src/middleware

Explorer

src

middleware

auth.ts

routes

protected.ts

dashboard.ts

billing

billing.ts

123456789101112

// src/middleware/auth.ts
export async function validateSession(req: Request) {
  const token = req.headers.get("authorization")?.split(" ")[1];
  if (!token) return null;
  const session = await db.sessions.findUnique({
    where: { token, expiresAt: { gt: new Date() } },
    include: { user: true },
  });
  return session?.user ?? null;
}

ProblemsOutputDebug ConsoleTerminal

~/projects/myapp$

🤖 Cursor active · watching

Ln 7, Col 34TypeScript

Works with your tools. Makes them better.

Install once. Every AI tool in your workflow gets smarter automatically.

VS Code

Cursor

GitHub Copilot

Claude

Windsurf

MCP

How SnapBack works

SnapBack is an integrated development intelligence platform that gives AI coding assistants repository-lifetime memory and workflow-aligned tools. Unlike generic context providers, SnapBack learns from every session and actively participates in AI interactions.

The Perceive → Reason → Act → Reflect Pattern

Auto-cycling

1. Perceive: Understanding workspace state

The pulse tool

When an AI assistant needs to understand current state, one call to `pulse` returns everything in token-efficient wire format.

Wire format response:

This tells the AI:

•Change velocity (18 changes per minute)
•Risk pressure (45% of safety threshold)
•Risk classification (Medium)
•Recommended action (monitor, not critical)

Why it matters: The AI grounds itself in reality before reasoning—using ~500 tokens instead of 15k+ for generic context retrieval.

Context windows reset. Your repository's memory doesn't.

The more you code with SnapBack, the better your AI suggestions get.

Multiple surfaces, one brain

SnapBack isn't just an extension or just an MCP server. It's an integrated platform with three coordinated surfaces powered by a persistent daemon.

VS Code Extension

The invisible UI that appears only when intelligence is needed.

•Real-time pulse and pressure indicators in status bar
•Inline warnings when risky patterns detected
•Advisor notifications with learned context
•Protection state navigation and time travel
•Configures and manages daemon lifecycle automatically

CLI with Persistent Daemon

The intelligence engine that powers everything.

•Processes observations from editor and AI tools
•Maintains repository-lifetime memory and learned patterns
•Serves context to both extension UI and MCP clients
•Runs continuously in background or on-demand
•Handles learning extraction, pattern detection, and risk scoring

$ npm install -g @snapback/cli

MCP Server

Protocol interface for AI assistants (Cursor, Claude, Copilot, Continue.dev).

•Provides workflow-aligned tools (snapback, snapback_learn, snapback_end, snap_pulse)
•Token-efficient wire format preserves context budget
•Shares state with extension via daemon
•Works with any MCP-compatible client

Connects via STDIO (ships with CLI) or SSE.

Why this matters

You get a cohesive experience across all workflows:

•The same intelligence that warns you in VS Code also advises your AI assistant via MCP
•The daemon learns from both human and AI interactions
•Memory persists across editor sessions, context window resets, and tool switches
•All surfaces get smarter together, compounding knowledge over time

One system. Multiple surfaces. Repository-lifetime intelligence.

Get started in 2 minutes

Choose the path that matches your workflow:

Recommended

Option 1: VS Code users

Install the SnapBack extension

1.Install from VS Code Marketplace or search "SnapBack" in Extensions
2.Extension automatically installs and manages CLI + daemon
3.Start coding—SnapBack observes and learns
4.If you use Cursor or Claude Desktop, MCP server is automatically available

Install Extension

Option 2: CLI-first users

Install the CLI and run the daemon

1.Install via npm or download binary
2.Start the daemon: snap daemon start
3.Use from terminal: snap status, snap analyze src/, snap check

# via npm
npm install -g @snapback/cli

# or download binary
curl -fsSL https://snapback.dev/install.sh | sh

View CLI Docs

Option 3: MCP-only users

Connect AI assistants via Model Context Protocol

1.Install CLI (daemon required for MCP functionality)
2.Configure your MCP client (Claude Desktop, Continue.dev, Cursor)
3.AI assistants can now call SnapBack tools

{
  "mcpServers": {
    "snapback": {
      "command": "snap",
      "args": ["mcp", "--stdio"]
    }
  }
}

MCP Setup Guide

94% accuracyacross Cursor, Copilot & Claude

<50ms overheadinvisible to your workflow

<1s context loadfull intelligence loaded instantly

Local-firstyour code never leaves your machine

Start free. Upgrade when it clicks.

Privacy-first architecture. Your code never leaves your machine.

Solo

Best place to start

$0/mo

For individual developers who want personal protection.

Full recovery.

Unlimited snapshots.

Basic AI detection.

Session tracking.

Community support.

Get Started Free

Free during Pioneer beta

Pro

Pioneer beta — Free for Contributing Pioneers

$20/mo

Everything in Solo, plus:

Closing ceremonies.

Pattern promotion.

Context compilation (.ctx).

Intelligence API access.

Priority support.

Join Pioneer Program

Team

For org-wide adoption

$28/mo

Everything in Pro, plus:

Team-wide pattern sharing.

Shared learning store.

Admin controls & RBAC.

Usage analytics per seat.

Audit trail.

Coming Soon

All plans: Privacy-first. Code never leaves your machine.

Why I built this.

I lost $12,000 in billable time to a single Cursor suggestion. It refactored a payment integration — confidently, cleanly, and completely wrong. I didn't catch it for three days.

Git blame told me what changed. It didn't tell me why, or that the same pattern had failed twice before, or that the file it touched was the most fragile file in my codebase.

SnapBack is the tool I needed that day. But more than that — it's the tool that would have prevented that day from happening.

— Qwynn, Founder

Frequently asked questions

Got questions? We've got answers. Can't find what you're looking for? Check our full FAQ or reach out to our team.

Still have questions? Join our Discord or email us.

Your codebase should get smarter, not just bigger.

94% accuracyacross Cursor, Copilot & Claude

<50ms overheadinvisible to your workflow

<1s context loadfull intelligence loaded instantly

Local-firstyour code never leaves your machine

VS Code extension. Zero config. First snapshot in 30 seconds.

Install SnapBack — Free Get CLI View Documentation

Join the community:GitHub Discord Changelog

{

}

Stop re-explaining your codebase to AI.

SnapBack learns what breaks your code — patterns compound, mistakes don't repeat, and your AI tools get smarter every session.

Install Extension — Free See How It Works ↓

94% accuracyacross Cursor, Copilot & Claude

<50ms overheadinvisible to your workflow

<1s context loadfull intelligence loaded instantly

Local-firstyour code never leaves your machine

Why I built this.

I lost $12,000 in billable time to a single Cursor suggestion. It refactored a payment integration — confidently, cleanly, and completely wrong. I didn't catch it for three days.

Git blame told me what changed. It didn't tell me why, or that the same pattern had failed twice before, or that the file it touched was the most fragile file in my codebase.

SnapBack is the tool I needed that day. But more than that — it's the tool that would have prevented that day from happening.

— Qwynn, Founder

Your codebase should get smarter, not just bigger.

94% accuracyacross Cursor, Copilot & Claude

<50ms overheadinvisible to your workflow

<1s context loadfull intelligence loaded instantly

Local-firstyour code never leaves your machine

VS Code extension. Zero config. First snapshot in 30 seconds.