Checked October 3, 2026: Roo Code's official repository was archived on May 15, 2026, and its README says the extension was shut down. Existing installations may still be in use; see the Roo Code migration guide before switching tools.
Moving off Roo Code
- Cline: an alternative named by Roo's own repository. ShardStitch supports Cline as a handoff target.
- Kilo Code: publishes its own detailed Roo migration guide. ShardStitch supports Kilo Code as a handoff target.
- Zoo Code: a community fork with a settings importer. ShardStitch has no Zoo Code adapter.
- Roomote: the former Roo team's cloud product.
ShardStitch carries available working state, including changes, decisions, failed attempts, and the next step, into Cline or Kilo Code so you do not have to start over. See our Roo Code migration guide for the options and their sources. Conversation details are available only if they were captured or saved before the session was lost.
Use ShardStitch with Roo Code.
When a Roo Code request stalls, the checkpoint and the working tree may disagree. ShardStitch reads the current project state and prepares a Roo-readable continuation before you retry.
Integration paths.
.roorules.
This is how the next Roo Code session receives the recovered working state.
Manual. Use global mcp_settings.json or project .roo/mcp.json.
When supported, Roo Code can call ShardStitch locally instead of relying only on pasted context.
Partial - ShardStitch still rebuilds from verified repo state and local sidecars; deeper session recovery depends on what the target makes available.
Setup path.
Inspect the diff and recent commits before restoring a Roo checkpoint or retrying the request.
Generate .roorules from the surviving project evidence. MCP configuration is separate, in global mcp_settings.json or project .roo/mcp.json.
Carry forward the error, changed files, and test status. Treat any missing conversation-only reasoning as unknown.
Limits to know.
Roo checkpoints can help with edits the extension recorded, but they are not proof that the last provider response finished or that tests passed. Compare a restored checkpoint with Git before accepting it. ShardStitch's MCP setup for Roo is manual.
Resume this workflow.
For a request that will not complete, follow the Roo Code stuck-request guide. Preserve the current workspace and provider error first; then decide whether to retry in Roo or hand the verified packet to another tool.
Best use case.
Restarting a stuck Roo Code request with clean repository context, or carrying unfinished work into Cline or Kilo Code when moving off Roo.
Source trail.
Roo Code's archived documentation covers common questions, checkpoints, and OpenAI-compatible providers. These sources describe Roo Code's behavior; ShardStitch's recovery claims describe its own local workflow.
FAQ.
Does a Roo Code checkpoint replace a fresh project scan?
No. A checkpoint records what Roo captured, while the current Git state and files show what is in the checkout now. Compare both before resuming.
Tool-specific troubleshooting
For symptom-specific diagnostics and recovery steps, use the focused guide: Troubleshoot Roo Code.