sw-load

Session Watcher Load Handoff

Restore a previous session's handoff package into context so work can resume.

Steps

1. Load the handoff. Resolve a token from the skill args, from the user's message, or from the host's own handoff notice, which names pending handoffs by token: the Claude Code SessionStart hook's additionalContext, or the message DSH injects when the agent starts or resumes. Then call the load_handoff tool, whose schema carries the three ways in.

   A token you were handed is the one path that proceeds without asking. Any other way in — a free-text match, an auto-match, or several tokens offered at once — means listing what came back with each one's age and task preview and letting the user pick before you go on. Nothing found → tell the user the token is expired or invalid, and ask for direction.

2. Read the kept paths. Relative paths resolve against CWD, then project_dir.

   One strategy per entry, the first row that applies:

   Entry has	Read at load
   lines	each range
   resolvedSymbols	the (lines a-b) each string carries
   neither	the file's first 40 lines; with symbols, also grep -n each name in the file to place the entry points

   Each read is the host's file-reading tool over a line range of the kept file. Each call names one file. Issue every read for every entry in one message — each further turn re-reads the whole accumulated context.

   Unresolvable path → tell the user, skip. Empty paths_to_keep → ask the user what they are working on.

3. Place the summary in its lineage. lineage runs oldest to newest, one headline per lineage member; the injected page holds the newest turns and is already in context. From the page, list the turns whose A: note bears on the next task, by their S{k}:{T} address. When a headline bears on the next task and the page does not reach that member, call turn_page with that member's label as before. That list is what step 5 reports.