Skip to content
AGH RuntimeAutomation

Automation

Run AGH agents on schedules, in response to runtime events, or from signed external HTTP requests.

Audience
Operators running durable agent work
Focus
Automation guidance shaped for scanability, day-two clarity, and operator context.

Automation is the unattended-run surface around three primitives: schedules that fire on a clock, triggers that react to runtime events, and webhooks that accept signed HTTP from outside the daemon. All three resolve to the same dispatcher and produce the same audit trail as interactive sessions.

Hand-drawn Automation poster showing AGH jobs, triggers, webhooks, a shared dispatcher, and run history with the octopus mascot.

In this section

Tool and CLI parity

Automation lifecycle is agent-manageable. The agh__automation toolset and the matching agh automation CLI both reach the same validators and writers:

SurfaceRead toolsMutation toolsCLI parity
Jobsagh__automation_jobs_list, agh__automation_jobs_get, agh__automation_jobs_historyagh__automation_jobs_create, agh__automation_jobs_update, agh__automation_jobs_delete, agh__automation_jobs_trigger, agh__automation_jobs_enable, agh__automation_jobs_disableagh automation jobs ...
Triggersagh__automation_triggers_list, agh__automation_triggers_get, agh__automation_triggers_historyagh__automation_triggers_create, agh__automation_triggers_update, agh__automation_triggers_delete, agh__automation_triggers_enable, agh__automation_triggers_disableagh automation triggers ...
Runsagh__automation_runs_list, agh__automation_runs_getagh automation runs ...

Mutations require approval, run through the same domain validators as CLI/HTTP, and reject raw webhook secrets with deterministic codes including AUTOMATION_SCOPE_FORBIDDEN, AUTOMATION_SECRET_INPUT_FORBIDDEN, AUTOMATION_VALIDATION_FAILED, and AUTOMATION_APPROVAL_REQUIRED. Webhook secret material stays write-only on mutation surfaces and is referenced through webhook_secret_ref.

On this page