Codex Engineer
Agent in the cast of your workspace
- Works for
- You
- How we recognise it
- Run key ending 4f2a
- Reports runs
- Yes, 214 in the last 30 days
- Last run
- 01:20 to 03:05, 1h 45m declared
Thursday 29 October
A diary for you and your agents
DevDiary reads your GitHub and your agents’ run reports, then writes each day down: who did what, in which session, on which stream.
An example day: you, three agents and a bot.
You
Person in the cast of your workspace
- GitHub
- your login, two emails
- How we recognise it
- Commits, reviews, the no-reply email
- Your time
- Inferred from your sessions
- Today
- 3 sessions, 6h 30m
Dependabot
Bot in the cast of your workspace
- GitHub
- dependabot[bot]
- How we recognise it
- Its GitHub account
- In the diary
- One Upkeep line a day
- Last change
- Bumped rack to 3.1.12
Every change has a name
Commits, pull requests and reviews come from GitHub. Agent runs report themselves with a key. DevDiary puts the two together, so each change names the person or agent who made it. Names it cannot place wait in Cast until you claim them.
Ten minutes, then every day
What a day holds
While you slept
Agents work the night shift. At 8:00 in your time zone the briefing is ready: what merged, what waits on you, and one line for each agent that ran while you were away.
On weekdays it comes by email too.
Morning briefing, 08:00
Two agents ran overnight. One PR waits on you.
- Codex Engineer ran the nightly backfill, 1h 45m declared.
- PR Fixer rebased PR #409 after a conflict.
- Dependabot bumped rack to 3.1.12.
Needs you Review PR #412, retry with backoff
How many agent runs a day?
10,950 runs a year
Runs a day times 365. Each one lands in the diary with its agent, its minutes and the works it touched, or one quiet line if it touched none.
Free to start
Every day page, session and stream for three months, with no card. Pro keeps your whole history and adds chat over your diary.
$9.99a month
- Everything in Free
- Your whole history, kept
- Chat over your diary
- Priority support
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.
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.
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.
Briefing When does the morning briefing arrive?
It is ready at 8:00 in your own time zone, and on weekdays it also comes by email. It covers yesterday and the night: what merged, what waits on you, and one line for each agent that ran while you were away.
From our own diary
Read the blog24 August 2025
Cloud-Based Developer Diaries vs. Traditional Documentation
In the ever-evolving landscape of software development, how we track, document, and reflect on our work has undergone significant transformation. Traditional...
11 August 2025
The Power of Reflection in Software Development
In the fast-paced world of software development, we're constantly moving forward—debugging that critical issue, implementing new features, or learning the la...
21 June 2025
Time Management for Developers
In today's fast-paced software development landscape, managing time effectively isn't just a nice-to-have skill—it's essential for survival and success. As d...
