Why the IDE Had to Be Reinvented

Thirty years of one person and one file

The integrated development environment we know was designed around a simple unit of work: a person editing a file. Everything the editor is good at — syntax highlighting, autocomplete, go-to-definition, a gutter of red squiggles — optimizes that one loop. It is a quiet, beautifully tuned place for a single typist.

VS Code perfected it. It became the default home for a generation of developers because it made that loop frictionless.

The first response to agents was a fork

Then models got good enough to write code, and the obvious move was to bring them into the place we already lived. Cursor did exactly that — a fork of VS Code with an agent bolted on. Tab to complete, Cmd+K to edit, or hand the whole task to an agent that reads the repo and iterates.

It was a genuine leap, and it made agents feel native. But notice what stayed fixed: the editor was still the center of gravity, and the agent was a guest in a house built for a single typist.

The unit of work changed

Here is the thing a fork can't absorb: the unit of work is no longer a file. It's a fleet.

When you're conducting several agents at once — one refactoring, one writing tests, one reviewing, one waiting on your approval to spawn a fifth — the questions that matter aren't "where's my cursor" and "what's on this line." They're durability (does this survive a reboot?), messaging (can these agents talk to each other?), approval (who signed off on that spawn?), and orchestration (who's routing the work?).

None of those are editor features. They're workspace primitives. Bolting them onto a file editor is like bolting a control tower onto a single-seat cockpit.

What a base layer is

So nala isn't a better editor, and it isn't a fork. It's a base layer: a workspace rebuilt from the terminal up, where durable panes, Tasks, messages, and approvals are first-class citizens — the things a fleet of agents actually needs.

• Durable terminal panes that survive reboots, held by a detached daemon
• Agent-to-agent messaging, with Off / Connect / Orchestrate modes
• Spawn safety: no agent mints another without your single-use approval
• One resident nala agent that routes work across every model and agent you bring

Not a nicer editor — a different center

The editor doesn't disappear; it becomes one pane among many. The center of gravity moves from the file to the fleet. That's the reinvention — and it's why it had to be built from the ground up rather than forked from what came before.

nala is free, local-first, and runs the models and agents you already use. If the last decade was about making the editor smarter, the next is about giving your agents a place to actually work.