daemon

1# /daemon -- Continuous Autonomous Operation
2 
3Architecture, daemon.json field reference, and rationale: docs/DAEMON.md.
4 
5## Orientation
6 
7**Use when:** running campaigns overnight or unattended -- chains sessions automatically until a ceiling or budget is hit.
8**Don't use when:** a single autonomous session is enough (use /archon); you want manual control between cycles (use /loop).
9 
10## Default execution path (READ FIRST)
11 
12**`/daemon start` does NOT call `RemoteTrigger` by default.** The local runner is the default. Only pass `--remote` to use Anthropic's routine system, and only after explicit user confirmation.
13 
14**Why:** `RemoteTrigger` counts against the account-wide **15 routine runs / 24h** cap. A single overnight run can exhaust the quota and pause every other routine on the account (including unrelated ones). See [docs/ROUTINE-QUOTA.md](../../docs/ROUTINE-QUOTA.md).
15 
16### Default flow — `/daemon start` (no `--remote` flag)
17 
181. Do Steps 1, 2, and 4 below (validate, check existing, write `daemon.json`).
192. **Skip Step 3.** Leave `chainTriggerId` and `watchdogTriggerId` as `null` in the state file. Keep the confirmation focused on the state path, campaign, finite budget, session ceiling, and local start/stop instructions.
203. Instead of Step 5's trigger-confirmation, output the local-runner instructions (full text: docs/DAEMON.md#local-runner-default): the state file path, campaign, and budget, then:
21   ```
22   To start the tick loop, run in a separate terminal:
23…