Code editors
Programs for writing code that pair a fast text core with language servers, debug adapters, extensions and, now, built-in agents.
How they work
A code editor keeps files in memory, highlights and edits them, and leans on helpers for knowledge about each language: language servers over LSP for completion, diagnostics and navigation, and debug adapters over DAP for breakpoints and stepping. Extensions add languages, themes and tools, and remote development runs those helpers on another machine while the UI stays local.
The field splits three ways. Visual Studio Code is the default: 70.9% of the 13,193 people who answered the Stack Overflow 2026 survey question used it regularly. Cursor and Windsurf (now Devin Desktop) are forks of its open-source base with agents built in. Zed is written from scratch in Rust, draws on the GPU and hosts outside agents through the Agent Client Protocol.
Pick by ecosystem first. A VS Code fork keeps most extensions but installs them from Open VSX rather than Microsoft’s Marketplace, and loses Microsoft-only pieces such as Remote - SSH. An editor written from scratch, such as Zed, gets languages and debuggers through LSP and DAP, but needs its own extensions for everything else.
Technologies
What all editors and terminals have in common →| Open source | Microsoft | MIT (Code - OSS source); Microsoft product licence for the VS Code build | 2026-10-09 | |
| Open source | Zed Industries | GPL 3 (editor), AGPL 3 (server components), Apache 2.0 (GPUI) | 2026-10-09 |
Sources
- Language Server Protocol: Overview
- Debug Adapter Protocol: Overview
- VS Code docs: Remote Development overview
- Stack Overflow Developer Survey 2026: Technology, Dev IDEs
- Eclipse Open VSX: README
- Zed blog: Bring Your Own Agent to Zed, introducing the Agent Client Protocol (Aug 2025)
- VS Code wiki: Differences between the repository and Visual Studio Code