feat(web): show server versions on remote connections - #7271
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
ApprovabilityVerdict: Approved 57c8e7d This PR adds a simple, well-tested pure function to display server version information that already exists in the environment config. The change is purely cosmetic and self-contained with no runtime behavior changes beyond showing additional metadata text. You can customize Macroscope's approvability policy. Learn more. |
- Display connected server version (including nightly suffixes) in connection metadata - Show "Last seen v…" when disconnected but a cached version is available
57c8e7d to
0ccd396
Compare
Hello, just added the version in the connections page because i just forgot in what version my remote machines are. This helps me to quickly see and identified which ones i should update


AI GENERATED FROM HERE
What Changed
Remote environment rows now show the connected server version alongside their existing metadata. The full package version is preserved, including nightly suffixes.
When a disconnected environment still has cached server configuration, the row labels that value as
Last seen v…. Environments that have never reported a version remain unchanged.Why
A client can connect to servers running different T3 Code versions, but Settings only surfaced the exact version when there was a mismatch. Showing the version on every known remote connection makes the environment state obvious without adding a new request or changing any wire contracts.
UI Changes
Before: remote connection metadata only showed the connection type, such as
T3 Connector an SSH target.After: connected rows append the exact version, such as
T3 Connect · v0.0.33-nightly.20260816; disconnected rows with cached configuration showLast seen v….Screenshot pending attachment from the verified local fixture.
Verification
pnpm --filter @t3tools/web exec vp test run src/components/settings/ConnectionsSettings.logic.test.ts --project unit— 11 tests passedpnpm --filter @t3tools/web typecheckgit diff --checkChecklist
Model/harness: GPT-5.6 Sol via the Codex harness in T3 Code.
Note
Low Risk
Display-only change in settings UI, reusing cached server config with covered formatting logic and no auth or connection behavior changes.
Overview
Remote environment rows in Settings → Connections now include a server version in the metadata line (alongside SSH target and T3 Connect), using existing
serverConfig.environment.serverVersion—no new API or contract changes.A new
remoteEnvironmentVersionLabelhelper formats the string: connected backends showv{version}(full semver, including nightly suffixes); disconnected backends with cached config showLast seen v{version}; unknown versions add nothing. Unit tests cover those three cases.Reviewed by Cursor Bugbot for commit 0ccd396. Bugbot is set up for automated code reviews on this repo. Configure here.
Note
[!NOTE]
Show server version labels on remote connections in settings
Adds a
remoteEnvironmentVersionLabelutility in ConnectionsSettings.logic.ts that formats a server version string asv{version}when connected orLast seen v{version}when disconnected, returning null when no version is available. Each saved backend row in ConnectionsSettings.tsx now includes this label in its metadata display.Macroscope summarized 0ccd396.