Not every security problem announces itself. A monitor-driven agent waits for an event; a scheduled agent goes and looks. Several of Clarion’s templates only exist in the second shape.
Three ways a run starts
Scheduled agents
A schedule carries its own prompt — the instructions for that run — plus a standard five-field cron expression and an IANA timezone (UTC by default, so a platform schedule doesn’t inherit one team’s local time). Schedules are enabled or disabled individually, and deactivating the agent is the master off switch for all of them. Several agent templates ship with a schedule already attached, materialized and pinned to the agent when you create it:
You can add your own schedules to any agent, or edit the ones a template brought.
What a scheduled run can do
A scheduled run is a full agent run, not a cut-down cron job:- It files issues from what it finds, with a per-run cap so a bad night cannot flood the queue.
- It can ask a human for clarification mid-run and resume when someone answers — an overnight sweep does not have to guess or abort.
- It writes verdicts back to the Brain, so tomorrow’s run starts with what today’s decided and stops re-reporting things a human already parked.
- It posts a summary to the workspace’s notification destination, including a clean result, so silence is never ambiguous.
Failure handling
Each schedule stamps its next firing time on every successful claim, and consecutive spawn failures trip a circuit breaker rather than retrying forever. Run history — start, result, and error — is kept per schedule, and a single run’s clarifications are reported together.Ad-hoc runs
Run now fires a schedule immediately, out of band, without touching its cadence. Multiple in-flight runs are safe: each gets its own run record. This is the usual way to test a schedule’s prompt before trusting it overnight, and Members can do it even though authoring schedules is Admin-only. Retriggering an issue re-runs triage on an existing issue — after new evidence lands, after a skill was corrected, or when the first pass was thin. Chat is the fully ad-hoc path: the same tools and skills, driven by a person, with no schedule and no monitor involved. See AI chat.Our agents
Which templates are schedule-driven.
Monitors
The event sources behind monitor-driven runs.
The Brain
Where a sweep’s verdicts are remembered.
AI chat
Drive the same tools yourself.