Daily Engineering Digest Agent with Hermes
The digest lives or dies on judgment: what counts as stuck, whether a blocker is work or a person, and which of ten state changes earns a line. Hermes is an open-model agent whose strength is general reasoning, which is the whole of this job, since none of it is code. It reads Linear, decides what matters, and posts once.
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 Hermes
Preselected for this page — connect your Hermes 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 Hermes for this agent
Sorting signal from movement
Plenty of issues change state overnight and few of them concern leadership. Deciding which lines earn their place is reasoning, and that is what this harness offers.
Open models on internal data
Teams that prefer an open-model foundation for anything touching their roadmap can have that and still keep the Linear and Slack tools the digest depends on.
Before you fork
What stops it from inventing progress on a quiet day?
The instructions rather than the harness. Every line has to point at an issue it read, empty fields are written as unassigned or no update, and a team that returns nothing gets a NOT SEEN line naming the reason instead of vanishing. Run the quiet Friday scenario before trusting it, since padding is most tempting exactly there.
Run it with a different agent
Put Daily Engineering Digest Agent to work on Hermes
Free to start. Guided setup, a test run against staged conversations, and it's live.