feat(diff): give the diff header its own white/gray identity#36
Open
rickliujh wants to merge 2 commits into
Open
feat(diff): give the diff header its own white/gray identity#36rickliujh wants to merge 2 commits into
rickliujh wants to merge 2 commits into
Conversation
The diff's module header shared the run log's colors, so it read like more run output and the teal hand-off faded against the diff. Give the header its own identity: - the turn chip is white (inverted), not the log's indigo root color, so the banner reads as "this is the diff"; - the hand-off jumps from the dim slate teal to a brighter teal so the breadcrumb between diffs stays legible. Only the two diff color constants change; layout and non-color output are untouched. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Bright color alone didn't stand out: the hand-off's hue sat next to the diff's cyan hunk lines, so a colored line couldn't separate from colored lines. Render the child — the module that produced the diff — as an inverted light-gray chip: a filled anchor no diff line has, one step below the white turn chip, and in neither the run log's indigo nor teal so it never reads as more run output. The marker and parent stay muted context. A turn with no submodule has no hand-off line, so it keeps just the white-chip turn banner, which already stands out on its own. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
rickliujh
force-pushed
the
feat/diff-header-color-identity
branch
from
July 23, 2026 23:45
25d4a30 to
79b8d11
Compare
rickliujh
changed the title
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.
Summary
Give the diff's module header a monochrome white/gray identity so it stands out against the diff and stays distinct from the run log (which owns the indigo and teal chips). Colored text alone couldn't separate from the diff's cyan/green lines, so the anchors are now filled chips.
≡ root ≡is white (38;5;231, inverted), not the log's indigo root color.38;5;250, inverted), one step below the turn chip. The▸marker and parent are muted gray (38;5;244) context. No teal — nothing collides with the run log.Diff header (real terminal)
No submodule? There's no
▸hand-off line at all — the header is just the white-chip turn banner, which already stands out on its own.Layout, non-color output, and the single-module header are unchanged.
Testing
go build ./...,go vet ./..., fullgo test ./...— all green.7m;231, gray submodule chip7m;250, no teal.🤖 Generated with Claude Code