share

Share (share <thread>)

Packages one thread of work so a colleague, or you on a machine with no access to the backup repo, can pick it up. Unlike zip, which mirrors everything for your own disaster recovery, share is curated and sanitized: it carries only what someone else needs to continue a single thread, with your personal memories held back by default and every file secret-scanned before it leaves the machine. It does not require /backup setup to have run.

The bundle uses the same machines/<hostname>/ layout as every other command (see ${CLAUDE_PLUGIN_ROOT}/docs/layout.md), so the recipient ingests it with the restore or merge they already have, no new command on their side. The scan behavior is in ${CLAUDE_PLUGIN_ROOT}/docs/secret-scan.md. Read both before building a bundle.

share is interactive-only, by design. Every step is a judgment call: which thread, which repos, which plans, whether a held-back memory should go, where the bundle lands. There is no cron or headless mode. If share is ever invoked with nobody to ask (for example from a non-interactive script), log the problem and exit cleanly rather than guessing, the same as zip and merge.

Step 1 - Resolve the thread and its scope

<thread> is required.

1. Match it against ~/.claude/handoff-index.md, case-insensitively and allowing partial matches, against the titles and one-line goals in the index (the same matching /pickup uses). This file is written by the session-continuity plugin; share reads it as a plain file and there is no hard dependency.
   • One live match (its path still exists): that handoff note is the anchor.
   • Several: list them and ask which via AskUserQuestion.
   • No match, but <thread> looks like a path (contains / or ends .md, expand a leading ~): use that file as the anchor if it exists.
   • No match and no index: say so and stop. Suggest running /handoff on the thread first, since share is built around a handoff note.
2. Derive the in-scope set from the anchor note:
   • The anchor handoff note itself, plus a one-line index entry for it (see Step 3).
   • The repo the note lives in: from the note's home-relative path (~/sites/foo/.claude/handoff.md -> repo ~/sites/foo), derive its memory store slug per docs/layout.md (sites-foo -> ~/.claude/projects/$(echo ~ | tr '/' '-')-sites-foo/memory/). If that store exists and is non-empty, it is in scope.
   • Other repos named in the note body: scan the note text for other absolute or ~-relative repo paths. For each whose memory store exists, ask via AskUserQuestion whether to include that store too. Never pull in a store the note only mentions in passing without asking.
   • Plans: if ~/.claude/plans/ exists and is non-empty, list every plan file and ask via AskUserQuestion (multi-select) which belong to this thread. Handoff notes do not reliably link plan files, so this is never automatic; default the selection to none.
3. If the derived scope is empty (no memory store, no plans, just the handoff note), say so and confirm the user still wants a handoff-note-only bundle before continuing.