Repository navigation
Show the build as a status card - #654
Merged
Merged
Conversation
MaggieAppleton
force-pushed
the
build-machine
branch
from
October 16, 2026 12:26
92f9b3a to
09e4153
Compare
MaggieAppleton
force-pushed
the
build-status-card
branch
from
October 16, 2026 12:31
6088ae3 to
5dc548e
Compare
The Build tab's cramped status row becomes an inset card: the state glyph and title with the task count, the coding agent's live activity, one progress segment per task, and a footer naming who started the build, when, and the machine it runs on, with the action on the right. The machine's online dot shows only to the build's starter. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MaggieAppleton
force-pushed
the
build-status-card
branch
from
October 16, 2026 12:36
5dc548e to
6034f1e
Compare
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.
Builds on #653 (machine on the build snapshot), now merged.
What and why
The Build tab's header was one 32px row: "Building 0 of 2 started by you 0m [Stop build]". It is now the approved Proposal A, status card from the build-header jig:
buildMachinesin Record which machine runs each build #653. On the right: Stop, Return to planning or Cancel build, atbtn-sm.Only tokens and existing components (
Face,MachineGlyph,BuildGlyph, the shared icons,btn-*). There are no middots.Things to note
radius-sm / 2falls outside the design record's radius scale..build-statusrule inbuild-view.cssstays, because the phone capsule also uses that class.Screenshots
The real
BuildViewis rendered from fixed snapshots in a local, git-ignored harness (Vite page, headless Chromium, reduced motion). Live build states need a running connector and coding agent, so I didn't capture them from the running app. "Before" is the same harness with the base commit'sbuild-view.tsx. "Stopping" is the real Stop button pressed against a request that never answers.Tests
DEMO_PERSONAS=off bun test apps/web/src: the build-model and middot suites pass. The only failures are in the git-ignoreddesign-jig/files that exist locally, not in CI.bun run types: no errors outsidedesign-jig/. oxlint is clean on the changed files.bun run ci/design:checkreport findings only indesign-jig/.implementation-launcher.e2e.tsbecause the text is now split into title, count and footer: "Built" + "2 pull requests", "Building"/"Queued" + "0 of 2 tasks" + "You", and "Returned for changes" + "Build plan builds it again.". I also dropped theUpdatedstamp check. I didn't run e2e locally; it is left to CI.🤖 Generated with Claude Code