The job is done
before you sit down.

The prompt

Every weekday at 8, check my supplier portal for
new invoices and tell me the total. If something
needs a decision, say so instead of guessing.

HailBrowser proposes the schedule in the chat. It is only created when you press Create, so a page cannot add one behind your back.

What happens

1. The schedule is stored with chrome.alarms and appears in the schedule list.
2. At the chosen time it opens a background tab, runs the goal and closes what it opened.
3. A notification reports the result, and the run is saved in History like any other chat.
4. If it needs a login, a payment or a CAPTCHA, it stops and tells you rather than waiting silently.

Stricter when nobody is watching

Scheduled runs follow the same tools but a tighter rule: they never send, buy, post or delete anything unless the goal says so. The goal is the permission. “Check the total” does not authorise “pay the invoice”.

That also means a scheduled job will not push through ambiguity. It reports what needs you, which is usually the point.

What to check

• The first run. Watch it once before you trust it on a schedule.
• The notification text, not just that a notification arrived.
• The queue. One run happens at a time, so a long job at 9 delays the job scheduled for 9:05.

What can go wrong

• Chrome was closed. The job runs once at the next start, not once for every missed interval.
• The site logged you out. The run stops and asks, or reports that it could not sign in.
• Another run is in progress. The job waits in the queue rather than interleaving clicks.
• The site changed. A moved button costs a decision, not a silent failure; the run reports where it stopped.