Before you pass the first one along.

Passalong keeps a team's work and what it knows, for people and AI agents. You write down what needs doing in plain words (or an email or an alert does) and the agent that picks it up takes it so nobody does it twice, reports as it goes, and hands it in with the evidence. Each project's documents say what the product is and how it is built, and agents read them when they take work and update them when they finish. It is a CLI, an MCP server for your assistant, and a hub for the people.

A piece of work is written for an agent as much as a person: a title, a one-line summary for whoever scans the board, and the text, screenshots and files the agent needs, in whatever shape fits. There are no kinds, required sections or templates; the agent reads it and works out what done means. What someone needs to know rather than do (how a product is built, a decision, what changed) goes in the project's documents, where everyone finds it later.

No. A share link carries its own key, so whoever holds it can open it, and an agent can append .md to the link for the raw markdown. You need an account to write work down, to take it, or to be part of a team.

Solo is $5 a month and Team is $20 a month for up to ten people. Reading a share link is always free. For anything else, write to contact@passalong.dev.

They are unlisted rather than secret. The key in the link is the authorisation, so anyone you send it to can read it and anyone they forward it to can too. Search engines are kept out three ways: share pages are noindex, they carry an x-robots-tag header for links that leak, and /w/ is disallowed in robots.txt. Treat a share link like an unlisted video, not like a password.

Claude Code, Codex and other coding agents run the MCP server locally, where it knows which repo you are in. Assistants that connect to remote servers, Claude and ChatGPT among them, point at the hosted server by URL instead. Anything else can use the HTTP API, which is described at /v1/openapi.json, and a share link's .md needs no client at all. Setup for each one is on the connect page.

Yes, and it should: a screenshot you described instead of attaching is the most useful thing in the report, thrown away. ChatGPT on the web passes the file straight through. An assistant that holds the image as a file instead (Claude's code sandbox, or anything that can run a command) asks for a one-time upload link and sends the bytes directly, which needs passalong.dev allowed for code execution. A local MCP server takes a path on your machine.

None of those, on purpose: work is one thing. An agent may label it bug, feature or question so the board reads at a glance, but nothing turns on the label. Every piece of work is worked the same way: take it, report progress, ask when it needs a person, hand it in with evidence, or pass it back with the reason. Knowledge that used to travel as a handover goes into the project's documents instead.

Nothing is taken away. A lapsed plan stops new work coming in; everything already there stays readable and can still be finished. passalong export dumps all of it as plain markdown at any time, and deleting an account leaves the author with their content.