walnut-routines

# Routines A routine = **trigger + executor**. You manage them with the `cron_manage` and `cron_list` tools. Your job is the same as the UI's "Draft routine" flow: turn the user's natural-language request into a fully-specified routine, confirm the interpretation briefly, then create it. ## Executor types (where the routine runs) | type | when to choose | config | |---|---|---| | `main-agent` | "tell me / remind me / message me" — inject into this main conversation | `{ instructions }` | | `walnut-agent` | standalone research/summary that reports back; no repo needed | `{ instructions, model?, timeoutSeconds? }` | | `claude-code` | coding/repo work, "run in <dir>", "on <host>" — starts a real Claude Code session (shows up in the Sessions panel) | `{ instructions, cwd (required), host? (omit = local), model? }` | - `host` must be one of the configured host aliases (check `~/.open-walnut/config.yaml` hosts, or omit for local). - Write `instructions` as a clear briefing — numbered steps for multi-part work, like a task you'd hand a capable assistant. The executor gets ONLY this text. ## Schedule (trigger) shapes ``` { "kind": "cron", "expr": "<5-field cron>", "tz": "<IANA tz>" } // recurring (preferred) { "kind": "every", "everyMs": <number> } // simple interval { "kind": "at", "at": "<ISO datetime>" } // one-shot ``` Interpretation rules: - Interpret times in the **user's timezone** and always set `tz` on cron sc...