Use ShardStitch with OpenClaw.

This OpenClaw profile combines a project context file with an optional manually registered MCP server. Treat the file as the handoff and the running server as a separate connection to verify.

After-death behavior: Partial. ShardStitch can rebuild from disk and feed OpenClaw through its context file.

Integration paths.

Hand-off in

.openclaw/context.md.

MCP

Manual. Use openclaw mcp add shardstitch or the equivalent server block.

Session recovery

Confirm workspace mount and local session capture; a remote root may differ.

Setup path.

Run ShardStitch inside the project.

Write .openclaw/context.md in the intended workspace. If you use openclaw mcp add or a server block, verify the registration in the OpenClaw environment that will run the next task.

Write the OpenClaw handoff.

Write .openclaw/context.md and add MCP manually if needed.

Start clean.

Have the next session confirm the workspace path, read the handoff, and list the first repository check before executing tools.

Limits to know.

A project context file cannot confirm that a remote or containerized OpenClaw process mounted the same checkout. MCP registration also does not restore the previous conversation; verify both workspace and server.

Best use case.

Grounding OpenClaw in changed files, decisions, and next tests.

FAQ.

Will OpenClaw see a local handoff file from a remote workspace?

Only if that workspace can access the same project file. Confirm the mounted path or paste the packet into the active environment; do not assume local paths transfer to a remote process.

Get ShardStitch

Resume this workflow.

If the next OpenClaw run is in a container, compare its visible project root with the path recorded in the packet. Start with a read-only status check and stop if the expected files are missing.

Verify the OpenClaw workspace mount and session identity before supplying the local context file to the active agent.

Primary source and delivery boundary.

OpenClaw session management (checked September 27, 2026). OpenClaw documents session management and persistence. Confirm which session and workspace produced the evidence; a local directory alone does not identify the active remote or messaging session.

Tool-specific troubleshooting

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