Daily Engineering Digest 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.