Why Atlarix Is a Desktop App, Not an Editor Extension
The first question developers ask about Atlarix is usually: why isn't this an editor extension? Most AI coding tools ship as editor forks or plugins. We built Atlarix as a standalone desktop app instead — and the reasons are about capability, not preference. Atlarix is a workstation that sits beside whatever editor you already use, not a replacement for it.
Local models need a real runtime
Atlarix is built for the open-weight frontier and for local execution — Ollama, LM Studio, Hugging Face, or any BYOK provider. Managing local inference alongside bundled ripgrep search, background services, and parallel writer sub-agents needs real process management. Electron gives us a full Node.js runtime with IPC between main and renderer — background services, child processes, long-running work — without fighting an extension host's sandbox.
The approval queue needs full UI control
Every file write in Atlarix surfaces an inline diff approval — a preview where you accept or reject individual hunks, with allow-once / always-allow decisions scoped to the workspace. Commands run inside a per-OS write sandbox — macOS Seatbelt, Linux Landlock, Windows AppContainer — that confines what they can write, with only genuinely dangerous ones stopping to ask. Building that as a reliable, non-intrusive surface inside a webview is genuinely hard; as a desktop app we own the window, the layout, and the interaction flow.
A workstation, not a panel
Atlarix bundles the things a coding session actually needs around the agent: an in-app browser the agent can drive (navigate, snapshot, click, fill), real interactive terminal tabs that persist across restarts, a live preview, and MCP server management — all in one window. That's a workstation. A sidebar in someone else's editor can't host it without permanent compromise.
Data stays local by design
Workspace memory, session history, and your keys live in SQLite and local files on your machine — there's no index of any kind uploaded to a vector service, and BYOK requests can go straight to your provider. For proprietary codebases or regulated work, "runs on your machine" is verifiable rather than a marketing line, and it's easier to guarantee as a desktop app than as a cloud-synced extension.
Editor-agnostic on purpose
Because Atlarix is its own app, it works regardless of your editor — Vim, Neovim, JetBrains, Zed, VS Code, or plain terminal. You keep your setup and run Atlarix alongside it. We don't ask you to switch editors to get an agent, and you're not locked into a fork that has to track upstream forever.
The extension model optimizes for distribution. The desktop model optimizes for capability — a real runtime for local models, full control over the approval queue and sandbox, a browser and terminal around the agent, and a local-by-design data path. For an open-weight, local-first harness, capability wins.