Command Explorer › sch: — when things happen › again
sch:again
The action, repeated on the stated pattern.
In the sch: domain
sch:once — One action, once, at the stated time.sch:again — The action, repeated on the stated pattern.sch:remind — At the time, you are nudged — the agent does no work.sch:watch — When the event occurs, the action runs — no clock.sch:due — A deadline: a boundary, not a firing.sch:snooze — Defer an item to a later time, unchanged otherwise.sch:pause — Suspend an item until resumed — never deleted.sch:stop — Cancel an item outright: it will not fire again.What it does
The designated action is performed repeatedly, on the pattern your message states.
The registry's own words: Recurring: the agent performs the designated action repeatedly, on the pattern this message states in prose (daily, every Monday, each hour — the pattern rides in the prose; the token fixes the type). The agent records the recurring item and confirms the pattern it recorded.
Fire it — usage examples
“Every Monday at 8, pull the week's numbers and summarize them.
sch:again”→ the recurring item is recorded, and the confirmation restates the pattern as recorded — that restating is how a fuzzy pattern (“every other day-ish”) gets caught before it runs.
“Check the job board every morning at 7 and flag anything in budget — until the end of the month.
sch:ag”→ a recurring item with its end condition recorded; the confirmation restates the pattern and the stop date.
Said aloud: “Lingo, schedule again — the Monday numbers, at eight.”
→ the recurring item, recorded and read back.
Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “schedule again”. Dictated directives fire deliberately, never by accident.
What the agent actually does
A recurring entry: action, pattern, type. End conditions ride in the prose (“until June”, “three times”) and are recorded with the item when stated. The first firing is the pattern's next occurrence, not an instant one.
The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-sch-again ↗.
When the host can't
No scheduling capability on this host: say so plainly and state the recurring item that would have been set, as for sch:once. If the host supports one-shot items but not recurrence, say so and offer the nearest one-shot, disclosed as such — never record a single firing as a recurrence.
Conformance — “done when”
The recurring item is recorded with its pattern restated in the confirmation — or the gap or ambiguity is reported with nothing recorded.
Persistence class: content-write. Execution report in the reply: required. A user can test any of this by hand — fire the directive, then check the result against the store, the schedule, or the reply itself.