An automation runs a task you describe on a repeating schedule: a daily
summary, a weekly report, a recurring check.
The one thing to understand first
Automations are scheduled in the cloud but executed by your desktop app.
- The schedule is stored server-side, so it survives restarts and does not drift
if your machine is off.
- The run itself needs your desktop app open and signed in at the scheduled
time.
If nothing is available to run it, the occurrence is recorded as skipped and the
automation is flagged as needing attention. You will see that it did not run —
it does not fail silently — but it does not run later either.
Closing your laptop at 18:00 means an automation scheduled for 02:00 will not
run. Schedule for times your machine is normally on and awake.
Turning it on
Automations are off by default.
- Settings → Preferences, enable Automations.
- An Automations section appears in the sidebar.
Enabling it also registers this machine as your automation runner — which is
what actually executes the runs.
Creating one
Give it a name, then write the instructions in plain language, exactly as you
would describe the task in a chat. This is also where you invoke a skill, for
example “run the weekly-report skill for the Vienna office and email me the
summary”.
Then pick a model and a schedule:
There is no cron expression — the schedule types above are all of them.
Use Run now to execute immediately without waiting. That is the fastest way
to check your instructions do what you expect before trusting them to a
schedule.
Reviewing runs
Each automation keeps its run history with a timeline of what happened, so you
can see what a run did rather than just whether it succeeded.
If an automation is marked as needing attention, the usual cause is that no
desktop was available when it was due. 
