Know what every agent did
Give each agent a run key. Its sessions arrive with a start, an end and the works they touched, next to the trail it left on GitHub.
A night with four agents
Move the time of day to see who was at work, and on which stream.
Where the diary helps
-
One key per agent
Claude Code, Codex, Paperclip agents, scripts and CI jobs each report their own runs. A runtime is never mistaken for the agent it runs.
-
Idle runs show up too
A run that named no work stays one quiet line. You see which agents produce changes and which only spend time.
-
Streams across repos
One body of work can span repos, PRs and agents. Streams keep it together, and you can rename, merge or split them.
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.
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.
-
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.