Automation & advanced

Beyond interactive work, Anvil can run on a schedule, take orders across a fleet, and be driven remotely — with the same permission model keeping it honest.

Routines

A routine is work Anvil runs on its own schedule — a recurring task, a check, a report. Define it once; it runs when due and tells you what happened. Routines respect the same permissions as an interactive session: a destructive step still needs the mode that allows it.

Fleet orders

Hand a task to one or many machines on your fleet as an order. The order carries the work and its changeset; a bot picks it up, runs it, and reports back — and if it stops at a step it isn't allowed to take, it waits on your approval rather than guessing.

[!NOTE] Routines and orders run against your deployments — create and watch them from your command centre, running across your fleet.

Remote control

Pair a browser with a running Anvil and you get a live view you can watch and steer — the same session, rendered like a product, handed back and forth without losing history. The view is interactive: where a step needs a human (solving a CAPTCHA, say), you do it in the pane.

Advanced flags

For scripting and CI, Anvil exposes non-interactive entry points:

anvil prompt "…"     # run one prompt non-interactively
anvil continue       # resume the last session
anvil --check        # verify the install, PATH, completions
anvil --setup        # re-run first-time setup
anvil upgrade        # self-update to the latest release

See the command reference for the full list.

Related

• Your crew & fleet — the machines orders and routines run on.
• Security & vault — the permission model automation runs under.