Use ShardStitch with Crush.

This Crush profile distinguishes the portable handoff note from the optional stdio MCP setup. Use the note as the restart record and validate the Crush project path before the next run.

After-death behavior: Yes, when the local session store and repo state are present. The generic memo keeps handoff portable.

Integration paths.

Hand-off in

Generic .handoff_memo.md.

MCP

Auto-configured at ~/.config/crush/crush.json using stdio MCP.

Session recovery

Use the memo and local project evidence; confirm captured conversation details align with the diff.

Setup path.

Run ShardStitch inside the project.

Save .handoff_memo.md in the project, then open Crush against that same checkout. If MCP is configured in crush.json, confirm its command and server status before depending on live calls.

Write the Crush handoff.

Generate the memo and let ShardStitch configure Crush MCP.

Start clean.

Ask the new session to identify the recorded failure, the last verified command, and the next safe check; compare those details with the current files.

Limits to know.

The memo is a project-side continuation artifact, not a backup of the full Crush transcript. MCP availability depends on the local Crush configuration and process; the handoff file remains usable without it.

Best use case.

Recovering from a Crush session into another CLI agent.

FAQ.

Does Crush MCP replace the handoff memo?

No. MCP supports live tool calls when configured; the memo carries restart context. Use whichever path is available and verify the repository state either way.

Get ShardStitch

Resume this workflow.

If Crush stops during a patch, preserve the diff, write the failed attempt and test output into the memo, then relaunch from the correct project. Do not rerun a destructive command merely because it appears in the packet.

Keep .handoff_memo.md beside the Crush checkout and explicitly request a read before running the next command; do not assume that this filename triggers automatic loading.

Primary source and delivery boundary.

Crush configuration and project instructions (checked September 27, 2026). The official repository documents Crush configuration and project context. The ShardStitch memo is a supplied checkpoint, not a vendor-guaranteed automatic pickup filename.

Tool-specific troubleshooting

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