Write it once, and have the next agent act on it.

npm i -g passalong installs it, passalong setup registers the MCP server, the capture skill and the Claude Code hooks, and passalong login syncs across machines. Reading a guide somebody sent you needs none of this: a share link opens in a browser, and an agent appends .md to it.

Connect your tools

Markdown with frontmatter, and headings that do not move: Problem, Steps, Verification, Gotchas. They are stable because the receiving agent keys on them — a bug uses Reproduce where a transfer uses Steps, and that difference is load-bearing.

Read the format

In Claude Code, say "pass this along" and the capture skill writes the guide from the session. From a terminal, passalong share <file>. Either way --to team/@handle asks one person, --to team/#group asks the people who do a thing, and --to team asks nobody in particular.

Connect an assistant

Four calls, whatever the guide is: take it — which is what tells the sender somebody is on it, and stops a second agent doing the same work — report progress, hand it in with the evidence, or pass it back with the reason. The sender hears each one.

A follow-up is more context for a guide, written as its own guide: passalong share --follows <id>. Whoever opens the original gets it too. Defects you found but are not fixing go in one call as a report, each becoming a guide somebody can take on its own — with the screenshot attached, not described.

Attaching screenshots

Every command and every MCP tool is listed in llms.txt, which is written for an agent and reads perfectly well as a person's reference. The HTTP API has an OpenAPI document, for a client that adds no MCP server at all.

The API document