Automations

An automation starts work for you without you being there. It runs a message as a new session, or a workflow, at a time you set or when something happens in Fleet.

Each run is an ordinary session. It appears in your session list like any other, and you can open it, steer it and review it.

1. Choose Automations in the rail on the left, then New automation.
2. Type what it should do and when, in one sentence: Every Monday at 9, summarise the open pull requests.
3. Read the summary under the box. It says when it runs next and what each run does. If it is wrong, fix it with the chips.
4. Choose a folder. A run in a git repository gets a new worktree by default, so your own checkout is never touched.
5. Press Enter, or choose Create automation.

Fleet reads the schedule out of your sentence. It doesn’t ask a model, so it costs nothing. It understands phrases such as every day at 6pm, weekdays, every Friday, every 2 hours, monthly on the 1st, tomorrow morning and once next Tuesday. The words it used are highlighted. Times are on your computer’s clock, and the automation keeps that time zone.

Say on Friday and Fleet asks whether you mean every Friday or just once.

Chip	What it does
When	Shows what Fleet understood. Choose it to pick Every day, Weekdays, a day of the week, Every hour, Once on a date, or a custom cron expression. Choosing here takes over from your sentence. It shows When? if Fleet found no schedule.
Runs	a session gives the agent your message. a workflow runs a workflow from the Library. It only appears with Workflows switched on.
Folder, Workspace, Base	Where each run happens. They work as they do on the new-session page.
New session each run	Each run starts fresh. Choose Same session each run and later runs continue the first run’s session.
Agent and model	Pick them as you would for a session. A workflow takes its models from your Workflows settings instead.
…	The automation’s Name, and Skip a run while the last one is still going, so a slow run never piles up behind itself.

If you have added other machines, a chip lets you choose which one runs it.

In the When chip, under When something happens, you can pick an event instead of a time: A session starts, A session is archived, A session is deleted, A sub agent starts or A sub agent’s status changes.

Open an automation from the list to see its page.

• Run now starts a run right away. The automation doesn’t have to be on.
• The switch next to its name turns it On or Off. An automation that is off keeps its place in the list, dimmed, with Off on its row.
• The … menu has Delete. The automation stops. The sessions its runs started stay in Sessions.
• To change one, edit it in the box on its page. Save changes appears when something is different.

A Once automation switches itself off after it runs.

The automation’s page lists every run, with its time and what started it: nothing for a normal schedule, or Run now, Once, Caught up or the event. The list header says how many have finished.

State	Meaning
Starting, Running	The run is going.
Needs you	A session or workflow step is waiting for you.
Done, Ended	The run finished.
Failed	The run failed. The reason is under it.
Skipped	The run didn’t start, with the reason.

Choose a run to open its session, or its workflow run. A workflow run says Started by the automation.

In the list on the left, each row shows Running, Needs you or Failed from its latest run. Otherwise it shows when it runs next, or Off.

Automations run while Fleet is running. A run you missed while it was closed still happens, late, if it was less than 3 hours overdue when Fleet started. Older ones are recorded as Skipped, and the run says Fleet wasn’t running.

• Workflows: put a whole process, with approval steps, on a schedule.
• Your first session: the folder, workspace and base chips explained.
• Sessions and worktrees: find, archive and clean up the sessions runs leave behind.