Working the fleetSeveral agents running at once is only useful if something tells you where to look. That is the whole design: the glow, the rail, and asks that arrive with enough context to answer in one pass.The attention modelA card only draws attention when a decision waits: a plan to approve, a question to answer, a review to take. Progress does not animate, and nothing else pulses. In the board view those cards get a filled, radiating border in their stage colour; everything else stays quiet.In the session view the left rail queues the same cards by why they wait, questions first, then plans, then reviews, so you can work top to bottom and always know what is next.What an ask carriesNever a bare "proceed?". Every ask arrives with the plan, the diff, the risk stated in one line, and the two or three answers you can actually give. If the agent needs a judgement only you can make, it says which judgement.The autonomy dialPer project, and per seat on Crew, four positions:SETTINGMEANINGAsk at every stepEvery stage transition needs your tap. Useful for a repository you do not trust yet.Ask at planThe default. You approve the plan, then it runs to Review.Ask only when riskyMigrations, deletions, dependency changes and anything touching declared risk paths still stop.Run to ReviewIt works uninterrupted and stops at the review gate. It never delivers without you.
Shift reportsWhat happened while you were away, in one screen: cards closed with links, cards waiting with their age, failures with the failing step, and token spend by project. On demand, or on a schedule (morning, end of day). Written as markdown to <config>/reports/ so you can keep or share them.Phone, sync and devicesThe phone app is for deciding, not for reading code: sessions, session chat, board, capture and the shift report. A plan is fully approvable from bed. It exists because sync exists, so it is Solo and up.SYNCSNEVER SYNCSCards, plans, board state, decisions, memoryRepositories, worktrees, diffs, transcripts, rewind history, the code index
Synced content is encrypted with a key you hold; the sync server stores ciphertext. Three devices on Solo, per person on Crew and Fleet, with remote sign-out per device.ALPHANo sync, no phone app and no shift-report scheduling in the alpha: cards live on one machine until the beta.