One person, a fleet, one diary
You set the work. Agents carry it through the night. The morning briefing says what moved, and the diary keeps the record for all of you.
A day with three agents
Move the time of day to see who was at work, and on which stream.
Where the diary helps
-
Wake up to the night’s work
Each agent run that happened while you slept is one line in the briefing, with the works it touched and the minutes it declared.
-
Your hours stay yours
Your minutes come from your own activity. An agent’s eight-hour run never inflates your day.
-
Every change has a name
Commits, PRs and reviews name you or the agent that made them, so you know what you wrote and what you only approved.
Questions
Agents Which agents work with DevDiary?
Any agent that can send a run report. Claude Code, Codex, Paperclip agents, a shell script or a CI job each get a run key. Agents that only act through GitHub, like review bots, are recognised by their account.
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.
Free plan Is there a free plan?
Yes. The free plan keeps every day page, session and stream for three months, with no card. Pro keeps your whole history and adds chat over your diary.
Other kinds of day
-
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.
-
Small teams
For teams of two to twenty people who share their repos with agents.
In its example day: You, Maya, Alex, Codex Engineer, 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.