Docs
Automations
An automation sends a message to sessions at the times you pick: every weekday at 9:00, every hour, on weekends. The sessions take it as if you had written it, and get to work.
What an automation is
A name, a schedule, the sessions to write to, a message and a switch. Open Automations: the button beside Settings under the session list on iPhone and iPad, the one in the sidebar of the web app. Each computer has its own list. A row reads morning-review · Weekdays at 9:00 → Review bot, with how it last ran and when it runs next.
The switch pauses one without deleting it. Run now sends the message at once, even when it is switched off. Deleting one stops it; its sessions stay.
When it runs
| Repeat | When |
|---|---|
| Every day | Each day at the time you pick. |
| Weekdays | Monday to Friday at the time you pick. |
| Weekends | Saturday and Sunday at the time you pick. |
| Every hour | Each hour, at the minute you pick. |
| Custom | The days you pick, at the time you pick. |
Times are the computer's local time.
What it does
Each run sends the message to every session of Send to, sessions of the same computer, as a prompt: one that is working gets it once its turn ends. In the chat the message is marked as coming from the automation. To start fresh work on a schedule, give the automation a session made for it, such as a review session that follows main in its own copy.
Skipped and failed runs
- A session still working on the previous run's message is skipped: an hourly message whose work takes two hours never piles up.
- The last run shows as sent to the number of sessions that got it, skipped when none did, or failed with the reason.
- A deleted session is taken out of the automations that wrote to it; one left with no session is switched off.
Where they live
On the computer, in ~/.slashcode/automations.json, readable by you alone; nothing about them is kept by the relay. They run only while the computer is on and its daemon running: a time missed while it was off or asleep is not caught up. Your devices see and change them only while the computer is online. A computer holds at most 50.
Made by an agent
An agent can read, create, change and delete automations with its Slashcode tools: ask it to “send the review session a message every weekday at 9 to look at yesterday's commits”. Creating, changing or deleting one asks Change automations first, under the harness's permission mode.