Theia IDE

The deciding trait is that the bill is yours. You supply a key or point it at a model you host, so the cost of the agent tracks what you actually asked it to do rather than a monthly figure someone else chose. For anyone who has watched an included-request allowance evaporate mid-refactor, that is a different relationship with the tool.

What you give up is the polish that money buys, in responsiveness and in defaults. Pick it if you want control and no invoice. Pick Zed if you would rather it just felt fast.

The gap is the registry. Extension compatibility is real, but the catalogue it draws from is smaller and differently populated than the one most developers know, and several widely used extensions are absent or lag behind because their publishers do not target it. Nobody discovers this during a demo. They discover it on day three, when a required debugger is missing.

What it does right is naming the agents. Coder, Architect and the rest are separate documented units, so a user knows which one answered and can disable the ones they distrust.

1. Routing is a design decision made visible. A dedicated agent selects among named specialists, so the attribution question, which component produced this answer, has an answer, and a user can correct a bad route rather than rewriting a system prompt. 2. Separating the framework from the product built on it means the architecture is reusable outside this editor, which is a strong signal that the boundaries are real.

2. No evaluation is published and no capability claim needs one, since the product asserts structure rather than performance.

The governance is the product feature. A neutral foundation holding the project means no investor needs an exit, no acquirer can redirect the roadmap, and the commercial parties contributing do so because they ship products on top of it. That converts the usual eighteen-month question into a question about contributor interest, which is slower and more legible.

Moat: neutrality, which attracts exactly the vendors who refuse to depend on a competitor. Likely path: continued incremental release, funded by the companies embedding it. Position: the safest longevity bet in this category, and priced accordingly at nothing.

Financially this is the easiest approval of the quarter: nothing per seat, and inference billed to an account we already reconcile. The open licence means legal review is a formality rather than a negotiation.

Operationally it is sixty independent installations. There is no administrative console, so model configuration, key distribution and version drift are all mine to solve with the tooling I already use for desktops. It does not execute unattended, so it never becomes a measurable pipeline step. Approved with conditions: managed deployment, and keys issued centrally rather than by developers.

Editable prompt templates are the feature I keep asking every vendor for and almost nobody ships. When an agent behaves stupidly here I open the template and fix it, instead of filing an issue and waiting two releases. That single capability changes the tool from something I use into something I maintain.

Two local serving options are documented by name, MCP servers attach, and the licence keeps a fork viable indefinitely. This is the most configurable editor on the board and it is not close.