← ClaudeAtlas

daemon-debuglisted

Diagnose autostart, proxy, and process issues — why things aren't starting, connecting, or recovering
standardbeagle/agnt · ★ 22 · Code & Development · score 79
Install: claude install-skill standardbeagle/agnt
# Daemon Debugging Use this skill when diagnosing why processes aren't starting, proxies are missing, ports are occupied, or the autostart flow isn't working. ## Diagnostic Checklist Work through these in order. Each step either finds the problem or rules out a category. ### 1. Verify Daemon State ```bash # Is the daemon running? agnt daemon status # What processes does the daemon know about? printf 'PROC LIST\n;;\n' | socat - UNIX-CONNECT:/tmp/devtool-mcp-$(id -u).sock # What proxies exist? printf 'PROXY LIST\n;;\n' | socat - UNIX-CONNECT:/tmp/devtool-mcp-$(id -u).sock ``` Decode base64 JSON responses. Check: - Are expected processes listed? - What state are they in? (running / failed / etc.) - Do running processes have `urls` populated? - Are any warnings present (rogue processes)? ### 2. Check Config ```bash # Read the project config cat /path/to/project/.agnt.kdl ``` For each proxy with `script` set: - Does the linked script exist in `scripts {}`? - Does the script have `url-matchers`? Do they match actual output format? - Does the proxy have `fallback-port`? (safety net if URL detection fails) ### 3. Verify URL Detection URL detection is the #1 failure point for script-linked proxies. **Common URL matcher mismatches:** | Dev server | Actual output | Correct matcher | |-----------|--------------|----------------| | dotnet | `Now listening on: http://localhost:6111` | `"Now listening on: {url}"` | | Vite | `Local: http://localhost:5173/` | `"Local:\\s+{url}"