CommandAGI · commandagi.com/for/triggers

CommandAGI
Open the workbench
Menu
Open the workbenchSign in

Triggers

Agents that wake on their own.

A schedule, a webhook or a platform event wakes an agent with a prompt. The trigger is a file, and every wake is on the record.

Open the workbenchRead the API

From a file to a wake

A trigger is a line in a file.

A thread's triggers are its triggers.tsx; a monitor's are the every of its sources. A create, an edit or a delete writes the file first.

How a trigger wakes an agentA trigger is declared in a file, a thread's triggers.tsx or a monitor's source with its schedule. When a schedule comes due, a webhook arrives or a platform event happens, the platform records an intent in the run's effects stream, then the command with the trigger as its author, then the outcome. The agent wakes with the trigger's prompt in its thread.triggers.tsx ormonitor.tsxcron · webhook ·platform eventDuethe schedule, aPOST, an eventeffects: intentrecorded beforeanything runseffects:commandby: trigger:<label>The agentwakeswith the trigger'spromptHow a trigger wakes an agentA trigger is declared in a file, a thread's triggers.tsx or a monitor's source with its schedule. When a schedule comes due, a webhook arrives or a platform event happens, the platform records an intent in the run's effects stream, then the command with the trigger as its author, then the outcome. The agent wakes with the trigger's prompt in its thread.triggers.tsx or monitor.tsxcron · webhook · platform eventDuethe schedule, a POST, an eventeffects: intentrecorded before anything runseffects: commandby: trigger:<label>The agent wakeswith the trigger's prompt

Read the API

One wake, four lines.

The Grants.gov monitor in CommandAGI's Drive reads every federal funding opportunity once a day. This morning's wake, as its run recorded it. The hlc and salt of each line are left out.

08:54:46.887 event   operator: open
09:59:49.096 event   operator: intent effect=trigger trigger=monitor:capital/grants-gov:source:opportunities due=2026-11-04
09:59:49.918 command trigger:monitor:capital/grants-gov:source:opportunities for=cloud#2
09:59:54.482 event   operator: outcome of=cloud#3 ok
runs/thread-idempotent-thread-user-commandagi-monitor-capital-grants-gov/streams/effects@cloudreal records · production · 2026-11-04
<monitor title="Grants.gov: forecasted and posted federal funding opportunities" class="capital-faucet">
  <source id="opportunities" adapter="grants-gov" params={{}} every="1d" />
  {publish("grants-gov.opportunity")}
</monitor>

Counted in the Drive

12,104 monitors, one way to wake.

CommandAGI's production Drive on 2026-11-04: 12,104 monitor.tsx files and 12,431 monitor thread runs, each with an effects stream (case-studies/triggers/stats.json).

Cron and webhooks. every in seconds, or a webhook with its own secret. A friendly shorthand, or the full condition algebra. Platform events. A thread can wake on an event of your own account: an email or a text that arrives, a calendar change, a Drive change, low credits.

monitors, each waking on its sources' schedules
12,104
monitor thread runs
12,431
effects streams of their wakes
12,430
Monitors by folder in CommandAGI's Drive
The numbers
Monitors by folder in CommandAGI's Drive
FolderMonitors
entities8031
software2082
science488
markets356
narratives232
marketplaces197
ProvenanceFile cloud://home/user-commandagi/ (production)Output case-studies/triggers/stats.jsonTool scripts/sites/case-studies.mjs triggersRan on This computer (dell-gb10-1), reading the production DriveWhen

Put an agent on a schedule.

Ask in a thread, or call create_trigger from any MCP client.

Open the workbenchRead the API