Skip to main content
Fimo runs recurring work two ways: agents activated with a schedule trigger, and scheduled commands that run any CLI command on a cron. Both execute in the project’s environment runtime — not on your machine.

​
Run an agent on demand

Once an agent is deployed and activated, trigger a run yourself instead of waiting for its cron:
run refuses if agents/<name>/ has uncommitted changes — the server dispatches the deployed bundle, so deploy first. Pass --skip-drift-check to dispatch the deployed version anyway.

​
Scheduled commands

fimo schedules runs any command — a publish, a validation, a test script — on a cron for the current environment:
Cron uses standard five-field syntax, and schedules must not run more often than every five minutes. On each run, Fimo prepares the environment, refreshes project files and dependencies, authenticates as the schedule owner, then runs your command from the project root.
list, run, and delete operate on the current checkout’s environment unless you pass --env <name>. A failed command marks the schedule failed and exits non-zero.

​
What’s next

Runs, reports & logs

Inspect the sessions your schedules produce.

Create an agent

Author a bundle before you schedule it.

Environments

How environments scope schedules and runs.