While you talk to your agent, your project writes itself down on a board your whole team can see.
It skipped a route, decided against a refactor, and left something odd in the invoice job. You wrote none of that down, and it was on the board before the session ended.
The agent wrote these three while it worked, under its own name. Nobody opened a form, and nobody had to remember them at the end of the day.
#
Description
Status
Priority
Type
Tags
Assignees
31
Mobile route: the signing key is missing
Blocked
High
bug
#auth#mobile
Rafael Souza
32
Legacy client stays until the mobile release
To do
Medium
chore
#mobile
Rafael Souza
33
The invoice job retries forever on a 500
To do
High
bug
#billing
Marina Alves
Every change on a card keeps the value it had before, the time it happened, and the hand that did it: the person, or the person's agent.
Move sessions off the cookie before the mobile release11
Audit history8 events
statusbodystatusattachmentassigneesstatusdeliveriesYour agent already keeps notes for itself, in its own file, on your machine. Nobody else can read them. This one belongs to the project: one gotcha, written once, and every session that touches that part opens it first. Yours, and the two people sitting next to you.
Three sessions, one memory
your session~/work/my-projectMarina~/work/my-project
Tomas~/dev/my-projectProject reference8 entries
Deploy
Open before any release. The command in the readme deletes production data.
Use the one in deploy/release.sh, which dumps first and refuses to run against production without the flag. Two people have hit this; the second one lost a staging database and half a day.
Gotcha
Touching money? Read this before you divide.
Two places used to divide by 100 for display and rounded down. If a total is off by one cent, this is why.
Decision
Anyone touching auth needs this first.
The mobile client cannot hold cookies across the payment sheet. The cookie path stays until the mobile release ships, then it goes.
Nobody writes a status update here. The cards kept the record while the work was happening, so the questions people ask on a Monday already have an answer.
The line starts at the first card and ends today. Each pin is a delivery you sealed and handed over.
80% done 75 of 94 cards
The bars are what closed. The line behind them is what came in on the same day, so you can see the week filling up as fast as it empties.
ClosedCreated
Counted by person, never by tool. Which hand made each change, yours or your agent's, lives on the card itself.
Person
Created
Worked
Closed
Pace
Last
Marina Alves
19
20
17
now
Tomas Reis
20
20
16
now
Rafael Souza
19
33
15
2d
Priya Raman
18
18
14
1d
Jonas Weber
17
17
13
now
Give the client a login instead of a status email. One project, read only, and the same numbers you are looking at, updated the second a card moves.
80%of the project done
75 done 5 in progress 14 to do 21 closed in the last 7 days
Backlog5
Multi-currency payouts87
To do7
Refunds over 90 days need an approval step81
In progress5
Guest checkout without an account74
Blocked2
Drop the unused coupon table79
Done73
Stripe webhook retries drop duplicate events1
Dropped2
Accept crypto at checkout85
What they get
A login of their own, to one project
Progress that moves while they watch
A request box: what they ask lands on your board as a card
A signed PDF of everything that shipped in a window
What they never see
Your other projects
The project memory
Your team, and who did what
Anything you did not share with them
Agents never take a seat. On a paid plan, neither does anyone on your team.
$0
Free forever. No card.
Three projects, and the two or three people working on them.
Start free$19/mo $16/mo
Billed monthly $190 billed yearly
A team with several projects going, and clients who keep asking.
Start with Team$49/mo $41/mo
Billed monthly $490 billed yearly
A shop that takes on a new project every month, with no ceiling.
Start with StudioDrop back to Free whenever you want. Nothing you wrote is deleted, and it stays yours to export.