You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Routines: agents that run on a schedule or an event
#2123
In Vstorm AgenticOS an agent doesn't have to wait for someone to type. A routine runs it on its own, in one of two ways:
A schedule fires on the clock: an interval (a minute at the finest) or a five-field cron expression evaluated in UTC.
A trigger fires on an arrival: a new GitHub issue, a new Gmail message (polled once a minute, so there is no webhook to set up), or the catch-all API source for anything that can POST signed JSON.
A weekday-morning schedule, created over the API:
curl -X POST "$BASE/api/v1/agents/$AGENT_ID/triggers" \
-H "Authorization: Bearer $TOKEN" \
-H "X-Organization-Id: $ORG_ID" \
-H "Content-Type: application/json" \
-d '{ "name": "Morning digest", "prompt": "List the open pull requests and mark the ones waiting for review.", "trigger_type": "schedule", "schedule_kind": "cron", "cron_expression": "0 7 * * 1-5" }'
0 7 * * 1-5 is 07:00 UTC on weekdays. The same form is in the console under Routines and in the agent's Availability tab, and any routine can also be fired once with Run now.
For the API source, the sender signs the exact request body with HMAC-SHA256:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
In Vstorm AgenticOS an agent doesn't have to wait for someone to type. A routine runs it on its own, in one of two ways:
A weekday-morning schedule, created over the API:
0 7 * * 1-5is 07:00 UTC on weekdays. The same form is in the console under Routines and in the agent's Availability tab, and any routine can also be fired once with Run now.For the API source, the sender signs the exact request body with HMAC-SHA256:
What happens when a routine fires:
schedulesurface.budget_exceededand waits for the next fire. Nothing retries it every minute.failedand also waits for the next fire.202means accepted, not finished. The answer is in Activity and in the routine's run-log conversation.Limits worth knowing:
Details: Triggers and schedules · Concepts: triggers · Governance
Question: what would you hand to an agent on a schedule first: a morning digest, issue triage, inbox replies, something else?
All reactions