Which AI coding tool has killed your session most?
by•
Building ShardStitch — a local session recovery tool for AI coding. Curious which tool causes the most pain for developers here.
Claude Code · Codex · Gemini · Cursor · Windsurf · DeepSeek · ChatGPT · Aider · Ollama
When it hits — do you copy-paste into a new chat, switch tools, or just lose the work?
ShardStitch does two things:
→ Moves your live session to the next available tool when you're locked out
→ Trims the conversation tree and restarts clean in the same tool when switching isn't possible
Everything stays on disk. No cloud. No asking the dead AI for help.
Launching June 17. Happy to share early access with anyone who replies.
37 views
Replies
One thing people don't expect: ShardStitch gets richer the longer you use it.
First handoff reads disk cold — git diff, changed files, dependency graph, what you were doing. That alone recovers most sessions.
But keep using it on a project and the memory layer kicks in — architectural decisions, known bugs, conventions, rejected paths all compound across sessions. Mature projects recover closer to 99% integrity automatically, without you doing anything differently.
Start early, recover perfectly. Start late, recover anyway.
Launching June 18. Happy to share early access with anyone who replies.
Something most handoff tools miss: they know what you were doing but not what's dangerous to touch.
ShardStitch builds a dependency graph before generating the handoff — impact radius, god nodes, files that everything else relies on. The next AI gets a warning: "don't touch this file first, it'll break these 12 things."
That's the difference between a handoff that continues your session and one that introduces new bugs.
Dead session recovery
The thing that frustrates me about every other handoff tool: they need the current AI to write the summary.
Rate limit hit? The AI can't write anything. Context overflowed? Same problem. The tool that was supposed to save you needs the thing that just died to help it.
ShardStitch never asks the AI anything. It reads git diff, changed files, dependency graph, and session logs straight from disk. Dead session is irrelevant — the work already survived on disk.
Zero dependencies / local-first
Quick technical note for anyone who cares about this stuff:
ShardStitch has zero pip dependencies. Pure Python stdlib. 9.4MB installer on Windows.
No dependency hell, no supply chain risk, no version conflicts. Runs on any machine instantly. Your code never touches a server — not even for updates.
Built this way deliberately. A tool about keeping your session private shouldn't route anything through a cloud.
Dead session recovery
The thing that frustrates me about every other handoff tool: they need the current AI to write the summary.
Rate limit hit? The AI can't write anything. Context overflowed? Same problem. The tool that was supposed to save you needs the thing that just died to help it.
ShardStitch never asks the AI anything. It reads git diff, changed files, dependency graph, and session logs straight from disk. Dead session is irrelevant — the work already survived on disk.