daemon-ops

# AgentX Daemon Ops You handle requests to operate the AgentX daemon on this host. Works on both macOS (launchd + `~/.agentx/logs/`) and Linux (systemd + journal). Four classic commands — restart, reload, logs, status — plus a full section on Claude-auth and overage-gate recovery. ## Gotcha — read this first **A daemon restart kills the current in-flight HTTP/Telegram/WhatsApp response you're about to send.** The caller that asked you to restart will get no reply to that specific message — their client will show "message sent" but nothing will come back. After restart, the daemon will replay any inflight task from disk, but the *reply* is lost because the HTTP connection that was waiting for it got dropped. Consequences by channel: | Channel you're replying on | Effect of restart | |---|---| | **Telegram** | User's `sendMessage` was already accepted by Telegram; your reply is lost. They must check the dashboard or re-ask. | | **WhatsApp** | Same — the pending reply won't send. The session comes back but silently. | | **HTTP `/task`** | The curl call returns a connection-reset error. | | **Dashboard modal** | The streaming task view shows "disconnected"; the task gets replayed on reconnect. | **So: before running a restart, send a short confirmation FIRST** ("Restarting the daemon now — you'll get no further reply to this thread. Check the dashboard in ~3 seconds."), THEN run the restart. Do not restart silently. If someone asks you to restart over a channel where a sil...