# Daemon problems Source: https://docs.ideharmony.com/troubleshooting/daemon The daemon is the process that owns your sessions, tasks, artifacts, and messages. It runs separately from the desktop window, which is why closing the window does not end your work — and why daemon problems look like everything being broken at once. ## Panes open but stay blank **Symptom:** the desktop opens, panes appear, but nothing renders in them. **Likely causes** 1. The daemon is not running. 2. The desktop connected to a different daemon instance than expected. **Safe diagnostic** ```powershell harmony doctor ``` **Expected evidence:** a daemon section reporting a reachable socket or pipe. **Repair:** close the desktop fully and relaunch: ```powershell harmony desktop ``` **When not to retry:** do not delete the data directory to force a fresh start before you have read what `harmony doctor` reports. That directory holds your durable sessions and tasks. --- ## The CLI cannot reach the daemon **Symptom:** `harmony tasks list` or similar reports a transport or connection error. **Likely causes** 1. No daemon is running yet. 2. Instance isolation — the CLI and the app resolved different data suffixes. **Background:** Harmony namespaces its entire runtime (data directory, socket, pipes) by a data-suffix environment variable. Development builds use a different suffix from packaged builds, which is how both can run side by side. A CLI started with a different suffix talks to a different daemon. **Safe diagnostic** ```powershell harmony doctor --json ``` **Expected evidence:** the resolved data directory and socket path. Compare it to what the running application is using. **Repair:** launch the desktop once to start the daemon, then retry. If you have both a development and a packaged build installed, use the one matching the suffix you intend. --- ## Sessions did not come back after a restart **Symptom:** you reopen Harmony and previous terminals or agent conversations are missing. **Likely causes** 1. The session passed its retention window. 2. The session was explicitly stopped rather than detached. 3. A crash left restore state that has not been applied. **Expected evidence:** a crash-restore banner on launch when restorable state exists. **Repair:** if a restore banner appears, accept it. Otherwise list what the daemon still holds: ```powershell harmony sessions list ``` **When not to retry:** a stopped session is gone. Detaching and stopping are different actions — `/detach` keeps a session alive, `/stop` ends the turn, and quitting a session ends it. --- ## The daemon is using more resources than expected **Symptom:** sustained CPU or memory use with no active agents. **Safe diagnostic:** check what the daemon still considers live: ```powershell harmony sessions list harmony tasks list ``` **Repair:** stop sessions you no longer need. A pane that looks closed in the UI may still have a live process behind it. > [!NOTE] > A process being alive is not the same as work being in progress. An agent can > hold a session open while doing nothing. Check the task state rather than > inferring from process activity. ## Related - [Session survival](/docs/concepts/session-survival) - [Logs and diagnostics](/docs/troubleshooting/logs-and-diagnostics) - [Architecture](/docs/concepts/architecture)