The goal is to start the day already briefed — not to spend the first hour becoming briefed. What follows isn't groundbreaking. It's just what pushing my own boundaries looks like in practice.
The problem
As a Tech Lead of a larger team, my mornings used to look something like this: open email, skim through multiple newsletters I subscribed to for staying current on AI and dev topics, switch to Slack, scroll through everything I missed, try to figure out what actually needs my attention, then check what code went into the repo in the last 24 hours. By the time I was done "catching up," a good chunk of the morning was gone.
I knew there had to be a better way.
Starting with Claude Cowork
Claude's desktop app has a feature called Cowork, and within that, you can set up Scheduled tasks — automated tasks that run on a schedule. I set up two that run every morning:
Newsletter digest: This one pulls in all the newsletters I received the day before and summarizes them for me, grouped by topic — AI-related first, then dev, then everything else. Instead of opening each email and scanning for what's relevant, I get a curated briefing in seconds.
Slack summary: This gives me a full summary of yesterday's Slack conversations across channels, and more importantly, flags what actually needs my attention. No more scrolling through hundreds of messages trying to separate signal from noise.
The only downside? The Claude desktop app needs to be open and running for these to kick in. It's not a dealbreaker, but worth knowing.
I'll be honest — the idea wasn't entirely mine. When you set up a new Scheduled task in Cowork, a Daily Brief is literally the example they suggest. I just happened to already be poking around with something similar. A lucky coincidence.
Taking it a step further with Claude Code
One of the hardest parts of leading a larger team is keeping tabs on everything that changes in code. PRs get merged, features get shipped, bugs get fixed — and it's nearly impossible to review it all manually without it becoming a full-time job.
So I set up a Routine in Claude Code — that's what they call scheduled automated runs — that kicks in every weekday morning at 09:30. It runs headless, no window required. It scans the develop branches across all three of our repos, picks up everything that merged since yesterday (or since Friday on Mondays), and produces an HTML report I can open straight away.
It's not just a list of commits. It reads the actual diffs for anything non-trivial, scores complexity, flags risky patterns — broad refactors, missing tests, pre-release SDK pins landing where they shouldn't — and calls out when the same feature landed across multiple repos as a coordinated rollout. It's like having a reviewer who never sleeps and never skips a merge.
The bigger picture
None of this is Claude-specific. Most major AI platforms have some form of scheduling now — ChatGPT just launched theirs — and the rest won't be far behind.
But scheduling isn't even the most important part. The real work is building the prompt — deciding what you want surfaced, how it should be structured, what noise to filter out. Once you have that, the platform doing the running almost doesn't matter. Any agent that can read your data and write a file can produce a digest you open in a browser. Local HTML works everywhere. No dashboard, no extra subscription.
And if scheduling isn't an option where you are, just run it manually. It still takes thirty seconds. It still saves you the fifteen minutes of scrolling. The automation is convenient; the prompt is the thing.
I'm not pushing the boundaries of what's possible with AI — someone else has almost certainly done all of this and more. But I am pushing my own boundaries, and that's what matters to me.
Top comments (0)