Conversation
…header The web dashboard only surfaced the coding-agent and Turma versions once a host card was expanded (in .host-meta), while the Android card shows them in its collapsed header. Add a version line under the hostname, shown while the card is collapsed, so the web header carries the same at-a-glance facts — '<coding agent> <ver> · Turma <ver>' — without expanding. When expanded the fuller .host-meta row still carries them alongside memory/uptime/repos root. hostVerLine() reuses the existing codingAgent() legacy-string parsing and the '–' unknown fallback; unit-tested in host-header.test.js.
… or not Follow-up: the version line was shown in the header only while collapsed, and the same facts reappeared in the expanded .host-meta block — so toggling the card made the info jump from one place to another. Render the header version line unconditionally (collapsed and expanded alike) and drop the now-redundant Agent + Turma rows from .host-meta, so the version sits in one fixed spot under the hostname and stays visible when collapsed. .host-meta keeps memory / uptime / repos root / sessions.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
The web dashboard (
turma/public/index.html) only surfaced the coding-agent version and the Turma agent version once a host card was expanded (in the.host-metablock). The Android card already shows those two facts in its collapsed header. XERK-539 asks for parity: make that info visible in the web header when the card is collapsed too.Change
hostVerLine(a)(besidecodingAgent()): returns"<coding agent> <version> · Turma <agentVersion>", reusingcodingAgent()'s legacy raw-string parsing and its–unknown fallback.<span class="host-ver">, wrapped with the<h3>in a new.host-name-textflex column. When expanded it disappears and the fuller.host-metarow carries Agent/Turma as before (no duplication)..host-name-text(column) +.host-ver(muted 12px,word-break: break-word).turma/public/only; no server/agent plumbing.Web ⇄ Android parity
This closes a gap where the web lagged Android — the Android collapsed card header already shows
codingAgentLabel · Turma <ver>(FleetScreen.kt). No Android change is needed; the web is catching up to it.Verification
hostVerLinecases toturma/tests/host-header.test.js(the two versions present →"Claude Code 2.1.211 · Turma 1.2.3"; neither present →"– · Turma –"). Full turma suite green (1700 pass, 1 pre-existing skip).Qwen 3.0.5 · Turma 1.2.3)..host-metastill carries Agent/Turma.claudeVersion("2.1.211 (Claude Code)") parses toClaude Code 2.1.211 · …."– · Turma –", no throw.esc()d — XSS payload in host name/version rendered as literal escaped text,window.__XSSstayed false.collapsedHostslocalStorage persistence intact.hostCard()path, exercised on initial paint + reload).