Using Xome
Automations.
Give the agent a standing instruction and let it run on a schedule, honestly scoped to what a browser can do.
Creating one
Settings → Automations. An automation is an instruction (“summarize today's unread email”), a trigger, a provider to run it with, and a list of integrations it's pre-approved to write to. Anything outside that pre-approval is declined automatically, headless runs never get a blank check.
How scheduling works
- Run now executes immediately and records the result in the audit log.
- Time-of-day triggers run while Xome is open: an in-tab scheduler fires them at the set time, once a day, with a browser notification on completion.
- Every run is audited: when it ran, which tools it called, and the outcome.
Being local-first cuts both ways: nothing runs with the tab closed. There is no Xome server that could act for you, that's the point. For always-on schedules you'd need the (planned) private-server tier or your own relay.