# Logs and diagnostics Source: https://docs.ideharmony.com/troubleshooting/logs-and-diagnostics ## Start with doctor `harmony doctor` is the first diagnostic for almost every problem. It reports what Harmony resolved rather than what it hopes is true. ```powershell harmony doctor ``` For a machine-readable form suitable for attaching to a report: ```powershell harmony doctor --json ``` **Expected evidence:** daemon reachability, resolved data directory, detected providers with their resolved paths and versions, and runtime prerequisites. ## What a diagnostic contains Diagnostic output is about your machine, so assume it includes: - Absolute filesystem paths, including your user directory - Repository and workspace names - Provider names and detected versions - Environment details relevant to launching processes > [!WARNING] > Review diagnostics before sharing them. Paths and workspace names commonly > reveal client names, unreleased project names, and your username. Redact > before posting into a public issue tracker or chat. ## Support bundles The application can assemble a support bundle for a problem, including recent events and state relevant to the failure. Bundles are intended for sharing with maintainers, which means the same rule applies more strongly: read it first. > [!SECURITY] > Never attach a support bundle, screenshot, or terminal capture that contains > API keys, tokens, or credentials. Harmony does not hold your provider > credentials, but your own shell environment might, and captures include what > is on screen. ## Reading session state Two commands answer most "is it actually doing anything" questions: ```powershell harmony sessions list harmony tasks list ``` > [!IMPORTANT] > A process being alive is not evidence that work is progressing. An agent can > hold a session open indefinitely without advancing a task. Trust the task > state over the presence of a running process. ## Escalating a problem When reporting, include: 1. The exact Harmony version (`harmony version`). 2. What you did, what you expected, and what happened. 3. Redacted `harmony doctor --json` output. 4. Whether the problem reproduces on a fresh workspace. Point 4 matters more than it looks: a problem that only appears in one workspace is usually state, and a problem that appears everywhere is usually the build. ## Related - [Daemon problems](/docs/troubleshooting/daemon) - [Provider problems](/docs/troubleshooting/providers) - [Privacy](/docs/security/privacy)