The record
The work is the record.
A developer's day now spans several agents, branches, reviews, meetings and test runs, and nobody has the time to report on it. Nothing here asks for a report: picking a task up, a commit, a meeting and a hand-back leave the record as they happen.
01
Pick up, build, hand back
A task is the handoff between sessions. Starting, spotting something on the way and ending are three verbs, and each one writes the task's timeline without a status update.
- Pickup — paste a task link and the server composes one bounded view — what to do, where to start, what to read first, which branch exists and what not to load. On a vt-<id> branch the SessionStart hook claims the task and prints it as the session starts.
- Spot — a defect or a follow-up seen mid-work is filed as a child of the task the moment it is seen — never batched for the end, never left in the chat.
- Hand back — one call lands the summary, the next steps and the pull request on the task, and its printed block is the hand-back. The trailer the CLI writes into each commit ties it to the task, and runs and pull requests move the status on their own.
02
A diary that keeps itself
Your Personal workspace keeps one board per day, and nobody else in any workspace sees it. Screens, the clipboard, notes and voice notes from Snap land on today's board and order themselves along the day.
- Days, weeks, months — a week lays seven days side by side and a month is a calendar; each month and each year gathers itself onto one board, done by the server at no AI cost. Timelapse replays a day.
- Meetings, transcribed on your own hardware — Snap records your microphone and the call into one track and transcribes it on the Mac as the meeting runs — or leaves that to the server's speech-to-text sidecar when your organisation turns server transcription on. On a self-hosted install the sidecar is one of your own services, so the audio never leaves your network, air-gapped included.
- Private until you promote it — a meeting promoted to a project becomes a meeting task with the recording and the transcript. Eve drafts the notes, the decisions and the action items when asked, and every action item waits in Intake for someone's verdict.
03
Todos that ripen, time that records itself
A todo waits for its moment instead of for someone to remember it, and the server, never a client, decides when the moment has come. Time works the same way: there is no timer to start.
- A typed moment — a pull request merging, a release being cut, a deploy to an environment, a file under a path being edited, a task being picked up or finished, a milestone or a due date — written once, as pr 472 merged or deployed prod.
- Where you already are — a ripe todo waits on your desk, prints at the start of an agent session in its project's repository — only the ones that fired — and speaks up once when an agent edits a file its path names.
- Human and agent time, apart — opt in per machine and agent sessions report their own activity while a local sampler notes the application in front and when you are idle; window titles are matched on the machine and thrown away. Human time, agent time and waiting stay separate, and a locked period stays as it was.