Use ShardStitch with Amazon Q Developer.

This Amazon Q Developer profile focuses on the project context file and the optional MCP connection described here. Use it when a Q session has ended but the local checkout still contains the implementation state.

After-death behavior: Partial. Disk truth still works from git, changed files, commits, and ShardStitch sidecars; there is no dedicated Amazon Q session state parser listed.

Integration paths.

Hand-off in

.amazonq/context.md.

MCP

Auto-configured at ~/.aws/amazonq/mcp.json.

Session recovery

Partial: project context and optional MCP support the handoff; verify any session-derived details.

Setup path.

Run ShardStitch inside the project.

Write the continuation to .amazonq/context.md, open the intended repository in the Q client, and confirm the file is visible in that workspace. Use the MCP route only when the local server is connected in the active client.

Write the Amazon Q Developer handoff.

Generate the recovery packet, let ShardStitch write .amazonq/context.md, and use the MCP config when Amazon Q can call local tools.

Start clean.

Ask Q to identify the current branch, files named by the handoff, and checks still pending before requesting the next code change.

Limits to know.

A project context file and a configured MCP server are separate pickup paths. This page does not claim that Amazon Q server-side history is recoverable or that every client mode loads the same local context.

Best use case.

Keeping Amazon Q aligned with the repo after a clean restart.

FAQ.

Does .amazonq/context.md prove Amazon Q loaded the handoff?

No. Open the repository in the intended Q client and verify the handoff is in its project context. The file existing on disk is not evidence that a particular session read it.

Get ShardStitch

Resume this workflow.

For a paused refactor, keep the packet beside the project context, reopen the same checkout, and ask Q to list the modified files and the exact test that remains. Reconcile that answer against Git before resuming.

Make .amazonq/context.md visible to the Q client working on this checkout, then confirm its account of the branch and unresolved test.

Primary source and delivery boundary.

Amazon Q IDE MCP configuration (checked September 27, 2026). AWS documents client-side MCP configuration. A generated project memo is separate from a connected server; verify the active IDE connection rather than assuming file generation configured it.

Tool-specific troubleshooting

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