Use ShardStitch with Factory Droid.

This Factory Droid profile uses a project context file and the MCP configuration described for Droid. Keep the two mechanisms distinct: one seeds the next run, the other enables live calls when connected.

After-death behavior: Yes. ShardStitch can combine Factory Droid session state files with git state and project context.

Integration paths.

Hand-off in

.factory/context.md.

MCP

Auto-configured at ~/.factory/mcp.json.

Session recovery

Use project context for restart; verify remote task completion against local output.

Setup path.

Run ShardStitch inside the project.

Place the verified packet in .factory/context.md and open the intended repository in Droid. For MCP, check the active ~/.factory/mcp.json entry and confirm the server starts.

Write the Factory Droid handoff.

Write .factory/context.md and install the local MCP server.

Start clean.

Have the next Droid run list the task boundary, files to inspect, and verification still missing before it launches an implementation task.

Limits to know.

A context file cannot guarantee that an agent run reads it, and MCP setup can fail independently. This profile does not claim to restore cloud task history or remote execution state.

Best use case.

Recovering Factory Droid work into a clean agent session.

FAQ.

Does .factory/context.md recover a Factory task automatically?

It supplies local project context for a new run when the workspace reads it; it is not a restoration of the previous task record. Verify the active workspace and server connection.

Get ShardStitch

Resume this workflow.

If a cloud agent task was interrupted, compare its last reported action with the local diff, then seed Droid with the verified local state. Do not assume a remote run completed a command unless its output is present.

Keep the Droid checkpoint in the correct repository and explicitly verify the file context before delegating the next remote action.

Primary source and delivery boundary.

Factory AGENTS.md guidance (checked September 27, 2026). Factory documents repository guidance through AGENTS.md. Confirm the active harness and checkout; a remote task result still needs comparison with the branch available locally.

Tool-specific troubleshooting

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