Practical use.
A handoff only helps when the receiving tool can pick it up clearly. The formatter should change the shape of the packet, not change the underlying facts.
native integrations.
The same disk-truth recovery state is reshaped for Aider, Amazon Q, Amp, Antigravity, ChatGPT, Claude Code, Claude Desktop, Claude.ai, Cline, Codex, Crush, Cursor, DeepSeek, Factory Droid, Gemini (web), Gemini CLI, Grok, Kilo Code, Kimi, Kiro, OpenClaw, OpenCode, Perplexity, Qwen Code, Roo Code, Trae, Devin and Windsurf, Z.ai (GLM), Replit, Lovable.
What it carries.
- CLAUDE.md and AGENTS.md style outputs
- Gemini and Cursor pickup formats
- Tool-specific continuation wording
- native pickup-file and MCP integrations, with web chats such as Replit and Lovable handled through clean clipboard handoff
How it fits ShardStitch.
This feature defines the output boundary: a recovery packet can be written as a tool pickup file, MCP response, or clean handoff for a web chat, depending on the target.
Choosing a pickup format.
Use the target tools native file when it supports one, such as CLAUDE.md, AGENTS.md, or a tool-specific rules file. Use clipboard handoff for web-first tools or when you want to review the packet manually. MCP is useful when the target can call the local server during the live session.
The format changes how context is delivered, not what is true. The same changed files, verification state, and next action should remain reviewable across targets.
Check the receiving tool before you switch.
For a same-repository switch from one coding agent to another, choose the destination format, then check that its pickup file or paste-in instructions are actually visible to that tool.
- Choose the destination AI before generating the packet; the chosen format controls its headings, instructions, and pickup location.
- Open the generated file and confirm the goal, changed files, decisions, failed attempts, and verification state survived formatting.
- Start the receiving tool in the correct repository and ask it to verify the listed files against the working tree before editing.
Worked example.
Suppose a task moves from a terminal agent to a desktop IDE. Generate the destination format, open the pickup file from the same repository root, and compare its changed-file list with git status. If the IDE does not expose the file in its project context, paste the packet instead and record that this was a manual handoff.
Limits and verification.
Formatting is not a native integration guarantee. A file can be written successfully while the receiving tool ignores it, starts in another folder, or supports a different instruction-file convention. Confirm the destination loaded the handoff; do not treat a successful export as proof that the next agent read it.