Skip to content

fix(web): server updates no longer look like warnings - #4992

Merged
t3dotgg merged 2 commits into
mainfrom
t3code/redesign-update-connection-states
Jul 30, 2026
Merged

fix(web): server updates no longer look like warnings#4992
t3dotgg merged 2 commits into
mainfrom
t3code/redesign-update-connection-states

Conversation

@t3dotgg

@t3dotgg t3dotgg commented Jul 30, 2026

Copy link
Copy Markdown
Member

Updating a server showed an amber warning banner with a triangle icon and a green/blue stepper, which made a routine "one moment please" delay feel like something was wrong. Worse, refreshing mid-update stacked two alarming banners: "Client and server versions differ" (with a dead Update button) on top of "Failed to connect. Reconnecting...".

The update banner is now calm and monochrome. Done steps recede to gray, the active step is the only bright element and pulses with the existing duty-cycled animation, and the redundant status sentence is gone. Failures still get full error treatment.

Reconnecting to a version-skewed server (the refresh case, or the reconnect blip during resume) now collapses both banners into a single quiet "Reconnecting - it may be finishing an update" line. The version-mismatch banner with its Update action only returns if the server comes back still on the old version.

Written by Claude Fable 5 via Claude Code.

🤖 Generated with Claude Code


Note

Low Risk
UI-only changes to composer banners and update progress presentation; no auth, data, or server logic changes.

Overview
In-progress server updates and version-skew reconnects now use calm default composer banners (pulsing dot) instead of warning triangles and amber styling, so routine waits don’t read as errors.

Banner stacking is reduced: when reconnecting during version skew with no failed update, unavailable and version-mismatch banners merge into one quiet “Connecting/Reconnecting… it may be finishing an update” line; the version banner with Update only returns if the server is still skewed after reconnect. During an active update, transient reconnect blips hide the unavailable banner unless the connection is in a hard error phase.

ServerUpdateProgress is a monochrome step rail—muted checks for done steps, pulsing dot on the active step with labels like “Resuming”, no per-stage status line except on failure; serverLabel is removed from the component and all call sites. ComposerBannerStackItem adds a default variant for these cases.

Reviewed by Cursor Bugbot for commit d11e4eb. Bugbot is set up for automated code reviews on this repo. Configure here.

Note

Fix server update banners to use neutral styling instead of warning appearance

  • The server update progress rail in ServerUpdateAction.tsx is now monochrome: completed steps show a faint check, the active step pulses, and no status sentence is shown while running (only errors surface an alert).
  • Transient 'environment unavailable' warnings are suppressed in ChatView.tsx when a server update is running and the environment is reconnecting.
  • Version-skew reconnects without an active update now show a single calm 'Connecting/Reconnecting' banner (variant: 'default') instead of an error/warning banner.
  • ServerUpdateProgress no longer accepts or displays a serverLabel prop; call sites in ConnectionsSettings.tsx are updated accordingly.

Macroscope summarized d11e4eb.

The in-progress server update banner used amber warning chrome, a
triangle icon, and green/blue stage colors, reading as an actionable
alert when it is really a "one moment" wait. The step rail is now
monochrome: done steps recede to gray, the active step is the only
bright element and pulses with the duty-cycled status-pulse animation.

Refreshing mid-update also stacked "Client and server versions differ"
on "Failed to connect. Reconnecting..." because the in-memory update
state was wiped. Reconnecting to a version-skewed server now collapses
both into one calm "Reconnecting - it may be finishing an update" line,
and the reconnect banner stays suppressed for the whole running update
rather than only the resuming stage.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 30, 2026

Copy link
Copy Markdown

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: b97e33b4-fe41-41d4-a2a6-ef970ade2a45

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

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:L 100-499 changed lines (additions + deletions). labels Jul 30, 2026

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using high effort and found 3 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 02b9e1c. Configure here.

Comment thread apps/web/src/components/ChatView.tsx
Comment thread apps/web/src/components/ChatView.tsx
Comment thread apps/web/src/components/ChatView.tsx Outdated
@macroscopeapp

macroscopeapp Bot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Approvability

Verdict: Approved d11e4eb

UI polish change that makes server update banners appear calmer (default variant instead of warning, monochrome progress indicators instead of colorful ones). Self-contained visual refinement with no runtime behavior impact beyond presentation.

You can customize Macroscope's approvability policy. Learn more.

Bugbot findings: the banner fold now only applies while the update state
is idle, so a failed update keeps its error and retry action; hard
error/blocked connection phases surface the Reconnect banner even while
an update runs; and the folded title says "Connecting" on a first
attempt instead of always "Reconnecting".

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@t3dotgg
t3dotgg merged commit e0513d2 into main Jul 30, 2026
17 checks passed
@t3dotgg
t3dotgg deleted the t3code/redesign-update-connection-states branch July 30, 2026 14:30
github-actions Bot added a commit to omarcresp/t3code-flake that referenced this pull request Jul 30, 2026
## What's Changed
* docs: split user and maintainer docs, fix 100+ stale claims by @t3dotgg in pingdotgg/t3code#4807
* fix(web): server updates no longer look like warnings by @t3dotgg in pingdotgg/t3code#4992
* fix(connect): reboots no longer strand the relay link, 403s now say why by @t3dotgg in pingdotgg/t3code#4988
* Add project file picker (⌘P) and project content search (⇧⌘F) by @jakeleventhal in pingdotgg/t3code#4855
* Check for mobile app updates on launch by @juliusmarminge in pingdotgg/t3code#4958


**Full Changelog**: pingdotgg/t3code@v0.0.32-nightly.20260730.956...v0.0.32-nightly.20260730.957

Upstream release: https://github.com/pingdotgg/t3code/releases/tag/v0.0.32-nightly.20260730.957
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:L 100-499 changed lines (additions + deletions). vouch:trusted PR author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant