CodeEdit is a native macOS code editor built entirely in Swift and SwiftUI, designed from the ground up to feel at home on the Mac rather than being a cross-platform app retrofitted onto it.
What is CodeEdit?
CodeEdit is an open-source, fully native Mac code editor that embraces AppKit and SwiftUI conventions instead of wrapping a web engine — making it feel snappier and more cohesive than Electron-based rivals. It is community-driven and actively developed on GitHub, with a growing contributor base pushing toward feature parity with mainstream editors.
The project was born from a simple frustration that every popular code editor on the Mac — VS Code, Atom (RIP), Zed aside — ships as a heavyweight browser in disguise. CodeEdit bets that a true AppKit/SwiftUI editor can be faster to launch, lighter on RAM, and better integrated with macOS system features like native menus, window management, and accessibility APIs.
What does CodeEdit do best?
CodeEdit's strongest suit is raw Mac-nativeness: it launches in under a second, respects system accent colours, integrates with macOS spell-check and text substitutions, and sits lightly in memory even with a sizeable project open.
- Native performance: no Chromium runtime means far lower idle RAM than VS Code or Fleet.
- SwiftUI interface: every panel, tab, and inspector is built with the same toolkit Apple uses — animations feel right, window tiling works, Stage Manager behaves.
- Source Control panel: a visual git log, branch switcher, and staged-changes view built in, without an extension.
- LSP support: Language Server Protocol integration means syntax highlighting and code completion for most languages without manual configuration.
- Extensible via plugins: a plugin architecture is under active development, aiming to match VS Code's ecosystem reach while keeping the core binary lean.
Is CodeEdit free?
Yes — CodeEdit is completely free to download and use, and the entire source is open on GitHub under the MIT licence. There are no paid tiers, subscription prompts, or telemetry paywalls.
Because it is community-funded rather than venture-backed, the pace of feature delivery depends on volunteer contributors. If you rely on it daily, the project welcomes sponsorship on GitHub to keep core maintainers motivated. That said, nothing is locked behind a paywall now or on the roadmap.
Who should use CodeEdit?
CodeEdit is ideal for Mac-first developers who are fatigued by the memory appetite and un-Mac feel of VS Code but are not ready to pay for a commercial alternative like Nova or Sublime Text.
Front-end developers, Swift/iOS developers, and hobbyists working in Python or Ruby will find the current feature set more than sufficient for day-to-day editing. If your workflow depends on a rich marketplace of VS Code extensions — complex debugger adapters, remote SSH editing, or Jupyter notebook rendering — CodeEdit is not there yet and you will feel the gaps. Think of it as the editor to watch, not necessarily the editor to switch to cold-turkey in production today.
What are the best CodeEdit alternatives?
The closest native Mac alternative is Nova by Panic, which is polished and paid (one-time licence). Zed is another Rust-native editor with excellent performance but is cross-platform and more opinionated about its collaboration model. Sublime Text remains a beloved lightweight option with a mature plugin ecosystem. If extension compatibility is non-negotiable, VS Code is still the pragmatic choice despite its Electron underpinnings. For Apple-platform development specifically, Xcode obviously owns the full iOS/macOS toolchain, but it is not a general-purpose editor. CodeEdit sits in the sweet spot between Sublime's minimalism and VS Code's maximalism — assuming you are comfortable riding a fast-moving open-source project.
How does CodeEdit compare to VS Code?
VS Code wins on extension breadth, remote development, and battle-tested stability — it has a decade of polish and a Microsoft-sized team behind it. CodeEdit wins on launch time, memory footprint, and the feeling that it actually belongs on a Mac.
In practice I have found CodeEdit uses roughly a quarter of the RAM that VS Code claims for an identical mid-size TypeScript project. The tab bar, file tree, and command palette all respond with a crispness that Electron simply cannot match. The trade-off is real though: if you need GitLens-level blame annotations, a Copilot inline-completion widget, or a Docker extension, CodeEdit cannot serve you today. Watch the GitHub milestones — each release closes that gap meaningfully.
