“Detect Tailscale” fails when Tailscale already running (App Store build); if Tailscale quit then Detect launches it but “Checking” stays disabled/stuck

[danielraffel]

On macOS with the App Store build of Tailscale already running and connected, tapping Detect Tailscale in CM returns an error. If I quit Tailscale and tap Detect again, CM launches Tailscale and it connects successfully, but CM’s Checking button remains stuck in a disabled state indefinitely. Mobile app works.

CodexMonitor v0.7.49
Tailscale 1.94.1
macOS 26.2

Invalid tailscale status JSON: expected value at line 1 column 1 (stout: The Tailscale GUI failed to start: The operation couldn't be
completed. (Tailscale. CLIError error 3.))

[Dimillian]

@codex fix this

[chatgpt-codex-connector]

Summary

• Fixed macOS Tailscale CLI discovery to use the correct App Store binary path (/Applications/Tailscale.app/Contents/MacOS/tailscale) and updated the related missing-binary message accordingly, so “Detect Tailscale” can resolve the right executable when Tailscale is already running. src-tauri/src/tailscale/mod.rsL50-L60 src-tauri/src/tailscale/mod.rsL82-L90
• Added a shared 12-second timeout for Tailscale command execution and applied it to both tailscale version and tailscale status --json, returning explicit timeout errors instead of letting the request hang indefinitely. This prevents the UI from being stuck in “Checking...”. src-tauri/src/tailscale/mod.rsL28-L29 src-tauri/src/tailscale/mod.rsL93-L130 src-tauri/src/tailscale/mod.rsL357-L372
• Updated the macOS unit test expectation to assert the corrected lowercase Tailscale CLI path. src-tauri/src/tailscale/mod.rsL437-L449
• Committed on the current branch (0aeaf93) and created a follow-up PR via the make_pr tool.

Testing

• ✅ npm run typecheck
• ⚠️ cd src-tauri && cargo check (fails in this container due to missing system glib-2.0/pkg-config setup, not due to this code path)

View task →