Schedule one prompt for later
A scheduled check-in delivers one future instruction to one exact existing session. It is a continuity primitive for known work—not a general reminder service and not a replacement for Routines.
Schedule a continuation, not a hidden reminder
Section titled “Schedule a continuation, not a hidden reminder”Use a check-in to inspect a long-running operation later, wake a coordinator after child work, retry a bounded external wait, or return to a known state without opening a new thread.
The destination is the durable session identity, not merely the newest conversation in the same project.
What an exact-session wake adds
Section titled “What an exact-session wake adds”- Exact continuity. The future prompt lands in the session that already owns the context.
- Less reminder translation. The instruction can name the state to inspect and next action.
- Bounded follow-up. Long waits can be rechecked without launching duplicate work.
Mission: schedule one bounded check-in
Section titled “Mission: schedule one bounded check-in”- Confirm the next action belongs to this exact session.
- Write the success, still-running, failure, and human-blocker branches.
- Choose the future delivery time or completion condition.
- Verify the pending instruction appears on the owning session.
- Stop rescheduling when the work completes, transfers, fails, or needs a person.
Keep the wake bounded
Section titled “Keep the wake bounded”Use a Routine for repeatable project work with run history. A scheduled prompt should not become an invisible infinite poller. If the exact session cannot be resolved, fail closed rather than delivering into a similar or newer conversation. The installed build is authoritative for which user-facing scheduling controls are available.
Related references
Section titled “Related references”Put this to work: Compare a one-off check-in with a repeatable Routine before scheduling.