Yes. Described once, then it shows up without being asked

What runs well on a schedule?

Digests: a morning sweep of named sources, industry news, competitor changelogs and the subreddit that matters, compressed into one note that replaces 45 minutes of tab-cycling.

Reports: the same numbers from the same logged-in dashboards every week, assembled into the same template, per the examples in AI for repetitive browser work. Checks: pages watched for movement, the competitor-monitoring pattern. Refreshes: prospect lists, stock, listings, re-verified on cadence.

How does an unattended run stay under control?

The same approval model as everything else, which matters more precisely because you are not watching. Reads and compiling flow. A routine that wants to send, write or change something consequential stops on a card and waits.

So the digest is on your desk and the drafted follow-ups are behind approval cards rather than in recipients’ inboxes. Ask Always mode in Settings → AI permissions tightens it further, and the pauses stay visible in the run, in the shape you can inspect at real runs.

A routine against a cron job

A cron job runs code somebody wrote and maintains, and it breaks silently the week a page changes. A routine runs a paragraph of English and survives the redesign, because the companion reads the page rather than a selector.

It also reaches the logged-in web without any credential hand-over, which is the half of the workday a script cannot enter without your passwords stored somewhere.

Setting your first one up

Start with the morning digest: five named sources, one note, delivered before you sit down.

Watch the first run and tighten the wording wherever it wandered.

Once a pass runs clean, save it as a Skill and it becomes one line to reuse inside any other instruction, or a routine that keeps running on its own cadence.

Frequently asked questions