Use ShardStitch with Amp.

This Amp profile uses a repository-level AGENTS.md pickup file and a manually configured MCP option. It is useful when the next Amp run should inherit a concise task boundary without importing an entire old transcript.

After-death behavior: Yes, when the local store and repo state are available. ShardStitch can rebuild from disk and hand the next session AGENTS.md context.

Integration paths.

Hand-off in

AGENTS.md, following the Codex convention.

MCP

Manual. Use amp mcp add, or amp.mcpServers in VS Code settings.

Session recovery

Use the repository handoff and available local history; confirm the capture matches this checkout.

Setup path.

Run ShardStitch inside the project.

Place the handoff in the project instruction file, then confirm Amp is started in that repository. If using MCP, check the active Amp configuration rather than assuming it was installed by generating the file.

Write the Amp handoff.

Write the handoff to AGENTS.md and add the MCP server manually where Amp expects it.

Start clean.

Have the new Amp session verify the task goal, files changed, and the next bounded action from the checkout before it launches an autonomous or background task.

Limits to know.

An instruction file can guide a new run but cannot re-create a completed or lost Amp conversation. MCP is optional and manual on this page; without a working connection, use the file handoff.

Best use case.

Splitting planning and implementation between Amp and another agent.

FAQ.

Is Amp MCP configured just because AGENTS.md exists?

No. AGENTS.md carries the pickup instructions. MCP must be configured separately if you want Amp to call ShardStitch during a live session.

Get ShardStitch

Resume this workflow.

Before handing an unfinished change to a background agent, put the verified state and do-not-repeat attempts in AGENTS.md. Ask the new run to inspect the diff first and keep its first action limited to the stated next check.

Check Amp guidance discovery for the repository AGENTS.md, preserving existing team instructions, before asking the new thread to inspect the changed files.

Primary source and delivery boundary.

Amp AGENTS.md discovery (checked September 27, 2026). Amp documents where repository and user guidance files are discovered. Check the active guidance list and preserve existing instructions when adding a task checkpoint.

Tool-specific troubleshooting

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