Problem
Issue #339 (PR #343) shipped three scheduling primitives — wake --delay, goal, and monitor — and surfaced them in the agent preamble so the agent can teach itself. There's still no user-facing docs page that walks a human through the same primitives.
Why it matters
The agent preamble is reachable only from inside a running session. New users installing Controller don't see these primitives until they start an agent. A docs/content/docs/scheduled-tasks.mdx page (modeled on worktrees.mdx) would make the feature discoverable from the docs sidebar and double as a reference once an agent is mid-loop.
Scope
Add docs/content/docs/scheduled-tasks.mdx covering:
controller sessions wake <self> --message "..." --delay 30s — deferred follow-upcontroller sessions goal set <self> --condition "..." --max-turns N [--expires-at <iso>] — completion-driven loopcontroller sessions monitor start <self> --command <shell> [--timeout-ms N] [--persistent] — long-running background watcher- The CI / status-check workflow as the worked example (already in the agent preamble; copy over the prose)
- A short note on each primitive's persistence file (
/Users/germanescobar/Library/Application Support/Controller/wakes.json, .../goals.json, .../monitors.json) so users can debug
Register the page in docs/content/docs/sidebar.mdx next to worktrees.
Out of scope
- The agent preamble itself — leave that as the agent's self-teach surface
- Implementation work; this is docs-only
Acceptance
docs/content/docs/scheduled-tasks.mdx exists and renders in the sidebar- Page covers all three primitives with at least one worked example
- Page references the underlying state files so users know where to look when debugging
Related
Problem
Issue #339 (PR #343) shipped three scheduling primitives —
wake --delay,goal, andmonitor— and surfaced them in the agent preamble so the agent can teach itself. There's still no user-facing docs page that walks a human through the same primitives.Why it matters
The agent preamble is reachable only from inside a running session. New users installing Controller don't see these primitives until they start an agent. A
docs/content/docs/scheduled-tasks.mdxpage (modeled onworktrees.mdx) would make the feature discoverable from the docs sidebar and double as a reference once an agent is mid-loop.Scope
Add
docs/content/docs/scheduled-tasks.mdxcovering:controller sessions wake <self> --message "..." --delay 30s— deferred follow-upcontroller sessions goal set <self> --condition "..." --max-turns N [--expires-at <iso>]— completion-driven loopcontroller sessions monitor start <self> --command <shell> [--timeout-ms N] [--persistent]— long-running background watcher/Users/germanescobar/Library/Application Support/Controller/wakes.json,.../goals.json,.../monitors.json) so users can debugRegister the page in
docs/content/docs/sidebar.mdxnext toworktrees.Out of scope
Acceptance
docs/content/docs/scheduled-tasks.mdxexists and renders in the sidebarRelated
server/lib/agent-preamble.ts— the in-agent version of the same content