Making VS Code Quiet Again | Vinit KumarVS Code is a good editor, but its defaults no longer feel quiet to me.

The editor has accumulated tabs, sidebars, breadcrumbs, minimaps, notifications, source-control indicators, language services, AI controls, chat panels, inline suggestions, and dozens of small visual prompts. Each feature is defensible on its own. Together, they make the tool feel as if it is constantly asking for attention.

I wanted the opposite: a fast window for opening files, moving through text, and writing. Nothing else.

The motivation

I spend enough time thinking about code without also thinking about the editor. A good editing environment should disappear once the work begins. It should respond immediately, preserve muscle memory, and avoid presenting choices that have nothing to do with the current line of code.

This is not minimalism as decoration. It is an attempt to reduce the distance between thought and action.

I still use Git, terminals, debuggers, and AI tools. I simply do not need all of them embedded in the text editor. Git already works well from the command line and dedicated tools. AI assistants can run in a separate terminal or desktop application. Keeping those concerns outside VS Code makes the editor predictable again.

Start with an empty profile

VS Code profiles are the key to making this experiment safe. I created a profile named Monk instead of changing my normal configuration. An empty profile starts without my existing extensions and can be selected for a folder without affecting other workspaces.

That also makes the setup reversible. If I need a full IDE for a particular project, I can switch profiles instead of rebuilding the editor.

Remove the visible chrome

The first pass removed everything that did not directly help with editing:

activity bar

command center and layout controls

editor tabs and action buttons

breadcrumbs, minimap, sticky scroll, and folding controls

line numbers, glyph margin, indentation guides, and overview ruler

hover cards, CodeLens, inlay hints, lightbulbs, and parameter hints

inline suggestions and automatic completion popups

The result is almost entirely text. Files are opened with Quick Open, commands come from the Command Palette, and the file explorer is available when I explicitly ask for it.

Here is the shape of the visual configuration:

"workbench.activityBar.location": "hidden",<br>"workbench.editor.showTabs": "none",<br>"workbench.editor.editorActionsLocation": "hidden",<br>"breadcrumbs.enabled": false,<br>"editor.fontSize": 18,<br>"editor.lineNumbers": "off",<br>"editor.glyphMargin": false,<br>"editor.folding": false,<br>"editor.minimap.enabled": false,<br>"editor.stickyScroll.enabled": false,<br>"editor.scrollbar.vertical": "hidden",<br>"editor.scrollbar.horizontal": "hidden",<br>"editor.renderLineHighlight": "none"

Remove the background work too

A visually minimal editor can still do a surprising amount of work behind the scenes. The next step was to remove services rather than merely hide their buttons.

The Monk profile disables Git and GitHub integration, Emmet, debuggers, task detection, npm helpers, notebooks, media previews, merge helpers, authentication services, and built-in language servers. It also has no third-party extensions except VSCodeVim.

Generated directories are excluded from file watching and search:

"files.watcherExclude": {<br>"**/.git/**": true,<br>"**/node_modules/**": true,<br>"**/.venv/**": true,<br>"**/__pycache__/**": true,<br>"**/target/**": true,<br>"**/dist/**": true,<br>"**/build/**": true<br>},<br>"search.followSymlinks": false,<br>"git.enabled": false,<br>"task.autoDetect": "off",<br>"typescript.disableAutomaticTypeAcquisition": true,<br>"workbench.localHistory.enabled": false

This matters most when opening a large parent directory containing several projects. The better habit is still to open one repository at a time, but aggressive exclusions stop dependency trees and build artifacts from becoming the editor’s concern.

No AI inside the editor

I use AI extensively, but I do not want it present in every surface where I write code. Inline predictions interrupt my flow, and chat controls turn the editor into another assistant dashboard.

VS Code now has a master switch for this:

"chat.disableAIFeatures": true,<br>"chat.agent.enabled": false,<br>"chat.agentHost.enabled": false,<br>"github.copilot.enable": {<br>"*": false<br>},<br>"github.copilot.nextEditSuggestions.enabled": false

I also disabled the Codex, Claude, and Copilot agent hosts, AI plugins, voice features, session sync, and AI recommendations. This is not a rejection of AI. It is a boundary: the editor is where I write and inspect code; AI lives beside it, not inside it.

One theme and one extension

The visual system is equally constrained. The profile uses only Quiet Light , with automatic dark-mode switching disabled. Every other built-in color-theme package is disabled.

Quiet Light gives me a clear white canvas without trying to make the code look dramatic. I increased the editor font to 18 pixels...