Every command, grouped by what it is for.
The passalong command does from a terminal what the hub does in a browser and an agent does over MCP. It keeps no work on your machine unless you ask: the server holds it.
Install
npm i -g passalong
passalong login # sign in from the browser
passalong setup # MCP server, hooks and skill for Claude Code
codex mcp add passalong -- passalong mcp # CodexWrite work down
passalong new "<what needs doing>" [--to TARGET] [--parent ID] [--draft]- Write work down in a sentence.
--tois a team,team/@handlefor one person, or"team/#group"for the people who do a thing (quote it: a shell reads#as a comment).--draftholds it for a person to read first. passalong new <file.md> [--to TARGET] [--parent ID] [--draft]- The same, from a markdown file.
passalong attach <file>- Upload a picture or a file and print the markdown that points at it.
Find it
passalong board- What needs you, who is on what, and what is ready.
passalong list [query]- Work you and your teams can see, newest first.
passalong open <id> [--print]- View it in the browser, or in the terminal with
--print. passalong now- What this worktree holds and what is waiting. The Claude Code hooks call it.
passalong hub- Open the hub in the browser, signed in.
Do it, and say so
passalong take [id] [--save]- You are doing it: nobody else can take it while you hold it. With no id, the next thing waiting for you.
--savealso writes./.passalong/<id>.md. passalong progress <id> <note>- Still on it, with a one-line note the hub shows.
passalong ask <id> <question>- Ask the person, keep it, and wait for their answer.
passalong wait <id>- Wait for the person's reply and print it. Run it in the background after
ask. passalong hand-in <id> <note> --evidence TEXT [--writeup TEXT] [--pr LINK]- It is done: it goes to Done with what you showed.
passalong pass <id> <why>- It is not yours, or you are stuck: hands it back with your reason.
Move it
passalong reply <id> <text> [--file PATH]- Write to whoever holds it, or leave a note for whoever takes it next.
passalong assign <id> <to>- Give it to
@handle(or several:@ada @bola), a#group, orteam. passalong release <id>- Take work back from whoever holds it.
passalong ready <id...|--all>- Work you have read is Ready: whoever it is for may take it now.
passalong reopen <id> <why>- Finished work is not right: back to Ready, and whoever takes it next reads why.
passalong archive <id>- Off the board and out of the free tier's count.
passalong rm <id>- Delete it.
Teams
passalong me [--handle H] [--name N] [--email E]- Who you are to teammates.
passalong team- The current team and its members.
passalong team create <name>- Start a team; you become its owner.
passalong team invite [email]- Make an invite link, mailed when an email is given. It is accepted in the browser, so a teammate needs no terminal.
passalong team join <link|code>- Accept an invite.
passalong team use <slug>- Switch the current team.
passalong team promote|demote <@handle>- Make a teammate an admin, or a member again.
passalong team remove <@handle>- Take a teammate out.
passalong team leaveleaves yourself.
Accounts
passalong login- Sign in from the browser.
passalong login --with-token- Read a token from stdin instead, for CI and scripts.
passalong login --new- Add another account to this machine.
passalong accounts- The accounts signed in here, and which is the default.
passalong use <name>- Make one of them the default.
passalong logout [name]- Forget one of them; the current one by default.
Agents and your data
passalong setup- Install the Claude Code capture skill, the MCP server, its hooks and a status line.
passalong mcp- Run the MCP server over stdio.
passalong work [--once] [--agent CMD]- Run an agent on each piece of ready work for this repo, one after another.
passalong export [dir]- Dump every piece of work as plain markdown,
./passalong-exportby default. passalong version- Print the installed version (also
-v,--version).
More than one account
A machine can be signed in to several accounts, say a work one and a personal one. passalong login --new adds another, and passalong use <name> picks the default a person at a terminal gets. For one command, --as <name> or PASSALONG_ACCOUNT=<name> says which.
An agent has no terminal to be asked at, so with two or more accounts and nothing saying which, it is refused and told to ask you. You answer, and it calls the accounts tool with use and the name. That lasts for the session and moves nothing on disk. The current team belongs to the account, not the machine.
Working a queue unattended
passalong work runs claude -p on each piece of ready work for the repo you are in, one after another. The agent runs headless, so it can only use the tools you allow up front; work that needs anything else ends with a BLOCKED: progress note. To allow tools, point --agent (or PASSALONG_AGENT) at a small script:
#!/bin/sh
# The prompt must come first: --allowedTools takes any number of values and would swallow it.
exec claude -p "$@" --permission-mode acceptEdits \
--allowedTools "mcp__passalong__*,Bash(npm test:*),Bash(node:*),Bash(git add:*),Bash(git commit:*)" Each agent commits its change and hands it in, which puts the work in Done. If it is not right, passalong reopen <id> <why>: the next agent reads the reason before it starts again.