Hand finished work to another context.
Solve something non-trivial in one agent session. Open a session somewhere else — another repo, another machine, a teammate — and the agent there already knows the whole story: the problem, the decisions, the steps, how to verify, and what went wrong along the way.
Backfill order totals without locking the table
Verification
- Run
pnpm verify:totals— every row reconciles, exit 0. - Check
pg_stat_activityduring the backfill: no lock waits over 50ms.
Gotchas
The obvious single UPDATE takes an ACCESS EXCLUSIVE lock and
stalls checkout for ~40s. Batching by primary key in chunks of 5,000 avoids it.
How it was built · Problem, Solution shape, Decisions, Steps
How a transfer works
-
Finish the work
In an agent session, say “pass this along”, or run
passalong share. It distills what you just did into a guide. -
Review and publish
Trim the draft. You get a short id and a link. Hand it to a teammate with
--to team/@them. -
Pick it up anywhere
Run
passalong pull <id>in the other context, or paste the link to an agent. Nothing to install on the receiving end.
If you write the guides
npm i -g passalong
passalong setup # Claude Code skill + MCP
passalong login # sync across machines
passalong board then tells you what is waiting on you, what you handed over
that nobody has taken, what landed, and what someone says does not work.
If you pick them up
Testers, teammates, anyone the work gets handed to. Nothing to install. Open the invite link, pick a handle, and guides addressed to you land in your hub.
- Every guide has a Verify view that leads with what to check and folds the implementation away.
- Two answers when you have tried it: it works, or it does not — with a reason the author sees the same day.
- The person who handed it over can see it landed, so nobody has to ask.
No lock-in
Guides are plain markdown with frontmatter. passalong export dumps everything.
Deleting your account leaves you with all of your content.