A bug report filed on VSCode’s GitHub repository documents an issue where border radius—rounded corner styling—has been applied across multiple interface elements in the code editor.
According to the report, the issue affects VSCode version 1.139.0 on macOS (version 26.5.1). The user notes that rounded corners now appear on the text editor, file explorer, terminal, and Copilot chat components.
The reporter indicates the issue persists even with all extensions disabled, suggesting the problem originates from VSCode’s core rather than third-party plugins. The user describes the visual changes as distracting and affecting work efficiency, characterizing the widespread application of border radius as an unwanted aesthetic shift.
The issue has garnered attention as multiple users have contributed similar reports to the bug tracker, indicating the problem affects multiple installations. The reporter expresses surprise that the styling change has reached a desktop application, noting they expected desktop apps to be insulated from design trends common to web interfaces.
Border radius—the CSS property that creates rounded corners on UI elements—has become increasingly prevalent in modern interface design. However, its application across an entire desktop application’s interface represents a significant visual departure for VSCode, which has traditionally featured sharp, angular UI elements aligned with common code editor conventions.
The nature of the reports suggests this may be related to a recent VSCode update or theme change rather than a persistent bug, though the exact cause has not been confirmed in the available documentation. Users experiencing the issue report it affects core editor functionality visibility and usability, prompting requests for resolution or configuration options to revert to the previous appearance.
Microsoft has not yet provided an official response to the reports at the time of documentation.
Key facts
- Border radius styling is affecting VSCode’s text editor, file explorer, terminal, and Copilot chat
- The issue occurs in VSCode version 1.139.0 on macOS 26.5.1
- The problem persists with all extensions disabled, indicating a core VSCode issue
- Multiple users have reported the same issue, suggesting widespread impact