Skip to main content
Authoring an agent is local, file-first work: scaffold a bundle, describe the goal, validate, then deploy and activate. Run any command below with npx fimo@latest <command> for the latest CLI.

​
Scaffold a bundle

Start from one of the bundled starter templates:
create writes agents/<name>/ — including a config.yaml and a GOAL.md — and requires you to be inside a real Fimo project so it never leaks files into a stray directory. The five bundled templates are _default, seo-audit, content-translator, broken-link-sweeper, and post-deploy-check.
--description writes a one-line tagline into config.yaml that surfaces in Fimo Studio’s agents list.

​
Write the goal

GOAL.md is the heart of the bundle — it states, in plain language, what the agent should accomplish on each run. If the agent needs a secret (say an API key), request it in config and store the value separately:
Integration access is an allowlist in config.yaml — anything you don’t list is off-limits to the agent.

​
Validate, deploy, activate

1

Validate locally

Omit the name to validate every bundle. Add --json for CI; the exit code is non-zero on any failure.
2

Deploy the bundle

The bundle reaches the server through git, so it must be deployed before it can be activated or run.
3

Activate its triggers

This wires the agent’s declared triggers on the environment. Cloud triggers (schedule / webhook) require notifications.email_recipients in fimo-config.json.

​
What’s next

Schedules

Put your agent on a cron and trigger manual runs.

Runs, reports & logs

See what each run produced.

Agents overview

The bundle format and why agents live in git.