When an AI coding session breaks, ShardStitch rebuilds the thread from disk.

Rate limit, context overflow, frozen model, tool switch, new machine. ShardStitch packages the surviving project state into a clean handoff so the next session starts already caught up.

WORKS TODAY - 100% ON-DEVICE

The short version.

1. Scan

Reads git diff, changed files, recent commits, dependency graph, notes, and project memory from your local disk.

2. Shape

Turns the messy working state into a compact continuation brief tailored to the tool you choose next.

3. Handoff

Copies the prompt, injects the right pickup file, or prepares a secured handoff for another machine or teammate.

ShardStitch does not ask the old AI for a summary. It works after the session is dead because the important state already survived on disk.

COMPACT VS RECOVERY

/compact is preventive. ShardStitch is recovery.

Claude's /compact, plan.md, and resume-from-summary workflows are useful when the session is still alive and you are staying inside Claude. They are the right move if you catch context pressure early.

ShardStitch covers the harder edge: the session is already blocked, the summary is lossy, the notes file drifted, or the next tool is not Claude. It builds a forward brief from disk state, including git diff, changed files, recent commits, dependency risk, notes, and project memory. It then separates verified facts from inferred next steps so the next AI gets a clean starting state, not a chat recap.

THE CORE LOOP

From stuck to restarted in under 30 seconds.

WHAT YOU DO

Press Alt+G, open the dashboard, or run shardstitch.
Choose the target: same tool fresh chat, Codex, Claude, Cursor, Gemini, or another supported agent.
Choose what to include: git diff, dependency graph, task notes, project memory, file snapshots.
Click Stitch. Paste the handoff or let ShardStitch inject it into CLAUDE.md, AGENTS.md, GEMINI.md, or .cursorrules.

The next AI sees what changed, what you were doing, what is risky, and what comes next.

WORKS TODAY

The common recoveries.

Same tool, fresh chat

Claude or Cursor got bloated. ShardStitch trims the context into a clean restart prompt for a fresh session.

Different AI tool

Claude stalls, Codex is ready. Cursor loses the plot, Gemini can continue. The handoff is formatted for the next tool.

Locked out

Rate limit hit mid-task. ShardStitch reads the project from disk and reconstructs the working state without the old session.

Local model crash

Ollama, LM Studio, or vLLM runs out of room. The disk state and autosave trail become the recovery source.

Developer handoff

One developer stops, another picks up. The next AI gets decisions, changed files, risks, and next steps.

Manual move

Download a handoff, copy-paste it, or move it through your own private repo. ShardStitch generates; you control transfer.

WHAT TRANSFERS

Not just a summary. A working-state packet.

Git state

Diff, changed files, recent commits, uncommitted work, branch context.

Dependency graph

Impact radius, hotspots, god nodes, and files the next AI should touch carefully.

Project memory

Decisions, conventions, known bugs, rejected paths, and the accumulated context that gets richer over time.

Session Vault

Local recovery history keeps usable conversation context available after crashes, closes, outages, or tool bugs.

4-tier context

Session, task, project, or everything. ShardStitch chooses the right depth for the next handoff.

Integrity check

Fresh scans reconcile stale memory, changed files, and dependency risk before the next AI receives context.

Task intent

What was in progress, what was tried, what failed, and the next concrete action.

Tool format

Aider, Amazon Q, Amp, Antigravity, ChatGPT, Claude Code, Claude Desktop, Claude.ai, Cline, Codex, Crush, Cursor, DeepSeek, Factory Droid, Gemini (web), Gemini CLI, Grok, Kilo Code, Kimi, Kiro, OpenClaw, OpenCode, Perplexity, Qwen Code, Roo Code, Trae, Devin and Windsurf, Z.ai (GLM), Replit, Lovable receive context in the shape they read best.

Your selection

Selective handoff lets you include only what belongs in that transfer.

native integrations

Every tool gets the recovery layer. The handoff method changes by tool.

ShardStitch's core recovery is tool-independent: it reads your project from disk, not from the AI. That means every supported target can receive a handoff by copy/paste. Some tools also support auto-injection, MCP, or live Recall capture.

Always available

Disk scan works across native integrations plus web-chat paste fallback because it reads git state, changed files, dependency graph, notes, and project memory from your local project.

Universal fallback

Manual copy/paste works for native integrations plus web-chat paste fallback. If a tool has no pickup file, no MCP client, or no capture path, you still get a clean continuation prompt.

Auto pickup where possible

File injection is full for tools with known pickup files like CLAUDE.md, AGENTS.md, GEMINI.md, and .cursorrules; partial where a tool only accepts looser project notes.

MCP where the tool supports it

MCP is available for tools that act as MCP clients, including Claude Code, Cursor, and Devin. Other tools still use disk scan, file injection, or copy/paste.

Recall when capture is possible

Recall is full for verified desktop environments such as Cursor, Devin, Aider, and Antigravity; partial for Claude Desktop and tools where history paths or browser capture vary.

Status labels matter

Full support means automatic path. Partial means the feature works with setup limits or tool-specific constraints. Not supported means ShardStitch falls back to disk scan plus manual handoff.

Important: support does not mean ShardStitch controls every AI tool. It means ShardStitch can produce the best safe handoff that tool can realistically accept.

PRIVACY

Local-first recovery. No telemetry. No cloud sync.

ShardStitch reads local files and writes local handoff artifacts. Your code does not leave your machine unless you explicitly move a handoff yourself through a channel you choose.

Apart from license validation with Polar, cross-geography transfer is the only planned feature that uses the internet. It is opt-in, encrypted on your device before it moves, and designed as a dumb relay that never sees readable code.

Network & privacy

ShardStitch's recovery is local: it reads your project from disk, never the cloud. The routine network calls are license validation at activation and a quiet periodic re-check to Polar, the payment provider that issued your key. No code or conversation content is included.

COMING NEXT

What changes later.

LAN handoff

Encrypted handoff between your own machines on the same local network.

Founder to developer

Turn product reasoning and architecture decisions into a developer-ready AI handoff.