Use ShardStitch with Kilo Code.
For a new Kilo Code run, ShardStitch can write a project handoff and summarize the work that reached the repository. This is useful after a retry loop or interrupted task, but it is not a restore of Kilo’s private chat history.
Kilo Code integration paths.
.kilocode/rules/handover.md
ShardStitch writes a continuation file in Kilo Code’s project rules directory. Review it with the project before you start a new task.
Configure Kilo separately
Current Kilo documentation describes MCP through the VS Code Settings UI or a Kilo config file with a top-level mcp entry. ShardStitch’s Kilo setup is manual; verify the server appears connected in Kilo.
Partial, based on local evidence
ShardStitch can collect changed files, diffs, commits, notes, and verification state. It cannot infer the full conversation or recover changes that never reached disk.
Prepare a Kilo Code handoff.
Run ShardStitch in the project and inspect the detected diff, changed files, commits, notes, failed attempts, and checks. Correct anything that is stale before generating the packet.
Select Kilo Code and review .kilocode/rules/handover.md. Keep the file focused on current decisions, constraints, completed checks, and one next action.
Open Kilo Code in the same project, validate the handoff against the files, and rerun the relevant check before continuing.
Configure MCP separately.
For a local MCP server, use Kilo Code’s Settings interface or its supported Kilo configuration file. The official documentation describes project and global scopes and configuration under the mcp key. Check the current Kilo docs for the file location supported by your installed extension or CLI; these surfaces can differ.
Official Kilo Code reference.
Kilo’s MCP setup guide covers the VS Code settings path, project/global config, transports, and connection troubleshooting. This ShardStitch page describes its handoff workflow, not a guarantee that every Kilo installation has an active MCP server.
FAQ.
Can ShardStitch recover a Kilo Code session?
It can prepare a continuation from available local project evidence. It cannot restore Kilo’s private transcript, remote request state, or unsaved edits.
Is MCP required?
No. The handoff file works independently. MCP is optional and must be configured and verified in Kilo Code.
Open the researched failure guide, preserve the work that reached disk, and continue from a clean verified state.