A run from another machine says so on the rail and the Overview, and is listed once across shared archives (#1648) - #1677
Merged
Merged
Conversation
…il, the name on the Overview card, one row per run across shared archives (#1648) The data branch is shared precisely so other machines' runs show up here, but a row from Rom's daemon looked exactly like one of this daemon's own, and two checkouts of one repository listed every run twice. The daemon now marks a record whose host is not this machine on the way to the dashboard (the same seam as the bridge's waiting mark, now applied to the pooled recents too), the rail row carries a glyph naming that machine, the Overview's working-now card spells it out, and the pooled recents list a run once.
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
1 participant
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.
🤖 automated
Closes #1648.
What the user sees. A run that another machine's daemon started now carries a laptop glyph at the end of its rail row, with the tooltip Started on rom-thinkpad-x280, by that machine's daemon. On the Overview's Agents currently working card the row says
from rom-thinkpad-x280outright — there is room there. And the pooled Recent agents list shows a run once, even when two registered checkouts (gemstack + tf-trust-e2e) share the archive that holds it.How. The record already carries
host(#716); what the dashboard lacked was this daemon's own hostname to compare against. The daemon now marks such a recordotherHoston the way to the dashboard — the same seam the bridge'scloudWaitingmark uses (markOtherHost, folded with it intoforDashboardindashboard-rpc/reads.ts). That step is now applied toonRecentAgentstoo, which it never was — so the pooled rail could not have said "waiting" for a parked cloud run before this.buildOverviewpasses the host of a working-now entry,buildRecentAgentsdedupes on run id.A word in the meta line was the first cut; the rail's fixed width truncated it to
from…, hence the glyph (the device glyph's pattern).Gap 2 of the issue (a cloud run's record freezes at the hand-off) is what #1669 shipped as
cloudRunState: a run with a PR reads done / merged, one inside the 12 h window reads in cloud, so nothing is left of it here.Verified. Typecheck, node + 806 vitest tests green; the five new tests each go red with their fix disabled. Dogfooded on this daemon against the real shared archive:
onRecentAgentsreturns 30 rows / 30 unique ids with 4 markedotherHost(Rom's web runs of 2026-08-22), the uncapped gemstack list marks 19, the Overview's two active runs (mine) carry no host, and the rail renders the glyph + tooltip.SPEC.md updated for every touched file (
agent-store,dashboard-rpc/reads,dashboard/overview,AgentHistory,Agents, their test specs) plusFEATURES-SPEC.md.