See, switch on and run automations
All your automations are on one page: More → Automations in the sidebar. A collection’s menu also has Automations: the same table, with only that collection’s automations.
The table
Each row is one automation.
| Column | What it shows |
|---|---|
| On | The checkbox. Ticked: the automation runs. Empty: it never runs by itself. |
| Name, Trigger, Collection | What it is called, what starts it (a schedule, an entry is created, a value changes) and where it works. |
| Does | What it does, in one sentence. |
| Status | “Active”, “Off”, or a red badge when the last run failed or a switched-on schedule has no next run. |
| Last run | When it last ran. Point at it to see how that run ended. |
| Next run | When a schedule runs next. |
The menu at the end of a row has Run now (in the desktop app), Edit JSON, Duplicate, Publish to the Library and Delete. Delete shows an Undo toast.
Switch one on or off
Tick the checkbox. The page changes at once. Only the switch changes: the rest of the automation stays as it is. A schedule you switch on shows its next run.
You switch an automation on or off here, in the app. Your AI, kzx and MCP can do it too, but only when you tick
“AI can make and switch on automations” in Settings → Security → AI permissions. It is off by default. See
Safety and approval. When you switch one on
here, it is yours, and it runs as yours.
Automations that came over from today’s app arrive switched off, so nothing runs twice while you use both apps. Switch each one on when you are ready. When you switch on one that was on in today’s app, it catches up the days since today’s app last ran it (14 days at most, see below).
If a change is refused, the page puts the box back and says so in one plain line.
When they run
- Schedules run in the desktop app: when it starts, then about every 30 seconds, and after your computer wakes up. The app runs them while its window is closed to the tray. After Quit, nothing runs until you open the app again.
- Only one copy of the app on a computer runs schedules. A second copy waits.
- An entry is created and a value changes run inside your change, at once. One Undo takes back your change and what the automation did because of it.
- Each run is one change in History, written as the automation. One Undo takes the whole run back.
Missed days
The app was closed at 01:00. When it starts again, it catches up.
- An automation that makes or changes entries runs once for each missed day, oldest first, up to 14 days back. A day runs only once, even after a restart or a crash. A day that already has its entry makes nothing new (“skipped, exists”).
- An automation that runs an agent runs once, for the newest missed time. It never replays old days, so you do not get five morning messages at once. This is how today’s app does it.
Run now
Run now (the row’s menu, for an automation on a schedule) makes one run at once, switched on or off.
- An automation that makes today’s entry makes it if today has none yet. Run it twice and the second run makes nothing (“skipped, exists”).
- Run now is not the scheduled run. The schedule still runs at its time (and finds today’s entry already there).
- The run shows in History. Undo takes it back.
Agent steps
A Run an agent step asks one of your agents to do something, for example “Send me a short motivational message”.
- The agent’s turn runs in the desktop app, with your own AI key. The run shows “queued” until the agent answers.
- The answer goes into that agent’s newest chat. If the step asks for a notification and your notifications are on, you also get one: “The Navy Seal · Morning motivation”.
- If the agent has nothing to say, it answers
NOTHING_TO_REPORT. Then there is no message and no notification, and the run says “nothing to report”. - With no AI key, the run fails and says why: “Add your OpenRouter key in Settings → Plan & billing → Your OpenRouter key to run agent steps.”
Run status words
| Word | Meaning |
|---|---|
| created | It made the entry. |
| skipped, exists | That day already had its entry, so it made nothing. |
| nothing to report | Nothing matched, or the agent had nothing to say. |
| queued | An agent step waits for the desktop app to run the agent. |
| delivered | The agent’s answer is in its chat. |
| failed | It did not finish. Point at the row’s status to see why. |
From the terminal
kzx can see and run your automations:
kzx automations list # every automation: on or off, last run, next runkzx automations run "Morning routine" # Run nowA name can be the automation’s name in any case, Automations/<name>, or its id.
kzx counts as an AI, even when you type the command yourself. So switching depends on your AI permissions:
kzx automations on "Done pile" # switch it onkzx automations off "Done pile" # switch it off- “AI can make and switch on automations” ticked: the automation switches. It is one change in History, and Undo takes it back. It runs with the AI’s limits until you switch it on yourself in the app.
- Not ticked (the default): nothing changes.
kzxsays where to allow it, printsOpen the permission: kaizendex://settings/security/ai-automations, and ends with an error code. The link opens Settings → Security with the checkbox highlighted.