Skip to main content
Every agent run creates a session on the server. The CLI lets you list those sessions and read the report — the agent’s final message, captured when the run finishes.

​
List past runs

Each row shows the session id, start time, duration, status, trigger, environment, and cost. The default limit is 20; --env filters to a single environment.

​
Read a run’s report

The report is the fastest way to see what a run actually produced — for a read-only agent it is the output (an audit), and for a write agent it’s a “what I changed” summary:
With no --session, the latest run is used; combine with --env to scope. If a run hasn’t finished or produced no message, the command says so and shows the stop reason when there is one.

​
Logs

The log-streaming endpoint is still a server-side stub, so logs currently prints a placeholder rather than live log lines. To read a finished run’s output today, use fimo agents report.

​
What’s next

Schedules

Trigger runs on a cron or on demand.

Create an agent

Author and activate a bundle.

Agents overview

How activations and run sessions relate.