cc-viewer 1.9.11 → 1.9.13

package/README.md

@@ -154,6 +154,14 @@ Once configured, just use the `claude` command as usual. Visit `http://localhost
 
 ## Features
 
+### Scheduled tasks
+
+Open **Scheduled tasks** from the (+) menu (chat input bar or terminal toolbar) to run a prompt on a schedule: a preset (hourly / daily / weekdays / weekly), a custom 5-field cron, or a one-off time. Each task either **injects the prompt into the current live session** (queued while busy, exactly as if you typed it) or **spawns a fresh isolated headless session** (SDK mode only) with a clean context.
+
+Task definitions and scheduling state live in `preferences.json` (the `scheduledTasks` key) and run history (last 20 per task) in `scheduled-task-runs.json` under the cc-viewer data dir, scheduled in the server's local timezone with a small per-task jitter to avoid on-the-hour stampedes. The server ticks every 10s and claims each fire under a cross-process file lock, so parallel instances / Electron tabs never double-fire. After a restart or a sleep it catches up the single most recent missed run within 7 days (earlier misses are recorded as `missed`, never back-filled one by one).
+
+You can **Run now**, pause/resume, delete, and see the last 20 runs (an isolated-session run can jump straight to its session). Fires are silent (the message just appears in the conversation); completions and failures surface as a toast. Note: a task only fires while `ccv` is running, and the scheduler does not run in a workspace-management (unbound) process.
+
 ### Programming mode
 
 After launching with ccv you'll see: