[BUG] Settings not applied on startup

[fuzz-goe]

Describe the bug
Settings saved to ~/.claude/claude-devtools-config.json are not applied when the app starts. The app always launches with default values, ignoring the persisted config.

To Reproduce

1. Launch the app
2. Change any setting (e.g. Auto-expand AI responses, notification triggers)
3. Quit the app
4. Confirm ~/.claude/claude-devtools-config.json contains the updated values
5. Launch the app again
6. Observe that settings are reset to defaults

Expected behavior
Settings saved to ~/.claude/claude-devtools-config.json are loaded and applied on startup.

Screenshots
N/A

Desktop:

• OS: Windows 11 (no WSL)
• Version: v0.4.9 (broken), v0.4.8 (working)

Additional context

⚠️ Note: the following is speculation from Claude (AI), not verified by the reporter.

PR #111 (perf: convert synchronous file reads to async in main process) introduced in v0.4.9 is a likely candidate. Converting the config read from sync to async may have introduced a race condition where the renderer initializes with default values before the async read completes and the config is sent over IPC.

[nevdelap]

Same when running with...

docker build -t claude-devtools .
docker run -d --name claude-devtools -p 3456:3456 -v ~/.claude:/data/.claude claude-devtools

{
  "notifications": {
    "enabled": true,
    "soundEnabled": true,
    "ignoredRegex": [
      "The user doesn't want to proceed with this tool use\\."
    ],
    "ignoredRepositories": [],
    "snoozedUntil": null,
    "snoozeMinutes": 30,
    "includeSubagentErrors": true,
    "triggers": [
      {
        "id": "builtin-bash-command",
        "name": ".env File Access Alert",
        "enabled": false,
        "contentType": "tool_use",
        "mode": "content_match",
        "matchPattern": "/.env",
        "isBuiltin": true,
        "color": "red"
      },
      {
        "id": "builtin-tool-result-error",
        "name": "Tool Result Error",
        "enabled": false,
        "contentType": "tool_result",
        "mode": "error_status",
        "requireError": true,
        "ignorePatterns": [
          "The user doesn't want to proceed with this tool use\\.",
          "\\[Request interrupted by user for tool use\\]"
        ],
        "isBuiltin": true,
        "color": "orange"
      },
      {
        "id": "builtin-high-token-usage",
        "name": "High Token Usage",
        "enabled": false,
        "contentType": "tool_result",
        "mode": "token_threshold",
        "tokenThreshold": 8000,
        "tokenType": "total",
        "color": "yellow",
        "isBuiltin": true
      }
    ]
  },
  "general": {
    "launchAtLogin": false,
    "showDockIcon": true,
    "theme": "light",  <<<<<<<<<<<<<<<<<<<<<<<<<<<<<
    "defaultTab": "dashboard",
    "claudeRootPath": null,
    "autoExpandAIGroups": false,
    "useNativeTitleBar": false
  },
  "display": {
    "showTimestamps": true,
    "compactMode": false,
    "syntaxHighlighting": true
  },
  "sessions": {
    "pinnedSessions": {},
    "hiddenSessions": {}
  },
  "ssh": {
    "lastConnection": null,
    "autoReconnect": false,
    "profiles": [],
    "lastActiveContextId": "local"
  },
  "httpServer": {
    "enabled": false,
    "port": 3456
  }
}

Runs in dark theme.

[nevdelap]

PR #161 fixes it in Docker and the AppImage running on Linux. @fuzz-goe, maybe you can test the App in Windows? The Windows and Linux release files in my fork are here.

Docker tested in Linux with...

docker run --rm --name claude-devtools -p 3456:3456 -v /home/nevd/.claude:/data/.claude claude-devtools

App tested in Linux with...

> curl -L https://github.com/nevdelap/claude-devtools/releases/download/v0.4.10/claude-devtools-0.4.10.AppImage -o /tmp/claude-devtools.AppImage
> nix-shell -p appimage-run --run "appimage-run /tmp/claude-devtools.AppImage"

Both read and save the config and retain the config changes between restarts, tested by switching between light and dark modes.