Use ShardStitch with Kimi.

This Kimi profile separates the web-chat handoff from Kimi CLI. The web route uses a portable memo or paste; the CLI route has a local MCP configuration path, so choose the route that matches the client.

After-death behavior: Partial. The CLI gets MCP and a generic memo; web usage is paste-based.

Integration paths.

Hand-off in

Generic .handoff_memo.md for web; Kimi CLI uses the local profile.

MCP

Auto-configured for Kimi CLI at ~/.kimi/mcp.json.

Session recovery

Separate Kimi web paste from CLI configuration; verify which surface produced the state.

Setup path.

Run ShardStitch inside the project.

For Kimi web, paste the generated continuation packet. For Kimi CLI, keep the memo in the project and verify the ~/.kimi/mcp.json connection in the active environment.

Write the Kimi handoff.

For Kimi CLI, install MCP and use the memo. For Kimi web, paste the continuation.

Start clean.

State whether the next session is Kimi web or CLI, then check that its context route matches the packet; do not assume a web chat reads CLI configuration.

Limits to know.

The two Kimi surfaces do not share a guaranteed session store or pickup mechanism. A CLI MCP config is irrelevant to a browser chat unless that client separately supports and loads it.

Best use case.

Keeping a Kimi continuation lean instead of session state-heavy.

FAQ.

Does Kimi web use the CLI MCP configuration?

This profile treats those as separate paths: web chat uses paste-based context, while Kimi CLI can use the documented local configuration. Confirm the active client before continuing.

Get ShardStitch

Resume this workflow.

When switching from CLI to web, paste the handoff and mark any commands not yet run. When staying in CLI, reopen the same repository and verify the MCP server before requesting a scan.

For Kimi web, paste the memo; for Kimi Code CLI, explicitly read it from the correct checkout. Keep these two delivery paths separate.

Primary source and delivery boundary.

Kimi Code CLI repository (checked September 27, 2026). Moonshot documents its terminal coding agent in this repository. Distinguish that local CLI from Kimi web; a memo supplied to one surface does not establish context in the other.

Tool-specific troubleshooting

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