A CALMER CODE-OSS EDITOR

A quieter place
to write code.

Open a project. Write code. Review your changes. Lean VS Code keeps the familiar tools and dials back the stuff that tries to grab your attention.

Get it on GitHub Explore the source v0.3.2 · Apple Silicon Mac · Auto-update
Lean VS Code showing its emerald workbench while editing this project's source code

The editor, editing its own source. Take a closer look by opening the image.

MEASURED AGAINST CODE-OSS

Less waiting.
Less overhead.

18%

less time to an editable file

13%

lower idle memory footprint

Median results on an Apple M3 Max: Lean VS Code v0.3.0 versus the same-revision Code-OSS 1.139.1 build, using isolated profiles and a 100 KiB text file. Startup uses 30 warm-cache runs per app; memory sums macOS physical-footprint readings across each app's process tree after 30 seconds idle. v0.3.2 adds auto-update; these figures are from v0.3.0. Full comparisons run for minor releases; patch releases keep the latest minor's results labeled with the version measured. See the method and version history

That's 108 MiB less idle app-tree memory in this test, leaving more room for your browser, terminal, and other apps. On a Mac under memory pressure, that extra headroom can help the whole workflow stay responsive.

A DEVELOPER'S YEAR

Small waits add up.

7.1 hours

illustrative yearly saving

“In the past year, my ILOapps commits touched more than 70,000 files. At 0.362 seconds faster to an editable file, that's about seven hours if I start a fresh editor for every file. Actual savings depend on how often I launch it. Lower memory use also leaves more room for the rest of my work. I'll keep optimizing Lean VS Code.”
— Matti Vilola, creator of Lean VS Code

Illustration: 70,276 file touches × 0.362 seconds = 7.1 hours. Git history from 95 local ILOapps repositories, 26 September 2025–26 September 2026; 14,206 Matti-authored non-merge commits across 39 active repositories. Repeated changes to a file count again. Dependency/build paths and commits touching more than 100 files were excluded to limit bulk imports and scaffolds. The benchmark measures fresh app startup, so actual savings depend on how often you launch the editor.

THE GOOD PARTS STAY

Your workflow already fits.

01

Get straight to the work

Files, project search, the integrated terminal, and local Git review are ready when you need them.

02

Choose your extras

A smaller set of extensions comes built in. Find more through Open VSX or install a local VSIX.

03

Keep your setup separate

Lean VS Code has its own app identity, settings, and extensions, so it can sit beside VS Code.

WHY THIS FORK EXISTS

Sometimes you just want to open a folder and code.

Code-OSS is a great foundation. Lean VS Code is a take on what happens when the editor puts writing code and reviewing local changes first.

It ships with fewer built-in extensions and turns off unsolicited AI prompts, recommendations, experiments, and telemetry by default. Signed app updates from GitHub are the one background check enabled by default; you can change when Lean VS Code checks in Settings. The editor and extension platform are still there; you decide what to add.

Read the project story on GitHub

MADE FOR THE EVERYDAY LOOP

See what changed.
Keep moving.

Inspect local Git changes side by side in the familiar diff view, then get back to your code.

See the open-source project
Lean VS Code showing a side-by-side local Git diff

READY TO TRY IT?

Open the project.
Get to work.

Download the signed, notarized DMG from GitHub and drag Lean VS Code into Applications. The current release is for Apple Silicon Macs.

Starting with v0.3.2, Lean VS Code checks for signed macOS updates and offers Restart to Update when one is ready. If you have v0.3.0 or the withdrawn v0.3.1 candidate, install v0.3.2 once by hand to enable future updates.

Download on GitHub