Use ShardStitch with Codex CLI.
When a Codex CLI run stops or you want to continue in another coding tool, ShardStitch turns the current repository state into a handoff Codex can read. The project files, not a remembered transcript, remain the source of truth.
Codex pickup paths.
AGENTS.md
Codex CLI uses this project instruction file. Put concise continuation facts and the next action there; keep sensitive values and large logs out of it.
Codex CLI MCP configuration
ShardStitch can configure the local MCP entry in Codex configuration. MCP availability depends on the client and configured server; it is not required to use a file handoff.
Rebuild from what reached disk
ShardStitch can summarize changed files, diffs, recent commits, notes, failed attempts, and verification state. It cannot recreate unsaved edits or a missing private chat transcript.
Continue a Codex task.
Run ShardStitch from the project and review the changed files, diff, recent commits, project notes, and test status it found.
Choose the Codex CLI target so the continuation is written to AGENTS.md. Review the generated file before starting a fresh run.
Start Codex in the same repository, inspect the handoff, and verify the proposed next step against the current files before editing.
Where recovery stops.
A handoff is not a Codex session restore. It cannot recover unsaved work, hidden remote state, credentials, or conversation details that never reached project files. Treat inferred notes as leads to verify, not as facts.
Official Codex references.
OpenAI documents project instructions in Codex CLI documentation and lists the CLI’s MCP support there. ShardStitch’s handoff is a portable project file; use Codex’s own documentation for current CLI behavior and configuration.
FAQ.
Do I need MCP to continue a task?
No. A project handoff file is the simpler path. MCP is optional and useful only when you want a compatible Codex client to call ShardStitch tools.
Does ShardStitch upload the repository?
Normal recovery is local-first. Review the current privacy and license documentation for the exact product behavior; do not put secrets in a handoff file.
Tool-specific troubleshooting
For symptom-specific diagnostics and recovery steps, use the focused guide: Troubleshoot Codex CLI.