How does ShardStitch hand off into Claude Code?

CLAUDE.md, auto-read by Claude Code on launch.

Does ShardStitch support MCP with Claude Code?

Auto-configured in .claude/settings.json for the project or ~/.claude globally.

Can ShardStitch recover after a Claude Code session dies?

Yes - ShardStitch supports recovery for this tool and combines it with verified repo state. Public docs show the outcome, not the private capture method.

Use ShardStitch with Claude Code.

Use ShardStitch when a Claude Code task needs a fresh session or a handoff to another coding tool. It creates a project continuation from repository evidence, then writes a file Claude Code can read with the project.

Important distinction: CLAUDE.md supplies project instructions; it does not restore Claude Code’s private conversation. ShardStitch summarizes work present in the repository and notes, and cannot recover unsaved edits or missing transcript content.

Claude Code handoff paths.

Project instructions

CLAUDE.md

Claude Code reads project instruction files at session start. ShardStitch can write a concise continuation there so a fresh session sees decisions, constraints, verification, and the next action.

MCP

Optional local tool connection

Claude Code supports MCP servers. ShardStitch can configure its local server; this is a separate capability from writing a handoff file, and is not needed for basic continuation.

Repository recovery

Recover what reached disk

Use the diff, changed files, commits, notes, and test results as evidence. Mark unknowns explicitly instead of treating old chat claims as verified state.

Start a fresh Claude Code session.

Inspect the project first.

Run ShardStitch in the repository. Check the detected diff, files, recent commits, notes, failed attempts, and checks before generating a handoff.

Write and review the handoff.

Select the Claude Code format and review the generated CLAUDE.md. Keep it focused on this continuation rather than turning it into a permanent, oversized project manual.

Resume from the repository.

Start Claude Code in the same project, review the handoff against the current tree, then run the next verification before continuing edits.

Use MCP only when needed.

For live ShardStitch tool calls, configure the MCP server separately using Claude Code’s supported project or user scope. Confirm its connection in Claude Code; a saved configuration does not by itself prove the server is reachable.

Official Claude Code references.

Anthropic explains CLAUDE.md and project memory and MCP setup and connection checks. Claude Code can read project instructions, but those instructions are context, not a hard enforcement mechanism.

FAQ.

Does this restore the old Claude Code conversation?

No. It rebuilds a continuation from available project state. Unsaved changes and private chat history that is not in the project cannot be reconstructed.

Do I need MCP for a handoff?

No. The generated project file is sufficient for a file-based handoff. MCP is optional for calling ShardStitch tools from Claude Code.

Get ShardStitch

Tool-specific troubleshooting

For symptom-specific diagnostics and recovery steps, use the focused guide: Troubleshoot Claude Code.