Skip to content

fix(ui): use BrowserCode v2 wordmark#97

Closed
Alezander9 wants to merge 1 commit into
mainfrom
fix/browsercode-v2-wordmark
Closed

fix(ui): use BrowserCode v2 wordmark#97
Alezander9 wants to merge 1 commit into
mainfrom
fix/browsercode-v2-wordmark

Conversation

@Alezander9

@Alezander9 Alezander9 commented Jun 16, 2026

Copy link
Copy Markdown
Member

Replaces the upstream opencode v2 new-session wordmark with a BrowserCode wordmark generated from the existing TUI glyph source.\n\nChanges:\n- Render BROWSER/CODE from the same terminal glyph rows used by the CLI logo.\n- Preserve v2 watermark treatment with mask/filter.\n- Use muted color for BROWSER and currentColor for CODE.\n\nVerification:\n- bun typecheck from packages/ui\n- bun run typecheck


Summary by cubic

Replaced the v2 session wordmark with a BrowserCode wordmark built from our TUI glyphs. Keeps the v2 mask/filter treatment and uses muted color for “BROWSER” and currentColor for “CODE”.

  • Refactors
    • Switched from fixed SVG paths to grid-based rects generated from glyph rows (12px cells).
    • ViewBox size is computed from glyph widths; gradient mask and filter are preserved.
    • Left segment uses var(--v2-icon-icon-muted); right uses currentColor with tuned opacities.

Written for commit d3dee28. Summary will update on new commits.

Review in cubic

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/ui/src/v2/components/wordmark-v2.tsx">

<violation number="1" location="packages/ui/src/v2/components/wordmark-v2.tsx:67">
P2: Left wordmark color logic is inconsistent with the muted-BROWSER requirement. Weak/shadow pixels in BROWSER currently render as currentColor.</violation>
</file>

Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic

y={rect.y}
width={rect.width}
height={rect.height}
fill={rect.fill === "fill" ? "var(--v2-icon-icon-muted)" : "currentColor"}

@cubic-dev-ai cubic-dev-ai Bot Jun 16, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2: Left wordmark color logic is inconsistent with the muted-BROWSER requirement. Weak/shadow pixels in BROWSER currently render as currentColor.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/ui/src/v2/components/wordmark-v2.tsx, line 67:

<comment>Left wordmark color logic is inconsistent with the muted-BROWSER requirement. Weak/shadow pixels in BROWSER currently render as currentColor.</comment>

<file context>
@@ -1,74 +1,98 @@
+            y={rect.y}
+            width={rect.width}
+            height={rect.height}
+            fill={rect.fill === "fill" ? "var(--v2-icon-icon-muted)" : "currentColor"}
+            opacity={rect.fill === "fill" ? 0.72 : rect.fill === "weak" ? 0.2 : 0.12}
+          />
</file context>
Suggested change
fill={rect.fill === "fill" ? "var(--v2-icon-icon-muted)" : "currentColor"}
fill="var(--v2-icon-icon-muted)"
Fix with cubic

@Alezander9

Copy link
Copy Markdown
Member Author

Closing: this targeted the web/desktop v2 SVG wordmark, but the reported regression is in the terminal TUI logo. A replacement TUI-specific PR will follow.

@Alezander9 Alezander9 closed this Jun 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant