wake

Gate: ungated · no kind, zero authority

Schedule the running conversation's own re-invocation: after seconds, this same conversation comes back with note as the prompt. Use it to wait and then continue — poll something, or re-check after a delay. It is the in-session cousin of a reminder, which fires a detached notification instead.

Input

Field	Type	Required	Notes
seconds	number	yes	Delay before resuming. Clamped to 1 s … 1 h.
note	string	yes	The prompt to resume with, e.g. "re-check the deploy status".

Output

The delay that was actually accepted, after clamping:

{ "wakeInSeconds": 300 }

From JavaScript

wrapper (idiomatic)

nocturn.wake(300, "re-check the deploy status");

nocturn.call

nocturn.call("wake", { seconds: 300, note: "re-check the deploy status" });

Notes

Bounded, not gated. wake reaches nothing external — it only schedules a continuation — so it carries no authority and never calls the gate. Any tool called in the resumed turn is gated normally. The risk it does carry is a runaway self-waking loop, so it is bounded instead: the delay is clamped and the number of pending wakes is capped. A wake resumes the exact conversation that scheduled it; delete that chat and its pending wakes go with it. Pending wakes are persisted (wakes.json in the workspace), so one survives a restart the way a reminder does — including one that came due while the daemon was down, which resumes as soon as it is back.