Use ShardStitch with Gemini CLI.

This Gemini CLI profile uses repository instructions and an optional MCP settings entry. It is suited to terminal work where the next process can reopen the same checkout and read a concise project handoff.

After-death behavior: Yes. Gemini CLI has a native file pickup, auto MCP config, and local history Recall.

Integration paths.

Hand-off in

GEMINI.md, plus .gemini/handover_context.md when that directory exists.

MCP

Auto-configured at ~/.gemini/settings.json.

Session recovery

Start from local project context; verify terminal commands and the current branch.

Setup path.

Run ShardStitch inside the project.

Create GEMINI.md, start Gemini CLI from the repository root, and confirm it sees the project instructions. If the handoff uses .gemini/handover_context.md, check that file exists; check MCP configuration separately.

Write the Gemini CLI handoff.

Generate GEMINI.md and start Gemini CLI from the repo.

Start clean.

Ask the fresh CLI session to verify branch, diff, and the first unfinished command before it edits files.

Limits to know.

A project instruction file does not recover provider-side chat state, and a settings entry does not prove the MCP process launched. Keep terminal output and local Git evidence as the verification source.

Best use case.

Moving a Gemini CLI task into a clean continuation or another AI tool.

FAQ.

Is GEMINI.md enough to restore a Gemini CLI session?

It can carry project instructions into a new process, but it does not restore the old conversation. Reconcile the file with current Git state and verify any commands that were reported as complete.

Get ShardStitch

Resume this workflow.

After a terminal session hangs during a multi-file change, start Gemini CLI at the same project root, load the packet, and first run the listed status check. Continue only after the branch and diff agree with the handoff.

Launch Gemini CLI in the intended checkout and verify its loaded project context includes GEMINI.md before rerunning the pending terminal check.

Tool-specific troubleshooting

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

Source references and delivery boundary

Reference section reviewed September 27, 2026. Gemini CLI issue #12163 concerns non-interactive hang diagnostics and is closed as not planned, not a confirmed shipped fix. A continuation packet preserves project evidence; it does not guarantee recovery of a running CLI process.

Sources: issue #12163; a silent startup hang; issue #22896

More Gemini CLI recovery guides.

Investigate a silent startup hang separately from a lost resumed session. Preserve the current checkout in either case.