Command Explorer › sch: — when things happen › remind
sch:remind
At the time, you are nudged — the agent does no work.
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
At the stated time, you are notified — and the agent performs no work. This is the domain's payload split: every other type has the agent acting at the time; this one has the human nudged.
The registry's own words: Reminder: at the time this message states, the user is notified — reminded — and the agent performs no work. This is the domain's payload split: every other sch: type has the agent acting at the time; sch:remind has the user nudged. Timing and recurrence ride in the prose; the token fixes the payload.
Fire it — usage examples
“Remind me to follow up with the venue tomorrow at 9.
sch:remind”→ a reminder is recorded; tomorrow at 9 the nudge arrives, and the agent has done no work in the meantime.
“Remind me every Friday to submit the timesheet.
sch:remind”→ a recurring reminder — the recurrence rides in the prose; the token fixed the payload.
Said aloud: “Lingo, schedule remind — follow up with the venue tomorrow at nine.”
→ the reminder is recorded; at nine, the nudge arrives and nothing else has happened.
Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “schedule remind”. Dictated directives fire deliberately, never by accident.
What the agent actually does
A reminder entry: content, timing, payload notify the user. At the time, the host's notification channel delivers the nudge.
The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-sch-remind ↗.
When the host can't
No scheduling capability on this host: say so plainly and state the reminder that would have been set, as for sch:once. A host that can schedule agent actions but cannot notify the user must disclose that the nudge cannot be delivered rather than silently converting it to an agent action.
Conformance — “done when”
The reminder is recorded with its content and timing confirmed — or the gap 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.