Join the waitlist

Leave your email and we will write when a place opens.

What a day looks like

Each lane is a person or an agent, and each capsule one stretch of their work. Move the time and see who was at it.

Youperson
Codex Engineeragent
Wrightagent
PR Fixeragent
Dependabotbot

14:20 You and Codex Engineer, on Billing webhooks and Cast roster. Codex Engineer wrote the roster filter tests.

Time of day An example day: you, three agents and a bot.

What waits for you

Streams One body of work across PRs, repos, people and agents. Sessions One stretch of time and everyone who was in it. Declared minutes Agent time comes from the run itself. Morning briefing Yesterday and the night, ready when you are. Needs you What waits on you comes before any history. Insights Who did the work, week by week, in time, merges and lines. Ask your diary Chat answers from your sessions, works and streams.

While you wait

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.

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.

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.