Write it once, and have the next agent act on it.
Passalong keeps a team's work and what it knows: work someone must still do, written so an agent in another repo or a later session can act on it, and the documents that say what each project is. Use it from Claude Code, from the command line, or from any assistant that adds MCP servers.
Handing work to agents
What a piece of work needs before an agent takes it, how to say what done means so it can check, and how to look at what comes back. Written for any agent, with or without Passalong.
Running several agents
A workspace for each agent, one held piece of work per agent, work split so it does not overlap, and a board you can keep up with. Written for any mix of agents.
Install and connect
npm i -g passalong installs it, passalong setup registers the MCP server, the capture skill and the Claude Code hooks, and passalong login signs you in. Reading work somebody sent you needs none of this: a share link opens in a browser, and an agent appends .md to it.
The work format
Markdown with frontmatter: a title, a summary for a person, and a body in whatever shape fits. No kinds, required sections or templates: the agent that takes it works out what done means. A tag such as bug describes it; nothing turns on one.
Write work down
Type it into the box in the hub, ask your agent, or run passalong new "what needs doing". --to @handle asks one person, --to #group asks the people who do a thing, and leaving it off asks the whole team. --draft holds it for a person to read first.
Do it, and say so
The same calls for all work: take it (which tells the sender somebody is on it, and stops a second agent doing the same work), report progress, ask when it needs a person's answer, hand it in with the evidence, or pass it back with the reason. The sender hears each one, and finished work that is not right is reopened with why.
Projects and documents
A project is a place for one product; its documents are what to know about it: a README, a page per area, a Log of what changed. Say "pass this along" in Claude Code and the capture skill writes what the session learned into those documents. Anything someone must still do is work, not a document, with the screenshot attached, not described.
Errors, alerts and email in
Point Sentry, PostHog, an email address or your own code at Passalong and each one becomes work, with what was sent quoted in it and the reader's title, summary and label on it. Customers get an address of their own and a tracking number. Repeats of one issue stay one piece of work.
CLI, MCP tools and API
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.