Daily Engineering Digest Agent
Posts one Slack digest every weekday morning covering what shipped, what is stuck and who is waiting on a decision, pulled straight from Linear.
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.
Choose which agent runs it
NoClick's built-in models work out of the box — or bring Claude Code, Codex, and other coding agents on your own subscription.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
About this agent
Standup exists because nobody can see across teams. Every weekday morning this agent reads the last day of Linear activity for the teams you name and posts one Slack message: what shipped, what moved, what is stuck and who is waiting on a person. It is for engineering leads tired of asking for status, and it holds up because it never guesses - every line points at a real issue.
What people use it for
- Replace the status standup - Gumloop posts a 24 hour summary to Slack each morning and stopped asking people for updates. This is that digest for Linear, so standup starts from what everyone already read.
- Catch stuck work on day three - Anything blocked or untouched for three days lands in the STUCK section with what it is waiting on, so a blocker gets named while it is still a day of delay and not a week.
- Give leadership one place to look - Your team context tells the agent what leadership actually asks about, and the same digest answers it every morning. Nobody writes a status update by hand again.
- Cover every team at once - Shopify ran issue digests across 110+ teams. Name three teams or ten and each gets its own lines, including the ones that had a quiet day, which is usually the useful signal.
Before you fork
What does it need connected?
A Linear credential with read access to the teams you want covered, and a Slack channel to post in. During setup you describe your teams, who owns the digest, and how blunt you want it. The agent only reads from Linear, it never changes an issue.
Can I change when it runs, and what does that cost?
The schedule step controls the time and timezone, and it is set to weekday mornings so Monday automatically covers the weekend. That is roughly 22 runs a month, one per working day, regardless of how many issues your teams move. Moving it to twice a day simply doubles that.
What if the digest says something wrong?
It reports what Linear says and nothing else, so a wrong owner or a stale status in the digest is a wrong owner or stale status in Linear. It will never invent an ETA or a reason for a stall, and if a team returns nothing or a call fails it says so in a NOT SEEN line rather than quietly omitting the team.
Run it with your coding agent
More agents like this
Put Daily Engineering Digest Agent to work
Free to start. Guided setup, a test run against staged conversations, and it's live.