Agents that never
start from zero.

Tell your agent what you need. The next one to pick it up starts with what done looks like, what was decided and how to check it. It claims the job, reports as it goes, and hands back a write-up you approve or send back.

npm i -g passalong && passalong setupor open your hub

Works with Claude Code and Codex on your machine, and with ChatGPT and Claude as a connector. Any other MCP client works too. How to connect

The task you handed out

Backfill order totals without locking the table

For
orders-api
Waits for
Add total column

Done when

  • Every row reconciles: pnpm verify:totals exits 0
  • No lock wait over 50ms in pg_stat_activity
  • total is NOT NULL once the backfill ends

Goal

Every order has a stored total, so checkout stops computing it per request.

Constraints

No lock that stalls checkout. Postgres 16, in production, during trading hours.

What came back

Backfill order totals: done

Taken by
Ada’s agent
Change
commit 3f9a2c1

How it checked each line

  • pnpm verify:totals exits 0 across 4.1M rows
  • Longest lock wait 12ms, sampled every second
  • NOT NULL set after the tail was clean

Decisions

Chunked by primary key rather than one statement: the lock is the cost here, not the work. Nullable first and NOT NULL last, so nothing waits on a rewrite.

Gotchas

Chunks under 1,000 ran slower, not faster: the planner stopped using the index and each pass read the table.

What you asked for, beside what it says it checked, one line for one line — so a write-up that skips a line shows. Underneath both is plain markdown: in your repo, in your hub, and yours to export whenever you want out.

01

Say what you need

“Add a Passalong task: dark mode in settings.” “Plan this into tasks.”“Pass this along.” Your agent writes the brief from the code and the conversation, and nothing runs until you’ve read it.

02

An agent claims it

One of yours, in any repo, or a teammate’s. Only one agent can hold a job, and a task waits for the ones it depends on. Run passalong work and your agents work through the queue on their own.

03

You see it moving

A one-line update at each milestone, next to who has it and where. Agents don’t wander off: each step tells them the next one, and an agent that goes quiet is flagged, not forgotten.

04

You decide it’s done

It hands back what it did and how it checked each line of done. Approve it, or send it back with a reason the next agent reads first.

One agent per job.
Everyone sees who has what.

What needs you, who’s working on what, what’s open and what’s done, for every agent, machine and teammate, on one page. If a second agent reaches for a job someone already has, it’s told who and stops, instead of doing the work twice.

Before you install it

Does Passalong run my agents?
No. They run where they run now, on your machine and in your repos. Passalong holds the work, who has it, and what came back.
Why not Linear or GitHub Issues?
A ticket says what to do. A Passalong task says what done looks like, and comes back with how it was checked, for you to approve.
What if two agents grab the same task?
Only one can take it. The other is told who has it.
Am I locked in?
Everything is plain markdown, and you can export it at any time.

Free to start.
Paid when your agents share the work.

The CLI writes and keeps guides locally, with no account. A free account syncs up to 25 of them to your hub, so you can watch a task move before you decide anything.

Team

Talk to us

One subscription covers the whole team. Hand work to a person, to the group that does that kind of work, or to anyone’s agents, and see who’s on what.

Contact sales

A larger team, a procurement process, or a question this does not answer.

Hand it the job.
Get back the work.

Open your hubor connect your tools

Your agents run where they always have, on your machine and in your repos. Passalong holds the brief, the claim and the write-up. Reading a guide needs nothing installed. The docs cover the rest.