Desktop code editors for your own projects: VS Code, OpenIDEA, VSCodium, Zed, Cursor and Kate
VS Code is the free editor we recommend for local projects that need language tools and debugging, as long as you check its settings and keep it updated. OpenIDEA, our Rising Star, is an open-source editor first released on October 22, 2026, with a debugger, Git and a terminal built in; VSCodium, Zed, Cursor and Kate complete the comparison.
Visual Studio Code
Free on Windows, macOS and Linux, with extensions for hundreds of languages and debuggers, and built-in Git staging and commits.
Telemetry is on until you turn it off, extensions run with full permissions, and Restricted Mode needed repeated security fixes in 2026: keep it updated.
Why VS Code is our PickTeam behind Visual Studio Code? Get your award badge
OpenIDEA
A free, open-source editor first released on October 22, 2026, with a debugger, Git, a terminal and language support for 60+ languages built into one native window on Windows, macOS and Linux, per its maker.
It was first released on October 22, 2026, its plug-in interface is a preview, and we found no independent review or statement about its telemetry.
Why OpenIDEA earned Rising StarWho is this article for? People choosing a desktop editor for their own source projects on Windows, macOS or Linux who want language-aware editing, Git and debugging without paying or needing an account.
About 40 min read
What Preferred Pick, Rising Star and Ready to Rock mean
The quick list
All six are free; Cursor needs an account, and Zed and Cursor sell optional AI plans. Compare what you must install around each editor, how it handles your data and unfamiliar projects, and where it runs.
Editor prices checked November 12, 2026, in US dollars before tax. VS Code, VSCodium, OpenIDEA, Kate and Zed’s Personal plan are free for ordinary editing. Cursor’s Free plan covers editing with limited AI use; its paid plans ($8 to $200 a month), Zed Pro ($10 a month, with $5 of hosted-model tokens) and GitHub Copilot plans are optional AI services.
The comparison at a glance
Compare what each editor costs, what you must install around it, how it handles Git and debugging, and what it does with your data and unfamiliar projects.
Order follows our verdict for editing your own projects: the Pick, the Rising Star, then the others by our scores, not measured speed or security. All tools remain selectable.
Hides matching answers for the selected tools. Unknowns and unverified claims stay visible.
| Feature | Visual Studio Code | OpenIDEA | VSCodium | Zed | Cursor | Kate |
|---|---|---|---|---|---|---|
| Best fit | Preferred Pick: local projects that need a particular language extension or debugger | Rising Star: an IDE-style window with debugger, Git and terminal built in, if you accept a very new release | No label: VS Code’s editing without Microsoft’s telemetry, if a smaller extension registry is enough | No label: built-in Git, multi-file editing and debugging without assembling extensions | No label: a VS Code-based editor, if you accept a required account and its security defaults | Also consider: Linux desktop projects under KDE’s opt-in telemetry policy |
| Editor cost, checked November 12, 2026 | Free for private and commercial use | Free, Apache-2.0 open source | Free, MIT-licensed builds of VS Code’s source | Personal plan free; optional Pro $10/month and Business $30/seat/month for hosted AI and controls | Free plan $0 for editing, with limited AI use; paid plans $8 to $200 a month cover AI | Free, open source |
| Stable desktop releases | Supported 64-bit Windows; macOS versions Apple still patches; Linux with glibc 2.28+ | Installers for Windows, macOS and Linux; no system requirements published | Windows, macOS and Linux builds and package managers; no requirements page read | Windows 10 1903+ and 11 (x64, Arm64); macOS 12+ (10.15–11 partial); Linux with a Vulkan 1.3 driver | macOS (Apple silicon and Intel), Windows (x64, Arm64), Linux .deb and RPM (x64, Arm64); no minimum versions published | Linux distributions, Flathub and Snap; Windows via Microsoft Store; Mac links are testing-only nightlies |
| Language-aware tooling | Built-in features vary; extensions add language servers and tools | Language-server code insight for 60+ languages, per its maker | VS Code’s language features with Open VSX extensions; extensions limited to Microsoft’s builds do not run | Built-in or extension languages; language servers downloaded automatically | VS Code’s language features with Open VSX extensions; some Microsoft-only extensions replaced by Cursor’s own builds | LSP Client plugin plus a language server you install and configure |
| Git in the editor | Review, stage and commit; Git installed separately | Git listed among its built-in tools; staging details not read | VS Code’s Source Control panel: review, stage and commit | Hunk and file staging, commits and branches in the Git panel | VS Code’s Source Control panel: review, stage and commit | Git panel: stage, commit, push, pull and branches (Kate’s 2023 guide) |
| Debugging | Through language extensions and their debuggers | Built-in debugger, per its maker; the newest notes add Kotlin and Bun debugging | Through language extensions; some proprietary debugging tools do not run outside Microsoft’s builds | Debug adapters built in for C, C++, Go, JavaScript, PHP, Python, Rust and TypeScript; extensions for others | Through language extensions and their debuggers, as in VS Code, where Open VSX carries them | GDB plugin: a front end for GDB or another Debug Adapter Protocol debugger you install |
| Telemetry default | On until telemetry.telemetryLevel is off; extensions collect separately | No telemetry or privacy statement in the pages we read: we make no claim | Disabled in its builds; extensions may still collect their own data | Usage metrics and crash reports on until switched off; ID may be linked to email if signed in | Account required; individuals must switch Privacy Mode on to keep code out of model training; usage data collected under its terms | KDE policy: opt-in and off by default; distributor builds may differ |
| Opening unfamiliar projects | Restricted Mode limits tasks, terminal, debugging and extensions; 32 advisories from September to November 2026, ten on November 10, all fixed by 1.145.3 | Release notes describe trusted folders and Restricted Mode (maker's claim, untested); no published security advisories, with a private-report policy | Same Workspace Trust as VS Code, but its latest build (1.143) predates the 1.145.3 fixes for ten advisories published November 10, 2026 | Restricted Mode blocks project settings and project language and MCP servers; .git/config flaw fixed in 0.227.1 | Workspace Trust off by default per Oasis Security (updated May 2026), so a project’s folder-open tasks can run; current default unconfirmed | Per KDE’s 2022 advisory, runs Git and language servers automatically when those plugins are on; that year’s binary-path flaw is fixed |
Researched comparison, not a hands-on review: no installs, extensions, accounts, speed or security tests by us. Scope is local desktop source editing, not hosted IDEs, terminal editors or AI-agent quality. Built-in features, external tools and paid services are kept apart. Prices, releases and advisories for the six editors checked November 12, 2026; other documentation checked October 19 and 20, 2026; next substantive review December 18, 2026, or sooner after a major release, price change or security event.
All features and sources 18 criteria
Open the groups that matter to you. They compare the same selected tools. “Planned” means future work, not an available feature. Sources include the published conditions.
Cost, platforms and accounts
Show 6 criteria
| Feature | Visual Studio Code | OpenIDEA | VSCodium | Zed | Cursor | Kate |
|---|---|---|---|---|---|---|
| Best fit | Preferred Pick: local projects that need a particular language extension or debugger | Rising Star: an IDE-style window with debugger, Git and terminal built in, if you accept a very new release | No label: VS Code’s editing without Microsoft’s telemetry, if a smaller extension registry is enough | No label: built-in Git, multi-file editing and debugging without assembling extensions | No label: a VS Code-based editor, if you accept a required account and its security defaults | Also consider: Linux desktop projects under KDE’s opt-in telemetry policy |
| Editor cost, checked November 12, 2026 | Free for private and commercial use | Free, Apache-2.0 open source | Free, MIT-licensed builds of VS Code’s source | Personal plan free; optional Pro $10/month and Business $30/seat/month for hosted AI and controls | Free plan $0 for editing, with limited AI use; paid plans $8 to $200 a month cover AI | Free, open source |
| Stable desktop releases | Supported 64-bit Windows; macOS versions Apple still patches; Linux with glibc 2.28+ | Installers for Windows, macOS and Linux; no system requirements published | Windows, macOS and Linux builds and package managers; no requirements page read | Windows 10 1903+ and 11 (x64, Arm64); macOS 12+ (10.15–11 partial); Linux with a Vulkan 1.3 driver | macOS (Apple silicon and Intel), Windows (x64, Arm64), Linux .deb and RPM (x64, Arm64); no minimum versions published | Linux distributions, Flathub and Snap; Windows via Microsoft Store; Mac links are testing-only nightlies |
| Account needed for | Copilot features (GitHub sign-in); not for editing | No account named in the pages we read; agent features use tools you connect | None; Microsoft’s telemetry and extension gallery are not configured in its builds | Collaboration and Zed-hosted AI (GitHub sign-in); not for editing | Required: you sign in with a Cursor account to use the editor | No account documented |
| Current release, checked November 12, 2026 | 1.146, November 11, 2026; stable releases most weeks | 0.1.43, November 12, 2026; first released October 22, 2026; several releases a week | 1.143, October 28, 2026; trails VS Code by several versions | 1.28.1, November 11, 2026; weekly releases; 1.0 in April 2026 | 3.24 listed as latest on October 20, 2026; the download page shows no version now | 26.08.3, November 5, 2026; about three application releases a year |
| Distinctive reason to choose it | Marketplace extensions for hundreds of languages, per Microsoft: the widest choice here | IntelliJ IDEA-style keymap, debugger, Git, terminal, database and HTTP clients in one native window, per its maker | The same editor with telemetry disabled by default and no Microsoft branding | Edit excerpts from several files together in one multibuffer | Built around AI agents, which carry no weight here; otherwise close to VS Code’s editing | Published opt-in telemetry policy within the KDE desktop |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for cost, platforms and accounts
Checked November 12, 2026: VS Code FAQ, license and release notes; Zed pricing and releases; Cursor pricing; Kate application page and download channels; VSCodium and its releases; OpenIDEA repository and releases. Checked October 19, 2026: VS Code requirements; Zed authentication and requirements. Cursor, checked October 20, 2026: downloads and install guide. Prices exclude tax; no checkout or license activation performed. Zed’s paid plans cover hosted AI and team controls, not core editing.
Language tools, Git and debugging
Show 6 criteria
| Feature | Visual Studio Code | OpenIDEA | VSCodium | Zed | Cursor | Kate |
|---|---|---|---|---|---|---|
| Language-aware tooling | Built-in features vary; extensions add language servers and tools | Language-server code insight for 60+ languages, per its maker | VS Code’s language features with Open VSX extensions; extensions limited to Microsoft’s builds do not run | Built-in or extension languages; language servers downloaded automatically | VS Code’s language features with Open VSX extensions; some Microsoft-only extensions replaced by Cursor’s own builds | LSP Client plugin plus a language server you install and configure |
| What you install around it | Extensions may also need runtimes, compilers and debuggers | Compilers and runtimes for your language; its pages do not say which language servers it fetches, so check yours | Open VSX extensions may also need runtimes, compilers and debuggers; check that yours is listed | Language servers fetched on first use; some languages need an extension | Open VSX extensions may also need runtimes, compilers and debuggers; check that yours is listed | Language servers and build tools; set server paths in the plugin |
| Extension model | Marketplace extensions with VS Code’s own permissions; publisher-trust prompt since 1.97 | Plug-ins run as sandboxed WebAssembly components; the plug-in interface is still a preview | Open VSX registry; the project says some extensions restrict their use to Microsoft’s builds | Zed’s own extension catalog; do not assume a VS Code extension has an equivalent | Open VSX through Cursor’s malware-scanning proxy; a September 2026 build reported extension API 1.128, behind VS Code | KDE application plugins and external tools |
| Git in the editor | Review, stage and commit; Git installed separately | Git listed among its built-in tools; staging details not read | VS Code’s Source Control panel: review, stage and commit | Hunk and file staging, commits and branches in the Git panel | VS Code’s Source Control panel: review, stage and commit | Git panel: stage, commit, push, pull and branches (Kate’s 2023 guide) |
| Debugging | Through language extensions and their debuggers | Built-in debugger, per its maker; the newest notes add Kotlin and Bun debugging | Through language extensions; some proprietary debugging tools do not run outside Microsoft’s builds | Debug adapters built in for C, C++, Go, JavaScript, PHP, Python, Rust and TypeScript; extensions for others | Through language extensions and their debuggers, as in VS Code, where Open VSX carries them | GDB plugin: a front end for GDB or another Debug Adapter Protocol debugger you install |
| AI features | Copilot chat and suggestions built in; chat.disableAIFeatures hides and disables them | An agent panel for coding agents such as Claude, Codex and Qwen Code; not weighed here | Not checked; AI features carry no weight here | Agents and edit predictions; own keys, local models or Pro; can be disabled | Agents, chat and completions are central; Privacy Mode governs training on your code | None in the features we reviewed |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for language tools, git and debugging
VS Code languages, extensions, Git and AI settings; Zed languages, language-server setup, Git, multibuffers and debugger; Cursor extensions and Git, October 20, 2026; VSCodium README and OpenIDEA README and v0.1.43 notes, November 12, 2026. Kate projects, LSP Client, GDB plugin and Git guide, February 2023. Syntax highlighting is not proof of semantic tooling. No project, extension or debugger was run.
Data, security and keeping your work
Show 6 criteria
| Feature | Visual Studio Code | OpenIDEA | VSCodium | Zed | Cursor | Kate |
|---|---|---|---|---|---|---|
| Telemetry default | On until telemetry.telemetryLevel is off; extensions collect separately | No telemetry or privacy statement in the pages we read: we make no claim | Disabled in its builds; extensions may still collect their own data | Usage metrics and crash reports on until switched off; ID may be linked to email if signed in | Account required; individuals must switch Privacy Mode on to keep code out of model training; usage data collected under its terms | KDE policy: opt-in and off by default; distributor builds may differ |
| Opening unfamiliar projects | Restricted Mode limits tasks, terminal, debugging and extensions; 32 advisories from September to November 2026, ten on November 10, all fixed by 1.145.3 | Release notes describe trusted folders and Restricted Mode (maker's claim, untested); no published security advisories, with a private-report policy | Same Workspace Trust as VS Code, but its latest build (1.143) predates the 1.145.3 fixes for ten advisories published November 10, 2026 | Restricted Mode blocks project settings and project language and MCP servers; .git/config flaw fixed in 0.227.1 | Workspace Trust off by default per Oasis Security (updated May 2026), so a project’s folder-open tasks can run; current default unconfirmed | Per KDE’s 2022 advisory, runs Git and language servers automatically when those plugins are on; that year’s binary-path flaw is fixed |
| Without a network connection | Install extensions and their tools first; updates, Marketplace and sync need a network | Updates itself; the pages we read do not say what else needs a network | Install extensions and their tools first; Open VSX and updates need a network | Preload language servers; collaboration and hosted AI need a network | Sign-in needs a network; install extensions and their tools first | Keep plugins, language servers and build tools installed locally |
| Keeping your work | Source and Git history are ordinary files; settings and extensions stay behind | Source and Git history are ordinary files; settings and plug-ins stay behind | Source and Git history are ordinary files; settings and extensions stay behind | Source and Git history are ordinary files; settings and hosted-service records stay behind | Source and Git history are ordinary files; settings, extensions and account records stay behind | Source and Git history are ordinary files; sessions and .kateproject settings stay behind |
| Main reason to choose something else | Telemetry on by default, extension permissions and frequent trust-bypass fixes | First released October 22, 2026, no independent review found, preview plug-in interface, telemetry unstated | Smaller extension registry, and builds that lag VS Code and its security fixes | Own extension catalog, so check your language and debugger first; usage metrics on by default; Linux needs Vulkan 1.3 | Required account, Workspace Trust off by default, and recent builds on Electron 42, out of support since October 19, 2026 | No stable Mac release |
| Outside evidence | Self-selected speed and workflow discussion; no verified aggregate | Its maker’s own benchmark and a large contributor count; no independent review found | Project documentation and repository activity; no independent review read | Mixed workflow and speed reports, including a disclosed employee | Security-firm report and user bug reports on defaults and runtime age; no verified aggregate | Favorable community workflow reports; not a representative sample |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for data, security and keeping your work
VS Code telemetry, network, Workspace Trust and security advisories, including GHSA-g3fj-wc2g-v3j5, November 10, 2026; Zed telemetry, Restricted Mode and security advisories; Cursor privacy, data use, security advisories, Oasis Security report, updated May 1, 2026, September 2026 bug report showing Electron 42 and Electron’s release schedule, October 20, 2026; VSCodium advisories and OpenIDEA repository, November 12, 2026. KDE application privacy and KDE advisory, January 2022. Readiness without a network is a documented-dependency assessment, not an air-gap or privacy certification. See What people are saying for the limited outside sample.
What matters when choosing
Visual Studio Code is our Practical Pick for someone choosing a desktop editor for their own source projects on Windows, macOS or Linux who wants language-aware editing, Git and debugging without paying. Microsoft’s build is free for private and commercial use and has stable releases for all three systems. Microsoft says its extension marketplace covers hundreds of programming languages, with language servers, linters and debuggers; in our judgment that is the widest choice of the editors here. Its built-in Git view handles reviewing, staging and committing. The most important compromise is that the language support you need comes from extensions, which run with VS Code’s own permissions and may need a compiler, runtime or debugger installed separately. Pick the extension for your language before you judge the editor. FAQ, extensions, languages, Git
Two settings and one habit matter. Usage telemetry stays on until you set telemetry.telemetryLevel to off, and that switch does not cover extensions’ own data collection. The built-in AI chat and suggestions can be hidden and disabled with chat.disableAIFeatures; Microsoft says nothing is sent to the Copilot service if you disable AI features or do not sign in. And keep it updated. Microsoft published 32 VS Code security advisories from September to November 2026, at least ten of them describing ways around Workspace Trust or Restricted Mode, the protection VS Code applies to folders you have not trusted. The newest ten, published November 10, are fixed in version 1.145.3, and the current release is 1.146 (November 11). Treat Restricted Mode as a first check, not as a safe way to open code you suspect is hostile. Telemetry, AI features, Workspace Trust, advisories
OpenIDEA is our Rising Star for people who want a debugger, Git and a terminal built into one native editor and are willing to try something very new. It is free and open source, runs on Windows, macOS and Linux, and was first released on October 22, 2026. Under the criteria we fixed before scoring, it scored highest of the newer editors we found, clearly ahead of the next one we could recommend, Trae, which needs an account. Devin Desktop scored between them but is not eligible: its latest build is based on a VS Code version that predates Microsoft’s November security fixes. The evidence for OpenIDEA is thin: we found no independent review, its plug-in interface is still a preview, and its pages do not say what telemetry it sends. Its maker documents a debugger, Git, a terminal and language support for more than 60 languages, with an IntelliJ IDEA-style keymap, and its release notes describe trusted folders and a Restricted Mode for unfamiliar projects. Its repository lists no security advisories and publishes a policy for private reports. Try it on a copy of a project before you rely on it. OpenIDEA repository, first release, latest release, security policy
VSCodium is the same editor with Microsoft’s telemetry switched off; it came second in our scoring, but its builds trail VS Code and lack the November security fixes until it catches up. Zed builds in Git, multi-file editing and debugging, and Cursor is VS Code’s editing behind a required account. On a Linux desktop, consider Kate: KDE’s policy makes any telemetry opt-in and off by default, and its Git panel stages, commits and pushes. Its Mac downloads are nightly test builds. Sublime Text is a standalone editor you buy once for $99 with three years of updates. VSCodium, Zed pricing, Kate downloads, Sublime store
These are researched judgments from documentation, release records, security advisories and public reports; prices, releases and advisories were rechecked on November 12, 2026 and the rest of the evidence was checked on October 19 and 20, 2026. We did not install or run any editor, so we make no speed or memory claim. Three conditions would change our recommendation: a reader who wants no Microsoft telemetry and can live with a smaller extension registry (choose Kate on a Linux desktop, or VSCodium on any system); a workflow built around in-editor Git and multi-file edits in languages Zed supports well (choose Zed); or a Mac running a macOS version Apple no longer patches, which current VS Code does not support (Zed and Sublime Text support older releases). Whichever you choose, your source files and Git history stay ordinary files you can open elsewhere; settings and extensions do not move between editors. VS Code requirements, Zed requirements
Disclosure: Practical Picks articles are researched and written with AI, currently Anthropic’s Claude. Visual Studio Code offers Anthropic’s Claude as a built-in model provider and integrates the Claude Agent SDK, and OpenIDEA, our Rising Star, supports Claude’s models and commands in its agent panel. We have no relationship with Microsoft, OpenIDEA’s maker or Anthropic over this article, and these Claude links carried no weight in our judgment. VS Code third-party agents, OpenIDEA release notes
Visual Studio Code
Preferred Pick · local projects that need language tools
Choose VS Code when your project depends on a particular language extension or debugger. Turn telemetry off if you prefer, hide the AI features if you do not want them, and keep it updated.
Reasons to choose it
- Marketplace extensions for hundreds of languages, per Microsoft
- Built-in Git review, staging and commits
- Stable releases for Windows, macOS and Linux
What to watch
- Telemetry is on until you switch it off; extensions collect separately
- Extensions run with the editor’s own permissions
- 32 security fixes from September to November 2026, several for Restricted Mode
VS Code is free for private or commercial use and runs on Windows, macOS and Linux. We verified that Microsoft now ships a stable release most weeks: 1.140 on September 30, 1.141 on October 7 and 1.142 on October 14, and 1.146 on November 11, 2026. Supported systems are 64-bit Windows client versions Microsoft still supports, macOS versions that still get Apple security updates (typically the latest three), and Linux distributions with glibc 2.28 or later. Microsoft’s downloadable application has its own license; the MIT-licensed source repository is a different licensing object, and editors built from that source are outside this comparison. FAQ, license, requirements, release notes, 1.146, releases
Built-in language features vary by language. Extensions add language servers, debuggers and other tools, and may also need a compiler, runtime or command-line program installed separately. Before choosing it for a course or project, identify the exact extension and its prerequisites: “supports Python” is less useful than knowing which interpreter and debugging setup the project expects. Extensions have the same permissions as VS Code itself. Since version 1.97, VS Code asks you to confirm that you trust a third-party publisher the first time you install one of its extensions. Language overview, extension marketplace
Read the full Visual Studio Code analysis and sources
The Git view is a practical reason to keep project work here: it supports reviewing changes, staging and committing inside the editor. Git itself must be installed. Local commits and sending them to a remote host are separate operations; a local project does not need to become a hosted repository. Source control
Microsoft documents a core telemetry switch, telemetry.telemetryLevel. Setting it to off stops VS Code’s own usage reporting and its experiments service, but third-party extensions may collect data separately. VS Code now includes chat and inline suggestions tied to GitHub Copilot, which has a free plan with a monthly allowance; chat.disableAIFeatures, at user or workspace level, hides and disables them, and Microsoft says a previous choice to disable them is kept after updates. Microsoft’s FAQ also says about half the VS Code team works on AI features. Updates, extension discovery and settings sync need a network connection; prepare the language tools you need before working without a network connection, and do not treat a saved extension package as containing all of its dependencies. Telemetry, FAQ, AI features, network
Restricted Mode is VS Code’s safeguard for folders you have not trusted: it limits tasks, the terminal, debugging, workspace settings, extensions and AI agents. Microsoft’s documentation says it cannot stop a malicious extension. The 2026 advisory record shows its limits too. On September 8 and October 13, Microsoft published 11 advisories each, and on November 10 it published ten more, nine rated High. Among them, a project’s settings file could change a terminal option Restricted Mode should have blocked, relaunching a terminal skipped the trust check, a crafted extension-recommendations file could produce a notification link that ran commands, and a critical path-handling flaw could, in some remote setups, extend trust to a folder outside the one you trusted. The November advisories include three more Workspace Trust bypasses: one treated a workspace configuration file fetched over the network as trusted, one let a crafted settings group key in a project’s .vscode/settings.json keep Workspace Trust from applying, and a third is titled a prototype-pollution bypass in workspace configuration. The two November pages we read list version 1.145.3 as the fix; the current release is 1.146. Many other advisories concern the AI agent, MCP and Copilot features. Keep automatic updates on, and open code you have reason to distrust in a disposable virtual machine or container. Workspace Trust, advisory index, terminal-option bypass, critical path-handling flaw, network workspace-file bypass, settings-key bypass
Choose OpenIDEA if you want a debugger, Git and a terminal built in and can accept a very young project, VSCodium if you want the same editor without Microsoft telemetry, Zed if you would rather have Git, multi-file editing and debugging built in than assemble extensions, and Kate on a Linux desktop if opt-in telemetry matters more than extension choice.
Used Visual Studio Code? Share your experience to help other readers choose.
OpenIDEA
Rising Star · IDE-style window with debugger, Git and terminal built in
Why Rising Star? First released on October 22, 2026, OpenIDEA scored highest of the newer editors under our fixed criteria, well ahead of the next one we could recommend, Trae. Its maker documents a debugger, Git and a terminal built into one native window on Windows, macOS and Linux, and no account requirement appears in the pages we read. It is new, its plug-in interface is a preview, we found no independent review and no statement about its telemetry, so treat it as one to try rather than a proven choice. Its repository lists no security advisories and publishes a policy for private reports.
Consider OpenIDEA if you like IntelliJ IDEA’s keymap and layout, want the debugger, Git and terminal in the editor, and are comfortable with a project this young.
Reasons to choose it
- Debugger, Git, terminal, database and HTTP clients in one window, per its maker
- Installers for Windows, macOS and Linux, with self-update
- Open source under Apache-2.0
What to watch
- First released October 22, 2026, with no independent review we could find
- Plug-in interface is still a preview
- Its pages do not state what telemetry it sends
OpenIDEA is a free, open-source desktop editor whose maker describes it as “the IDE you know, rebuilt in Rust”: IntelliJ IDEA’s keymap, tool windows and search-everywhere habits in a native app, with an editor, code insight, debugger, Git, terminal, and database and HTTP clients “for 60+ languages”. Its first public release, version 0.1.0, appeared on October 22, 2026, and version 0.1.43 followed on November 12, 2026, 39 releases between October 22 and November 12. It scored 3.83 on our five-point scale, behind VS Code’s 4.48 and level with Cursor, and highest of the newer editors we found, ahead of Trae (3.53), the next one we could recommend; the score is tentative because almost everything we know about it comes from its maker’s pages. It earns the award for building in what VS Code assembles from extensions, on all three systems, without an account in anything we read. Choose it if you like IntelliJ IDEA’s layout, want the debugger, Git and terminal in the editor, and are comfortable adopting a project this recent; keep VS Code installed beside it for a while. Repository and README, first release, v0.1.0, v0.1.43 notes
The code is licensed under Apache 2.0, so the price is $0 and the source can be forked. Release 0.1.43 offers installers for Windows (EXE), macOS and Linux and updates itself from within the app; no minimum system versions are published on the pages we read. The maker’s notes for that release list a profiler for JVM runs, Kotlin and Bun debugging, Django templates, notebook code intelligence, and custom agents for coding assistants such as Claude, Codex and Qwen Code, none of which we weighed. The README’s benchmark, opening a Python project of about 770 files in 0.9 seconds against 3.1 seconds for IntelliJ IDEA, is the maker’s own measurement on one Windows machine; we did not repeat it. README, v0.1.43 notes
Read the full OpenIDEA analysis and sources
Plug-ins run as sandboxed WebAssembly components, but the maker calls the plug-in interface “still a preview”, so do not expect the extension choice of VS Code. For unfamiliar projects, its release notes describe trusted folders (“Add trusted folders from Settings”) and sessions that “stay in Restricted Mode”; that is the maker’s claim, which we did not test. The repository publishes a security policy that asks for private vulnerability reports and promises an advisory once users can update; its advisory page lists none, and the newest issues we read among 136 open and 1,009 closed were ordinary bugs and feature requests. With so short a history, an empty advisory list is not proof of safety. We found no statement about telemetry, no privacy policy or terms (the project’s site did not load for us), and no independent review. The repository belongs to a GitHub account named l0ng-ai with 145 contributors; we found no named company or maintainer and no business model beyond voluntary sponsorship, and we scored its continuity on that, not on its age. The application runs locally and opens ordinary project folders, so your source and Git history stay ordinary files. Choose VS Code when a specific extension or debugger decides the project, and Zed if you want built-in Git and debugging from a longer-established project. Security policy, advisories, issues, releases
Used OpenIDEA? Share your experience to help other readers choose.
VSCodium
VS Code’s editing without Microsoft’s telemetry
Consider VSCodium if you want VS Code’s editor without Microsoft’s telemetry and account hooks, and the Open VSX extension registry covers your languages. Update it promptly: its builds trail VS Code.
Reasons to choose it
- VS Code’s editor, Source Control and terminal with telemetry disabled by default
- Free MIT-licensed builds for Windows, macOS and Linux
- Package managers such as Homebrew and WinGet
What to watch
- Open VSX is smaller than the Microsoft Marketplace; some extensions will not run
- Its latest build predates the 1.145.3 fixes for ten November 10 advisories
- Run by the community, a few versions behind VS Code
VSCodium is a community-driven, freely licensed binary distribution of Microsoft’s VS Code source. The project explains that Microsoft’s downloadable VS Code has its own license and Microsoft-specific telemetry and extension-gallery settings, and that VSCodium builds the open-source code without them: “These binaries are licensed under the MIT license. Telemetry is disabled.” Builds exist for Windows, macOS and Linux, with Homebrew and WinGet packages. It scored 4.00 on our five-point scale, second only to VS Code (4.48): the same editing, Source Control panel and terminal, but a smaller extension registry and slower security updates. We added it because it is widely used and its feature set matches the Pick’s, not because it is new. VSCodium, repository
Because Microsoft’s Marketplace terms allow its extensions only in Microsoft’s products, VSCodium uses the Open VSX registry. The project’s README warns that some VS Code extensions have licenses that restrict them to the official builds, including proprietary debugging tools, so check that the extension and debugger your language needs are listed. Language servers, runtimes and compilers still have to be installed separately, as in VS Code. README, extensions and the Marketplace
Read the full VSCodium analysis and sources
The main drawback is update speed. VSCodium’s latest release, 1.143, was published on October 28, 2026, while VS Code is at 1.146. Two of the ten advisories Microsoft published on November 10, 2026, both Workspace Trust bypasses, say versions before 1.145.3 are affected, which includes the code VSCodium 1.143 is built from, so until the project publishes a newer build it carries that exposure. The project’s own advisory page lists none. Extensions run with the editor’s own permissions, as in VS Code, and extensions may collect their own data. It is not independent evidence about VS Code’s features: it builds the same source, so every claim about its editing rests on Microsoft’s documentation. Choose VS Code for the widest extension choice and fastest fixes, and VSCodium if telemetry matters more to you than either. Advisory: network workspace-file bypass, advisory: settings-key bypass, VSCodium releases, VSCodium advisories
Used VSCodium? Share your experience to help other readers choose.
Zed
Built-in Git, multi-file edits and debugging
Consider Zed if you want staging, multi-file editing and debugging in the editor rather than assembled from extensions, and your languages are well supported.
Reasons to choose it
- Edit excerpts from several files together in a multibuffer
- Hunk staging, commits and branches built in
- Built-in debug adapters for eight languages, including Python, Rust and Go
What to watch
- Usage metrics are on by default and may be linked to your email if you sign in
- Its own extension catalog: check your language first
- Linux needs a Vulkan 1.3 driver
Zed is the longer-established of the two editors here that build in Git, multi-file editing and debugging. Zed Industries announced it as a public beta on March 15, 2023, and released version 1.0 on April 29, 2026. It scored 3.93 on our five-point scale, behind VS Code’s 4.48 and VSCodium’s 4.00, and ahead of Cursor (3.83). Choose it if built-in hunk staging and commits, editing across several files in one view, and debug adapters for eight languages matter more to you than the widest extension choice, and check its language list, its telemetry setting and, on Linux, your graphics driver before you switch. As a stable product it has a six-month record, and we found no independent measurement of its speed or reliability.
Zed’s Personal plan is free, and signing in is not required for most editing; real-time collaboration and Zed-hosted AI models require a GitHub sign-in. Pro costs $10 a month with $5 of hosted-model tokens included and further use charged at the model’s list price plus 10%. A Business plan at $30 per seat a month adds organisation controls over AI and data sharing. Zed says all AI features can be switched off, or used with your own API keys or local models instead. We verified that Zed 1.0 was released on April 29, 2026, that releases arrive weekly (1.28.1 on November 11), and that the source is licensed under GPL-3.0-or-later with some Apache-2.0 parts. Pricing, authentication, 1.0 release, releases, license
Read the full Zed analysis and sources
Its distinctive editing feature is the multibuffer: editable excerpts from different files shown together, useful when you follow references or review changes across a project. The Git panel stages individual hunks, commits and switches branches. Debugging uses the Debug Adapter Protocol, with adapters included for C, C++, Go, JavaScript, PHP, Python, Rust and TypeScript, and provided by extensions for Java, Ruby and Swift. None of this shows that Zed handles your repository faster or more accurately; we did not measure it. Multibuffers, Git, debugger
Language support combines syntax parsing with language servers for semantic features. Some languages are built in; others need an extension from Zed’s own catalog, so do not assume a VS Code extension you rely on has a Zed equivalent. Zed downloads and updates suitable language servers automatically. That reduces manual setup, but opening a new language without a network connection is not the same as opening a project whose servers are already present. Language list, language configuration
Check the hardware requirements before switching. Zed supports Windows 10 version 1903 or later and Windows 11 on x64 or Arm64 with a DirectX 11 graphics card and a current driver; macOS 12 or later fully, with macOS 10.15 and 11 partly supported; and 64-bit Linux with a Vulkan 1.3 driver and standard desktop portals. Installation and requirements
Usage metrics and crash reports are on until you turn them off in settings. Zed says the metrics include the file extensions you open, features used, project statistics and detected frameworks, but not your code. If you sign in, the random telemetry ID may be linked to your email address. Hosted services also collect metadata for rate limiting and billing. Zed opens every new folder in Restricted Mode: until you trust the folder, it does not apply the project’s own settings or install and start language servers and MCP servers for it, although tools you installed globally still run. Earlier advisories show why. One published in December 2025 described a project’s settings making Zed run arbitrary commands as a “language server”; one published in May 2026 described a crafted .git/config running a command when a folder was opened, even untrusted, fixed in version 0.227.1. Zed’s own local data has had a problem too: in September 2025 its developers wrote that database upgrades had several times deleted editor records that are the only copy of unsaved text, and they changed the upgrade process to stop it. Zed has published no security advisory since May 8, 2026 (checked November 12); its AI terminal-tool advisories from that day concern agent use, not plain editing. Telemetry, Restricted Mode, language-server advisory, Git config advisory, unsaved-text fix, advisory list
Zed Industries also launched Delta, a separate product for coding with AI agents that it calls a first step toward replacing GitHub, in public beta since September 16, 2026. That does not change the editor. We read it, with the Pro and Business plans, as a sign that the company’s revenue depends on AI and team services rather than on the free editor. Choose VS Code when a specific extension or debugger decides the project, and VSCodium if you want the same editor without Microsoft telemetry. Zed blog
Used Zed? Share your experience to help other readers choose.
Cursor
An editor built on VS Code’s open-source code that needs an account
Consider Cursor only if you want VS Code’s editing and most of its extensions in Cursor’s editor and accept a required account. Turn on Workspace Trust and Privacy Mode yourself, and keep it updated.
Reasons to choose it
- Most VS Code extensions through the Open VSX registry
- VS Code’s Source Control panel for staging and commits
- Builds for Windows, macOS and Linux, including Arm
What to watch
- You must sign in with a Cursor account to use it
- Workspace Trust off by default, per a security firm’s report
- Recent builds on Electron 42, out of support since October 19, 2026
Cursor is an editor built on VS Code’s open-source code by Anysphere, which SpaceX acquired on August 14, 2026; its pricing page, checked November 12, shows the Free plan unchanged. We added it on October 20, 2026 because, under the same fixed criteria, it scored 3.83, behind Zed (3.93), level with OpenIDEA and ahead of Kate (3.75). Its Free plan costs nothing and covers editing, with limited AI use; paid plans from $8 to $200 a month buy AI usage, and new customers now subscribe through The X Subscription, which bundles Cursor with Grok and X. You must sign in with a Cursor account to use it: Cursor’s install guide lists an account as the first requirement. Version 3.24 was listed as the latest on October 20, 2026, with builds for macOS, Windows and Linux, including Arm; Cursor publishes no minimum system versions. SpaceX acquisition, pricing, The X Subscription, install guide, downloads
For editing, it keeps VS Code’s core. The Source Control panel stages and commits, and language support comes from extensions. Cursor uses the Open VSX registry instead of Microsoft’s Marketplace and scans extensions for malware through its own proxy; it says not every Marketplace extension is listed there and publishes its own builds of some Microsoft-only ones. A user’s bug report from a September 2026 build showed VS Code extension API 1.128, while VS Code itself is at 1.142, so check that the extensions your project needs will install. Its main selling points are AI agents, chat and completions, which carry no weight for this reader. Extensions, Git, bug report, September 2026
Read the full Cursor analysis and sources
Three defaults matter before you open your own code. First, according to Oasis Security’s report (published September 10, 2025, updated May 1, 2026), Cursor ships with Workspace Trust off, so a project’s tasks set to run when its folder opens can run without a prompt; Cursor said users can switch it on. We found no Cursor page saying the default has changed, so whether it still applies to the current version is open. Second, individuals must switch on Privacy Mode themselves; it is on by default only for teams. With it off, Cursor’s data-use page (updated September 3, 2026) says it may use codebase data, prompts and editor actions to train its models, although its terms of the same date say it will not train on your content unless you have explicitly agreed. Third, a build from September 22, 2026 used Electron 42.10.0, and Electron’s security support for version 42 ended on October 19, 2026. A search-engine copy of a newer forum report shows version 3.24 on the same Electron line, but we could not read that page directly, so 3.24’s runtime is also open. The newest security advisories we read, sandbox escapes in its agent features including a critical one from June 2026, were fixed in versions 3.0 and 3.1.2. Oasis report, privacy, data use, terms, security, advisories, Electron schedule
Choose VS Code or VSCodium if you want the same editing without an account and with a supported runtime, and Zed if you want Git, multi-file editing and debugging built in without signing in.
Used Cursor? Share your experience to help other readers choose.
Kate
Also consider · a Linux desktop, opt-in telemetry
Consider Kate on a Linux desktop if KDE’s opt-in telemetry policy matters more to you than the widest extension choice, and you are happy to configure language servers yourself.
Reasons to choose it
- KDE policy: any telemetry is opt-in and off by default
- Git panel that stages, commits, pushes and pulls
- Projects, sessions and plugins without an account or subscription
What to watch
- Mac downloads are nightly builds meant for testing
- Language servers must be installed and configured separately
- Its debugger plugin expects previous GDB experience, per its manual
Kate is KDE’s free, open-source editor, with tabs, split views, multi-cursor editing, sessions and application plugins. We verified that the current release is 26.08.3, published November 5, 2026. KDE releases its applications about three times a year, and the text-editing and syntax-highlighting engines update monthly through KDE Frameworks. Linux users can install it from their distribution, Flathub or the Snap Store; Windows users from the Microsoft Store or an independent Chocolatey package. KDE application page, features, download channels
The download channel limits our recommendation to Linux. Kate’s official macOS links are nightly builds, which KDE says may be unstable and are “only recommended for testing”. On Windows, the stable route is the Microsoft Store. KDE’s application privacy policy says telemetry, where present, is opt-in and disabled by default, and warns that third-party distributors may modify the software; check how your distribution packages it. That is a documented policy advantage, not proof that every plugin, language server or packaged build never uses a network connection. Download channels, KDE application privacy policy
Read the full Kate analysis and sources
The Project plugin can build a file list from Git or from a .kateproject file, and the LSP Client plugin supplies navigation, references and other language-aware actions by talking to an external language server you install and configure. With the Project plugin on, a Git panel lets you stage and unstage files, commit (including amend and sign-off), push, pull and check out or create branches, according to Kate’s own 2023 guide. Its GDB plugin is a simple front end for GDB or any other debugger that supports the Debug Adapter Protocol, and its manual strongly recommends previous GDB experience. Projects, LSP Client, Git guide, February 2023, GDB plugin
KDE’s January 2022 advisory notes that Kate runs Git and language servers automatically when those plugins are active. It fixed a case where a program with the right name placed in a project folder could be run instead of the real tool (CVE-2022-23853, fixed in Kate 21.12.2). Our search found no Kate advisory in 2025 or 2026; that is not proof none exists. Choose VS Code if you work on a Mac or need a particular extension, and Zed if you want debugging and Git without configuring plugins. KDE advisory, January 31, 2022
Used Kate? Share your experience to help other readers choose.
Which product are we missing?
Know a product that belongs in this article? Tell us what it does differently and why it deserves a closer look. Newcomers welcome.
Readers and product teams can suggest candidates. Suggestions inform our research; they do not guarantee inclusion or a recommendation.
Opens an email draft with this article attached as a link. Nothing is sent until you send it.
No email app? Send the product name, website, and this article’s title to admin@practicalpicks.guide.
What people are saying
Public discussion is a check on vendor claims, not a measured satisfaction score. A May 2024 Sublime discussion includes appreciation for familiar editing habits and concern about aging packages. A March 2026 Kate-versus-Zed discussion contains favorable reports for both, plus a disclosed Zed employee’s opinion. A May 2026 VS Code discussion disputes speed claims and points to language-server overhead. We read these threads on September 6, 2026; Reddit blocked our automated check on October 19, so newer replies are not reflected. They are self-selected experiences, not matched benchmarks.
The March 2026 Sublime forum report about the Windows installer is a user’s claim that we have not verified; it remained the only post in the thread on October 19. Our October 19 search for incidents, security problems, ownership changes and disputes involving the four original editors found nothing beyond the items in this article that changed our conclusions, and on November 12 we found no further public dispute about any editor compared here beyond the advisories and notices cited; a search that finds nothing is not proof that nothing exists.
How we researched
This is public-source research. We did not install any editor or extension, create accounts, buy licenses, open projects or measure speed, memory, accessibility or security. No vendor supplied access, payment or input, and we use no affiliate links. We first compared VS Code, Zed, Kate and Sublime Text on September 6, 2026, added Cursor on October 20, 2026, and rechecked prices, releases, plans and security advisories for the editors compared here on November 12, 2026, when we also added VSCodium and OpenIDEA. The rest of the evidence was checked on October 19 and 20, 2026. We read vendor and project documentation, store and license pages, changelogs, GitHub release and security-advisory records, NVD vulnerability records, KDE’s security advisory and public discussions.
We wrote this for someone choosing a desktop editor for their own source projects who wants language-aware editing, Git and debugging, and would rather not pay or depend on an account. We fixed six criteria and their weights before comparing: language tooling and debugging reach (25%), local project workflow including Git (20%), cost and licensing (15%), stable platform availability (15%), data handling and project security (15%), and maintenance and continuity (10%). VS Code scored highest, 4.48 on our five-point scale, followed by VSCodium (4.00), Zed (3.93), Cursor (3.83), OpenIDEA (3.83), Kate (3.75), Kiro (3.70), GNU Emacs (3.70), Devin Desktop (3.68), Trae (3.53), Lapce (3.18), ecode (3.15) and Athas (3.10). Every one of these except Sublime Text costs nothing for ordinary editing, so price did not separate them; Sublime Text’s $99 licence could not be scored against a field of free editors, and its other criteria alone leave it below every editor above. VS Code’s lead over VSCodium is larger than the weight of any single criterion. Giving data handling much more weight on a Linux desktop favors Kate, which is why it keeps a label; on every other system, and with the weights as fixed, VS Code stayed ahead. We left out hosted IDEs, terminal editors such as Neovim and single-language IDEs such as PyCharm. We scored AI-first editors as desktop editors, giving their AI features no weight because AI is not this reader’s job. We also checked each editor’s bundled browser engine, where it has one: VS Code 1.142 ships Electron 43, which Electron supports until January 2027.
We also search for new entrants. On November 12, 2026 we repeated that search through Hacker News launch posts since November 2024, GitHub’s code-editor topic, vendor documentation and our earlier screens, and scored the newer editors that could compete under the same criteria. We counted an editor as new if its first public release was on or after November 12, 2024. Zed (a public beta in 2023) and Cursor (2023) fall before that date and stay in the comparison without an award. OpenIDEA, first released on October 22, 2026, scored highest of the newer editors (3.83), so it is our Rising Star. Other editors we scored:
- Devin Desktop (3.68), the former Windsurf from Cognition, opens on an agent dashboard and needs an account. Cognition’s security page says it may use your data for model training by default, and only paid plans can opt out. We did not consider it for the award: its latest build is based on VS Code 1.141.2, which predates the November security fixes for Workspace Trust. The earliest dated public evidence we found for the editor is a November 13, 2024 launch post, one day after our cut-off.
- Trae (3.53) comes from ByteDance and needs a login. Its privacy policy, updated January 22, 2026, says it temporarily uploads codebase files to compute search indexes and uses information to train and improve its technology, and ByteDance told The Register in July 2025 that Trae’s telemetry switch covers only the VS Code framework’s telemetry. It is the next newer editor we could recommend after OpenIDEA.
- Kiro (3.70) from Amazon is a VS Code-based editor that uses the Open VSX registry and requires a sign-in; on its free tier, content may be used for service improvement unless you opt out.
- Athas (3.10), first released in August 2025, is before version 1.0 and mostly one developer’s work.
We did not score Google Antigravity: the download its documentation offers is an agent workspace, and we found no documentation of an editor’s language, Git or debugging features. Kiro’s maker is a large company that already sells developer tools, so we do not count Kiro as a newcomer. Hyperlane, a VS Code-based editor launched in 2026, could not be assessed because we found no operator, terms or privacy pages. As of October 20 Void had been archived, Pulsar continues the Atom editor, and the other projects we found were design canvases, terminal editors, single-language tools or very early launches; Notepad++‘s Mac version is an unofficial port that its maker says is unauthorized.
The editors that do not have their own section:
- Sublime Text costs $99 once for a personal license with three years of updates; after that you keep the last version released within the three years. Build 4215 (September 25, 2026) is current. Language features come from a community package and a language server per language, Git staging and commits happen in the separate Sublime Merge, and a question about the Windows installer reported in March 2026 has had no public answer. Store, sales FAQ, download page
- GNU Emacs (3.70) is free, and version 31.1 was released on August 24, 2026. Eglot, a language-server client, and a Git-capable version-control interface are built in, and debugger front ends cover GDB, LLDB, PDB and JDB, but it needs configuration, its Windows binaries come from GNU while macOS builds come from Homebrew or a third-party site, and we did not read its telemetry or project-trust behavior, so that score is tentative. Emacs, Eglot
- Lapce (3.18) and ecode (3.15) are open-source native editors that are still before version 1.0 or release only as nightly builds; ecode’s README warns that it is not well tested on Windows.
| Tool | Public sources | What remains uncertain |
|---|---|---|
| Visual Studio Code | FAQ, license, requirements, language, extension, Git, telemetry, network, AI-settings and Workspace Trust documentation; release notes and GitHub releases; Microsoft’s security advisories, including those published November 10, 2026. | How exposed ordinary editing is between monthly security fixes; what each extension collects; how the AI features will change. |
| OpenIDEA (Rising Star) | Repository README, license, first release (October 22, 2026), the v0.1.43 release notes, security policy, advisory list and issues page. | How it behaves in practice: no independent review, no readable telemetry or privacy statement, no named maintainer or business model; whether its trusted-folder protection works as described; a plug-in interface that is still a preview. |
| VSCodium (added November 12, 2026) | Project site, README, releases and advisory page; Microsoft’s advisories for the shared source. | How quickly it ships fixes; which extensions its registry lacks; what each extension collects. |
| Zed | Pricing, authentication, telemetry, Restricted Mode, installation, language, Git, multibuffer and debugger documentation; GitHub releases, license and security advisories; Zed’s blog. | Depth of language and extension support compared with VS Code; long-term business model as the company adds AI and Delta; reliability over a stable-release record that began in April 2026. |
| Cursor (added October 20, 2026) | Pricing, install, extensions, Git, privacy, data-use, security, terms and X Subscription pages; downloads; SpaceX acquisition post; security advisories; user bug reports; Oasis Security report; Electron’s release schedule. | Whether current versions still ship with Workspace Trust off; which Electron line version 3.24 uses; how its training default and terms fit together; how many Marketplace extensions are missing. |
| Newcomer search, November 12, 2026 | Hacker News launch posts since November 2024; GitHub’s code-editor topic; pricing, changelog, setup and security or privacy pages for Devin Desktop, Trae, Athas, Kiro and Google Antigravity; Kiro’s extension-registry and authentication pages; The Register’s July 2025 report on Trae. | Independent coverage beyond launch posts; Devin Desktop’s first-build date; Trae’s behavior in practice; Hyperlane’s operator and terms. |
| Kate | KDE application page, Kate features and download pages, Project, LSP Client and GDB plugin manuals, Kate’s 2023 Git guide, KDE application privacy policy, KDE’s 2022 security advisory. | Whether the 2023 Git guide reflects every current feature; everyday Windows reliability; how each distribution packages it. |
| Sublime Text, GNU Emacs | Sublime and GNU pricing, download, plugin and documentation pages; Sublime’s changelog and forum report; NVD records. | Whether Sublime’s Windows installer still uses the reported Inno Setup version; Emacs’s telemetry and project-trust behavior. |
None of this establishes speed, memory use, accessibility or security in your environment. Next substantive review is due December 18, 2026, or sooner after a major release, price change or security event involving any of the six. Found a changed price or policy? Contact the editors.
Sources and evidence
Sources were checked October 19, 2026 unless another date is given. Vendor and project documentation establishes stated capabilities and terms, not behavior in your environment. Security advisories are the publishers’ own descriptions. Community posts are attributed opinions, not representative samples.
- Visual Studio Code: FAQ, November 12, 2026; license; requirements, updated October 14, 2026; release notes, 1.146, November 11, 2026; GitHub releases; languages; extension marketplace; Git; telemetry; AI features and how to remove them; network; Workspace Trust; security advisories, November 12, 2026, including GHSA-vmmp-977m-xvwx and GHSA-pc77-xwc5-p6jp, October 13, 2026, and GHSA-g3fj-wc2g-v3j5 and GHSA-x5cm-xmvw-73rv, November 10, 2026.
- OpenIDEA, read November 12, 2026: repository and README; security policy; advisories; issues; releases, including v0.1.0, October 22, 2026 and v0.1.43, November 12, 2026.
- VSCodium, read November 12, 2026: project site; repository and README; releases; security advisories.
- Zed: pricing, November 12, 2026; authentication; telemetry; Restricted Mode (worktree trust); installation and requirements, Windows and Linux; languages; language-server setup; Git; multibuffers; debugger; privacy and terms; 1.0 release, April 29, 2026; releases, November 12, 2026; README and license; security advisories, November 12, 2026, including GHSA-29cp-2hmh-hcxj, December 17, 2025, GHSA-fj2r-rmw6-h222, May 8, 2026 and GHSA-c99f-97vf-4h5h, May 8, 2026; Zed blog, for the 1.0, Business and Delta announcements and the March 15, 2023 beta announcement; unsaved-text fix, merged September 6, 2025. Optional AI costs are not a model-value comparison.
- Cursor, read October 20, 2026 unless dated: pricing, November 12, 2026, The X Subscription, install guide, extensions, Git, privacy, data use, security, terms, downloads, security advisories, SpaceX acquisition, August 14, 2026, a September 2026 bug report showing Electron 42 and Oasis Security’s Workspace Trust report, updated May 1, 2026; Electron’s release schedule.
- Other newer editors, read November 12, 2026: Devin Desktop pricing, getting started, changelog and security and data use; Trae pricing, downloads, privacy policy, setup guide and The Register, July 28, 2025; Athas and its advisories; Kiro pricing, data protection, authentication and extension registry; Google Antigravity pricing and getting started; Pulsar; Hyperlane; Lapce; ecode; Notepad++ for Mac, MacRumors, April 29, 2026, updated May 1. Launch dates come from Hacker News posts, such as Windsurf Editor, November 13, 2024, Trae, January 24, 2025 and Hyperlane, August 4, 2026.
- Kate: KDE application page and release dates, November 12, 2026; features; download channels, November 12, 2026; Project plugin; LSP Client; GDB plugin; Using Kate’s Git features, February 1, 2023; KDE application privacy policy; KDE security advisory, January 31, 2022.
- Sublime Text: US store, November 12, 2026; sales FAQ; EULA; download page and changelog, build 4215, September 25, 2026; platform support; projects; build systems; Git integration; community LSP package, which is that project’s documentation, not a Sublime HQ guarantee; forum report, March 11, 2026; NVD records for CVE-2025-15595 and CVE-2026-7006, September 18, 2026.
- GNU Emacs, November 12, 2026: home page, download page, Eglot manual, version control and debuggers.
- Community evidence: Reddit discussions linked under What people are saying, last read September 6, 2026.
This is a researched comparison, not a product review. Method: evidence standard, editorial picks.