fix(clients): reconnect after credentials fail during remote server updates

[t3dotgg]

Remote server updates on macOS can briefly reject an environment credential after the new server starts. The connection supervisor then blocks, and the update recovery loop never retries it.

Retry authentication failures once per second while an update is resuming. Permission and configuration failures remain blocked.

Tests: 55 focused client runtime, authorization, and connection supervisor tests pass.

Built with GPT-5.6 Sol using Codex.

---

Note

Medium Risk
Touches reconnect retry during server updates, including authentication-blocked states. The extra retries are limited to the update-resume window and exclude permission/configuration failures.

Overview
During a remote server update restart, reconnect nudges now also fire when the supervisor is blocked on authentication, not only while it is in backoff.

A newly restarted server can reject the first environment credential and leave the client stuck. nudgeReconnectDuringUpdateRestart now retries those auth blocks on the same ~1s cadence used for backoff. Permission and configuration failures stay blocked. A unit test covers that only authentication blocks are retried.

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

Note

Fix nudgeReconnectDuringUpdateRestart to retry on authentication blocks

• Expands nudgeReconnectDuringUpdateRestart in server.ts to schedule paced retries for states blocked by authentication errors during remote server update restarts.
• Broadens the filter from only phase === "backoff" to also include phase === "blocked" when lastFailure?.reason === "authentication".
• Behavioral Change: permission and configuration failures are explicitly excluded from retries and will no longer trigger reconnect nudges.

^{Macroscope summarized 208a63d.}

[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 Plus

Run ID: 082bf040-dfa0-498a-b737-f02b7d31c00b

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

---

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.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.4 KiB	13.4 KiB	−5 B (−0.0%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	0 B (0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.6 KiB	6.5 KiB	−5 B (−0.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.0 KiB	55.0 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	16	16	0 (0.0%)	21	✅
Claude	Total thread wire	13.4 KiB	13.4 KiB	−1 B (−0.0%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−12 B (−0.2%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.6 KiB	+11 B (+0.2%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	55.8 KiB	55.8 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	16	16	0 (0.0%)	21	✅

Baseline: 30be311 · PR result: 208a63d · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[macroscopeapp]

Approvability

Verdict: Skipped

Macroscope did not run approvability analysis for this PR. Macroscope could not determine whether this PR modifies its approvability configuration, so the PR was not approved automatically. A PR that may change the rules that govern approval is never approved automatically.