fix: increase Claude auth probe timeout to 10s

[Heinz-G]

Summary

• Adds AUTH_PROBE_TIMEOUT_MS = 10_000 to providerSnapshot.ts
• Uses it for the claude auth status probe in ClaudeProvider.ts instead of DEFAULT_TIMEOUT_MS (4s)

Why

claude auth status involves disk/account lookups and can exceed 4s on Windows due to Node.js cold-start overhead. This causes a spurious "Could not verify Claude authentication status. Timed out while running command." warning in the provider panel — even when the CLI is correctly installed and authenticated.

The --version probe is fast and keeps its 4s timeout unchanged. Only the auth check gets the higher limit.

Before / After

Before: Provider shows yellow "Needs attention – Could not verify Claude authentication status. Timed out while running command." on Windows on first load.

After: Auth check has 10s to complete, resolving the false positive on Windows.

Test plan

• Launch T3 Code on Windows with claude on PATH and authenticated
• Confirm provider status shows green "Ready" instead of the timeout warning
• Confirm --version probe speed is unaffected (still uses 4s timeout)

🤖 Generated with Claude Code

---

Note

Low Risk
Low risk: only adjusts the timeout used for the claude auth status probe to reduce false timeout warnings, without changing auth parsing or other probes.

Overview
Increases the timeout for the Claude provider’s claude auth status check by introducing AUTH_PROBE_TIMEOUT_MS (10s) and using it instead of DEFAULT_TIMEOUT_MS.

This makes the auth probe more tolerant of slow first-run startup (notably on Windows) while leaving other CLI probes (e.g. --version) on the existing 4s timeout.

^{Reviewed by Cursor Bugbot for commit 8179582. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Increase Claude auth probe timeout to 10s

Auth checks against Claude can be slow, causing false failures with the previous 4s timeout. Introduces a new AUTH_PROBE_TIMEOUT_MS constant (10,000ms) in providerSnapshot.ts and applies it in ClaudeProvider.ts instead of the general DEFAULT_TIMEOUT_MS.

^{Macroscope summarized 8179582.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: b69ce09a-d321-4444-803e-6d36cb870ca9

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[macroscopeapp]

Approvability

Verdict: Approved

This is a simple timeout increase for auth status checks from 4s to 10s to handle slow disk/network operations on first run. No authentication logic is changed, only the allowed duration for the operation to complete. Low-risk configuration tweak.

^{You can customize Macroscope's approvability policy. Learn more.}

[samuelpatro]

Not sure if this is fixed i think i have similar issue to this PR fix:

Needs attention - Could not verify Claude authentication status. Timed out while running command.