Troubleshooting¶
| Symptom | Fix |
|---|---|
| "claude.exe not found" screen on startup | Install Claude Code, or set the path in ⚙ Settings |
| Generated files don't open in an editor | Set your editor path in ⚙ Settings (auto-detects Notepad++, VS Code, falls back to Notepad) |
| Window closes instantly with an error | Check %TEMP%\claudectl_crash.log — the crash handler writes the traceback there |
| Projects missing from the list | The project folder was moved/deleted, or the path can't be decoded — see Session encoding |
| Wrong account / want a second account | Set Config dir in ⚙ Settings to that account's CLAUDE_CONFIG_DIR (e.g. ~/.claude-work). Drives both session browsing and the env handed to claude at launch. Blank = default ~/.claude. Restart claudectl to apply. See Multiple accounts for running two at once. |
| Settings location | ~/.claude/claudectl.json — safe to edit by hand or delete to reset (always read from ~/.claude, independent of Config dir) |
| Usage stats look stale | Delete ~/.claude/claudectl-stats-cache.json — it rebuilds on the next scan |
| GUI window tears or flickers | Set stage: lite in Settings first; if it persists, stage: off, or launch with QTWEBENGINE_CHROMIUM_FLAGS=--disable-gpu-compositing |
| OmniRoute free execution not working | See the Plan → Execute troubleshooting section |
Still stuck? Open an issue — and check the FAQ first.