VS Code 1.139 bug report: rounded corners spread across editor, terminal and file explorer

What happened

A bug report filed against Visual Studio Code 1.139.0 claims that rounded corners have appeared across large parts of the editor's interface. According to the report on Microsoft's VS Code GitHub repository, which reached the Hacker News front page, the effect touches the text editor, the file explorer, the integrated terminal and the Copilot Chat panel.

What the report says

The filing comes from a user running the macOS Universal build of VS Code 1.139.0 on OS version 26.5.1. The reproduction steps are unusually short: open VS Code, and the rounded corners are already there.

Notably, the reporter states that the problem occurs with all extensions disabled. That detail matters because VS Code's appearance can be reshaped heavily by themes and extensions, and "does it happen with extensions off?" is the standard first question maintainers ask. With that box ticked, the report points at the editor's own styling rather than anything the user installed.

The tone of the report is deliberately theatrical. Its author describes rounded corners as a design trend that spread across the web, jokes that desktop applications were supposed to be safe from it, and argues that the curves are a distraction that pulls attention away from the code.

Deliberate redesign or accidental regression

The issue is framed as a bug in its title, but the filing itself does not settle whether the styling was an intentional design change that shipped in 1.139 or an unintended regression, and the source material includes no response from Microsoft or the VS Code team.

The technical backdrop makes either explanation plausible. VS Code is an Electron application, so its interface is drawn with the same CSS machinery as the web, where corner rounding is a one-line change. Panels, side bars and editors are styled in stylesheets that the team revises release by release, which means a small styling edit can ripple across many surfaces at once — exactly the pattern the report describes.

Why it matters

A cosmetic change sounds trivial next to crashes and data loss, but an editor's interface is on screen for every hour of a developer's working day, and unexplained visual shifts are genuinely disruptive. For anyone who upgraded to 1.139 and wondered whether their setup was broken, the report offers a simple answer: this is a publicly filed issue, reproducible without extensions, and not something caused by a local theme or plugin.

The episode is also a small lesson in how interface changes land. When a visual alteration arrives without clear documentation, users cannot tell a bug from a feature, and issue trackers become the place where that ambiguity gets resolved. Anyone affected can follow the GitHub issue for a maintainer response or a fix; in the meantime, the practical options are limited to rolling back to an earlier VS Code release or waiting to see whether the curves are confirmed as a bug or declared the new design.