Automate Your AI Daily Brief Without Leaving Your Laptop On

A third workflow, same person, same habit of automating things

Bob had already built out an evening reflection and a weekly review with Claude connected to xTiles. This time the question was narrower: how to make a daily brief run entirely on its own, without needing a laptop left open or a personal automation setup wired through GitHub.

The old way needed GitHub and a machine that stayed on

Scheduling a recurring AI task used to mean routing it through Claude Code and a GitHub-connected setup — workable, but it added real technical overhead for something that should just run in the background every morning.

Native scheduling changes what's required

Claude has since rolled out its own scheduled-task capability, so a recurring workflow like a daily brief can now be set up directly inside Claude — no GitHub connection, no code, no separate automation layer to maintain. The rollout reached different accounts at different times, but once it's available, setup is a matter of creating the scheduled task directly rather than wiring a workaround.

What that means in practice: nothing has to stay open

Because the schedule runs on Claude's side rather than on a local machine, the brief still generates whether or not a laptop is open at the time. The setup for connecting Claude to xTiles in the first place is covered in a dedicated guide to Claude routines versus scheduled tasks if you want the full walkthrough of the options.

A small detail that made the automation feel real

What convinced Bob it was actually working wasn't a bigger feature — it was a notification arriving the moment Claude updated his xTiles with news and events, confirming the brief had run without him having to check manually or remember to trigger it himself.

Automating a daily habit tends to lead to automating the next one

With the daily brief running on its own, Bob's next request was a different kind of automation entirely: pulling in expense and income data he already tracks elsewhere so it gets organized automatically instead of manually. That workflow is still being built out on the product side, but the instinct behind the request is the same one that drove the first three: once one recurring task stops requiring manual attention, the next candidate for automation gets obvious fast.

Frequently asked questions

Do I need to keep my laptop open for a scheduled AI brief to run?

No. With Claude's native scheduled-task capability, the schedule runs on Claude's side rather than on a local machine, so it generates whether or not your laptop is open.

Do I still need GitHub or Claude Code to schedule a recurring brief?

Not anymore. That was the old workaround. Native scheduling lets you create a recurring task directly inside Claude instead.

How do I know the automated brief actually ran?

A notification arrives when Claude updates your xTiles content, confirming the task ran without needing to check manually.

Is this the same as the Evening Reflection or Weekly Review workflows?

No — those are separate workflows. This covers the scheduling mechanism itself, which any recurring workflow, including those, can use.

Does this feature roll out to every account at the same time?

Rollout has happened gradually across accounts rather than all at once, so availability may vary slightly by account.

Can this same approach automate something other than a daily brief?

In principle, yes — any recurring request pointed at connected data can use the same scheduling mechanism, though more complex workflows (like structured expense tracking) may still need dedicated product support to work smoothly.