Automations

An automation is a managed agent on a schedule. The built-in Signal sweep on each project is an automation, and so is any recurring agent you save in the Managed agents UI. Use ag automation to see what is scheduled in a space and to fire one without waiting for its next run. ag automation and ag automations are the same command.

`ag automation list`

List automations in a space. The signal column is yes for the built-in Signal sweep, and status is enabled or paused.

ag automation list [--space <id>] [--columns <list>] [--output <fmt>]

Option	Description
`--space`	Space ID (falls back to the saved context)
`--columns`	Comma-separated columns for text output (default: `id,name,trigger,signal,status,last_fired`)

Examples:

ag automation list
ag automation list --output json

`ag automation trigger`

Start a run of an automation now. The run skips the schedule’s next fire time but still passes the same admission checks as a scheduled run (cooloff, capacity, and the plan’s Signal issue limit). On success the command prints the new session’s jobId and the schedule resets to now plus the cadence. If the automation is blocked, the command errors and no session is started.

ag automation trigger <automation-id> [--prompt <text>] [--output <fmt>]

Option	Description
`--prompt`	Extra instructions appended to the automation’s prompt for this run only

Examples:

# Find the Signal automation (signal column = yes), then fire it
ag automation list
ag automation trigger <automation-id>

# Steer this one run
ag automation trigger <automation-id> --prompt "Focus only on latency regressions in the last 24h"

# Follow the run it started
ag session events <job-id> --follow

See Signal for enabling Signal and reading the issues a run produces.

Skills

MCP server

API reference

API clients

`ag automation list`

`ag automation trigger`

​ag automation list

​ag automation trigger

`ag automation list`

`ag automation trigger`