Works after the AI session dies.
The core ShardStitch wedge: when the old AI cannot summarize, compact, export, or continue, rebuild the coding state from what survived on disk.
Why "after the session dies" is a different problem.
When an AI coding session is alive, you can ask it to summarize, compact, write a handoff, call MCP tools, or update memory. Once it is dead or blocked, that option disappears. The only durable source left is the project itself.
That is the line ShardStitch is built around: recover from what survived locally instead of asking the old AI to explain itself.
The recovery sources that still exist.
Git state.
Diffs, changed files, recent commits, branch names, and staged work.
Project files.
The code as it exists now, not as the old transcript claims it exists.
Local notes and memory.
Plans, scratchpads, repo instructions, tool logs, and saved context.
Dependency shape.
Files that are central, risky, or likely to matter for the next step.
What can be recovered after a chat is deleted?
Files, Git history, current diffs, command output, and saved notes may still show what changed and what was checked. They cannot reliably recreate every decision or rejected approach that existed only in the vanished conversation.
The workflow.
Who this is for.
This is for builders who did not have perfect discipline before the failure. If you remembered to write a perfect handoff before every limit, great. If the session died while you were deep in debugging, this is the missing layer.
FAQ.
Why not just use /compact?
/compact is useful before failure. It does not help when the old session is already blocked, deleted, or no longer trustworthy.
What makes this different from memory tools?
Memory tools recall what was saved. ShardStitch reconstructs working state from disk even when no clean note was written.