Daily Engineering Digest Agent with Codex
Underneath the writing this is a data job: pull issues per team, bucket them by what changed, count opened, closed and in progress, and lay it out in the same five sections every morning. Codex is strong on that sort of concrete API and data work, and the shape never varies from one day to the next. What comes out is a single Slack message waiting before standup.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Weekday 08:00 digest tick
It is Tuesday 08:00 in Berlin and standup is at 09:15. Overnight the Platform and Payments teams closed nine issues and moved three into review, while the checkout migration has not changed state since Friday.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Linear
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Team context
Your Linear teams and projects, who owns this digest, and what your leadership actually asks about each morning.
Digest style
Which sections your team really reads, how blunt the tone should be, and how long the digest can run before people skim past it.
Runs on Codex
Preselected for this page — connect your Codex account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why Codex for this agent
The NUMBERS line is arithmetic
Opened, closed and in progress per team has to be correct, not eloquent. Careful data handling is what this harness is steady at.
Same shape every morning
Fixed sections in a fixed order is a tightly scoped brief, and tightly scoped is where Codex needs the least supervision.
Before you fork
Can I change when it runs, and does the harness affect that?
The schedule step owns the time and timezone and is independent of which harness you pick, so moving to Codex leaves your posting time alone. It ships set to weekday mornings, which is why Monday's run covers the weekend. Shift it and the instructions still hold, because the lookback follows the day rather than a hardcoded hour.
Run it with a different agent
Put Daily Engineering Digest Agent to work on Codex
Free to start. Guided setup, a test run against staged conversations, and it's live.