Guides / Feature coverage
ShardStitch support across 31 AI handoff targets across native integrations and web-chat handoff is layered, not identical.
Every supported tool can receive a recovery handoff because ShardStitch reads the project from disk. More advanced paths depend on what the target tool allows: pickup files, MCP client support, or live capture access.
Plain rule: disk scan and manual handoff work everywhere. File injection, MCP, and Recall vary by tool.
Coverage levels
- Full: supported through a known automatic path.
- Partial: works with setup limits, variable paths, or tool-specific constraints.
- Not supported: use disk scan plus manual copy/paste instead.
Feature coverage snapshot
| Tool group | Examples | Disk scan | File inject | MCP | Manual | Recall |
|---|---|---|---|---|---|---|
| CLI tools | Aider, Amazon Q, Claude Code, Codex, Crush, Gemini CLI, OpenClaw, OpenCode, Qwen Code | Full | Full | Claude Code plus compatible clients | Full | Partial to full |
| Desktop IDEs | Antigravity, Cursor, Devin and Windsurf, Trae, Kiro, Claude Desktop, Factory Droid | Full | Full or partial | Cursor/Devin-Windsurf/Claude-compatible clients | Full | Full or partial |
| VS Code extensions | Cline, Roo Code, Kilo Code, Amp | Full | Full or partial | Tool-dependent | Full | Tool-dependent |
| Web/browser tools | ChatGPT, Claude.ai, DeepSeek, Gemini (web), Grok, Kimi, Perplexity, Z.ai (GLM), Replit, Lovable | Full | No | No | Full | Partial or manual fallback |
Why this matters
ShardStitch does not promise magical control over every AI product. It promises a reliable recovery layer. When a tool supports deeper integration, ShardStitch uses it. When it does not, the fallback is still useful: a structured handoff generated from your real local project state.