What
There's no way to try throughline without wiring it into a real repo you care about. New users
have to install the plugin, trust it, and generate their own capture history before they see what
a populated HANDOFF.md or a live capture buffer actually looks like.
Prior art
adrrr/persistent-handoff ships demo/setup.sh plus demo/homelab/ — a small fictional repo
(a docker-compose homelab project) with a real, populated .claude/handoff.md already in it, a
project-scoped hook wired via demo/homelab/.claude/settings.json, and a README telling you
exactly what to type:
git clone https://github.com/adrrr/persistent-handoff && cd persistent-handoff
./demo/setup.sh && cd demo/homelab
claude --model claude-sonnet-5 --setting-sources project,local --strict-mcp-config \
--tools Read,Glob,Grep,Skill,Write
Then: tell the agent a decision was made and a restart is coming, watch the skill rewrite the
handoff, /exit, restart, ask "where were we?", and see the answer come from the hook.
Fix shape
Add a demo/ directory with:
- A small fictional project plausible enough to make the capture buffer and HANDOFF.md read as
real (not lorem-ipsum) — something with a few files, a git history, maybe a failing test or a
known bug to "investigate."
- A
setup.sh that wires the throughline hooks scoped to that project only.
- A populated example buffer and HANDOFF.md so someone can see the artifacts immediately, before
generating their own.
- A short walkthrough in
demo/README.md (or linked from the main README) of what to type to see
capture → distill → resume in action.
This also becomes the fixture for #'s recording.
What
There's no way to try throughline without wiring it into a real repo you care about. New users
have to install the plugin, trust it, and generate their own capture history before they see what
a populated
HANDOFF.mdor a live capture buffer actually looks like.Prior art
adrrr/persistent-handoffshipsdemo/setup.shplusdemo/homelab/— a small fictional repo(a docker-compose homelab project) with a real, populated
.claude/handoff.mdalready in it, aproject-scoped hook wired via
demo/homelab/.claude/settings.json, and a README telling youexactly what to type:
Then: tell the agent a decision was made and a restart is coming, watch the skill rewrite the
handoff,
/exit, restart, ask "where were we?", and see the answer come from the hook.Fix shape
Add a
demo/directory with:real (not lorem-ipsum) — something with a few files, a git history, maybe a failing test or a
known bug to "investigate."
setup.shthat wires the throughline hooks scoped to that project only.generating their own.
demo/README.md(or linked from the main README) of what to type to seecapture → distill → resume in action.
This also becomes the fixture for #'s recording.