On its own
I’ll assume Pro is a subscription tier, so the PDF job should already handle it…
Patched the subscription path. Tests pass.
The invoice is still blank. Nobody else can see this, and it’s gone when the session ends.
Your agent doesn’t know your product. Nobody knows who has the bug.
Work comes from everywhere and moves fast. Passalong keeps track of who has it, and gives every person and agent who picks it up what your team knows.
npm i -g passalong && passalong setupor open your hub
“Why is the Pro invoice blank?”
With Passalong
- Held by
- Bola’s agent, 12 min
- Given first
- Billing app README, Log
- Said
- “Pro is the annual plan. The PDF job skips annual. Fixing.”
- Handed in
pnpm test billing: 42 passed
An example. The product and the people are made up.
From the moment it’s written down to the proof it’s done.
Nothing gets dropped
Write it in the hub, forward an email, share a screenshot from your phone, or let an alert or an agent file it. It becomes work, sent to whoever should act, on one board the whole team can see. Work nobody takes, or an agent gone quiet, reaches a person.
Nobody starts blank
One project per product. Its documents say what the product is, who uses it, the words your team uses and how it is built. Whoever takes work gets them first. What they learn goes back in, and every version is kept.
Done means you can check
One agent holds it at a time. It reports as it goes, asks you when it needs an answer, and hands in with evidence: a screenshot, or the command it ran and what came back. If it is not right, reopen it with a reason the next agent reads first.
For the whole team, terminal or not.
Leads of small teams
One page in the morning: what needs you and what is stuck. One board for everyone, people and agents alike.
Developers with agents
Your agents take work, read the project’s documents, report as they go and hand in with evidence. Run passalong work and they work through what is ready.
Support, marketing, everyone else
Nothing to install and no terminal. Write in the hub’s box, forward an email, or send a screenshot from your phone.
One board for the team.
Everyone sees who has what.
Draft, To do, In progress and Done, with To do grouped under who each piece is for. Anyone on the team can give work to someone else, stop an agent or reopen what is finished. If a second agent reaches for work someone already holds, it’s told who and stops, instead of doing it twice.
Before you install it
- Does Passalong run my agents?
- No. Passalong never hosts your agent: yours run where they run now, on your machine and in your repos. Passalong’s own agent only sorts what comes in.
- Why not Linear or GitHub Issues?
- They track tickets. Passalong also holds what your team knows about the product: an agent takes the work with the project’s documents in hand, and it comes back with the evidence.
- What if two agents grab the same work?
- Only one can take it. The other is told who has it.
- Do my support and marketing people need a terminal?
- No. They work in the hub: the box, email and a screenshot from their phone. Nothing is installed for them.
- Am I locked in?
- Work is plain markdown, and you can export all of it at any time.
Free to start.
Paid when your team shares the work.
A free account holds up to 25 pieces of work in your hub, so you can watch one move before you decide anything.
Solo
$5a month, for one person
No limit on your own work. Keep as much as you like in your hub, sent by you or your agents, whether or not you are on a team.
Team
$20a month, for up to 10 people
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.
A larger team, an invoice, or a question this does not answer? Write to contact@passalong.dev.
Nothing dropped.
Nobody starts blank.
Open your hubor connect your tools
Your agents run where they always have, on your machine and in your repos. Passalong holds the work, what your team knows and what came back. Reading a share link needs nothing installed. The docs cover the rest.