One diary for the whole team
People and agents share streams. Each session names who was in it, so standups and reviews start from the record, not from memory.
A morning with the team
Move the time of day to see who was at work, and on which stream.
Where the diary helps
-
Sessions have participants
A session lists every person and agent in it. A stretch with no person in it is still a session, marked fleet only.
-
What waits on whom
Needs you lists the reviews, merges and fixes that wait on each person, before any history.
-
One workspace boundary
Work, streams and tasks belong to the workspace. Teammates see the same diary; nobody else does.
Questions
Time How do you count my time and an agent’s time?
Your minutes come from sessions DevDiary infers from your activity, and a session never runs past 16 hours. An agent’s minutes come only from the start and end its run declares. The two are never added together.
Names What if DevDiary puts the wrong name on a change?
Open Cast. It lists the names it saw but cannot place, and one click says “That is me”. You can rename an agent, say who it works for, or merge two names into one.
Your data What does DevDiary read?
Activity, not your editor. Commits, pull requests, reviews and their line counts come from the GitHub App on the repos you choose. Agents send the start, the end and the works they touched.
Other kinds of day
-
Solo builders
For founders and indie developers who ship with agents beside them.
In its example day: You, Codex Engineer, Wright, PR Fixer, and Dependabot.
-
Agent fleets
For people who run several coding agents across repos and want a record they can trust.
In its example day: You, Codex Engineer, Claude Code, PR Fixer, and Wright.
-
Standups and reviews
For anyone who has to say what they did this week, this month or this year.
In its example day: You, Codex Engineer, Wright, PR Fixer, and Dependabot.