You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Redesign feedback: browser typography looks worse than before #25953
The text in the redesigned browser UI looks worse to me than before. This affects the interface broadly, including the goal text. The issue is the appearance of the text, not a hidden goal panel.
How to compare
Open the same conversation in the redesigned browser client and the previous design.
Compare the conversation, composer, and goal text at the same zoom and appearance settings.
Code and release status
The audit did not find a change to the default interface font stack between v0.1.2 and v0.1.4-nightly.20261027.3770. appearanceFonts.ts and index.css use the platform fonts followed by Inter Variable, Segoe UI, and system-ui. Appearance settings can override the interface font, size, and smoothing.
This does not resolve the reported visual regression. A specific change to letter shapes, size, weight, or spacing has not yet been isolated, so no global font replacement is proposed or claimed as a fix.
The connected server is v0.1.2 on Ubuntu 24.04.5 x86_64. The reporter's browser client build, browser version, client OS, zoom, and custom font settings remain unconfirmed. The server version alone does not identify the browser UI build.
Goal placement is tracked separately in #25954. That report concerns having to scroll to the bottom to reach goal status and controls.
I tried to reproduce this on the current build and could not.
On origin/main 31a108c, ran T3CODE_DEV_SEED=0 vp run dev in a fresh worktree and opened the web client in a Chromium browser on Linux x86_64. document.body and all sampled text compute to -apple-system, BlinkMacSystemFont, "Inter Variable", "Segoe UI", system-ui, sans-serif, and the only loaded font face is Inter Variable 100 900, so interface text renders in Inter. Git history: v0.1.2 does not contain the redesign commit 3816296 (#24865) and v0.1.4-nightly.20261027.3770 does; that commit changed --font-sans from -apple-system, BlinkMacSystemFont, "Segoe UI", system-ui, sans-serif to put "Inter Variable" ahead of Segoe UI/system-ui. So on Windows and Linux clients the interface font moved from the system UI font to Inter (macOS still resolves to SF Pro). Whether this looks worse is subjective, and the reporter's client OS is not stated, so 'looks worse' cannot be confirmed as a defect. No clipping, overlap or unreadable text was seen. The '90% chat text' change comes from the #24865 description and was not checked in the running app.
Closing as not planned. If it still happens for you, reply with the exact steps and the version you are on and it will be looked at again.
Activity
juliusmarminge commentedon Nov 12, 2026
I tried to reproduce this on the current build and could not.
On origin/main 31a108c, ran
T3CODE_DEV_SEED=0 vp run devin a fresh worktree and opened the web client in a Chromium browser on Linux x86_64. document.body and all sampled text compute to-apple-system, BlinkMacSystemFont, "Inter Variable", "Segoe UI", system-ui, sans-serif, and the only loaded font face isInter Variable 100 900, so interface text renders in Inter. Git history: v0.1.2 does not contain the redesign commit 3816296 (#24865) and v0.1.4-nightly.20261027.3770 does; that commit changed--font-sansfrom-apple-system, BlinkMacSystemFont, "Segoe UI", system-ui, sans-serifto put "Inter Variable" ahead of Segoe UI/system-ui. So on Windows and Linux clients the interface font moved from the system UI font to Inter (macOS still resolves to SF Pro). Whether this looks worse is subjective, and the reporter's client OS is not stated, so 'looks worse' cannot be confirmed as a defect. No clipping, overlap or unreadable text was seen. The '90% chat text' change comes from the #24865 description and was not checked in the running app.Closing as not planned. If it still happens for you, reply with the exact steps and the version you are on and it will be looked at again.