Zed reaches 1.0 stable with paid teams tier

Zed shipped 1.0 this week. The features themselves aren’t dramatic — Zed has been usable for over a year — but the framing is. The 1.0 designation comes with stability commitments and a paid teams tier, signaling Zed’s transition from “interesting alternative” to “production tool.”

What 1.0 means

The release explicitly commits to:

API stability for extensions. Extension developers can build against 1.0 APIs with confidence they won’t break.
Format stability for project settings, themes, and keybindings. Configurations from 1.0 will work in future versions.
Performance baselines. No regressions on the documented performance metrics in future minor releases.
Channel transparency. Stable channel for production use; beta and dev channels for early access to changes.

This is the kind of commitment that lets organizations adopt the tool in a serious way. Pre-1.0, “this might break next month” was a real concern.

The teams tier

A paid Zed for Teams tier is now generally available:

$15/user/month (annual billing, less if monthly)
Includes the editor at no charge
Adds: shared channels, audit logs, SSO, admin controls, priority support

The free tier (the editor itself) remains fully featured for individual use. The teams tier is for organizations that need governance and collaboration features.

Zed’s collaboration capabilities are differentiated. The shared channels (real-time multi-user editing, shared terminals, voice chat) work better than equivalent features in other editors. The teams tier productizes these.

Why this is interesting

The competitive landscape:

Cursor is positioned as “VS Code with AI.” Strong individual experience; teams features improving but not the differentiator.
JetBrains has strong IDE features and team licensing; AI is a recent addition.
Copilot is GitHub’s distribution; the editor is incidental.

Zed is positioning around collaboration. The bet: as engineering teams use AI tools heavily, the collaboration story matters as much as the individual one. Two engineers pairing on a problem with AI assistance is a workflow that’s awkward in most editors. Zed’s making it native.

If the bet pays off, Zed has a real wedge in team-sized adoption. The individual differentiation (speed, native AI panel, vim mode) gets you in; the team differentiation (collaboration) keeps you.

What 1.0 doesn’t fix

Some limitations remain:

Extension ecosystem is small. Compared to VS Code’s marketplace, Zed’s is sparse. Many useful third-party tools aren’t available.
Windows support is still beta. Linux and Mac are stable; Windows users are on the secondary path.
Some language servers have rough edges. The polished languages (Rust, Go, TypeScript, Python) are great. Niche languages have less polish.
No graphical debugger. Zed’s debugger is improving but covers fewer languages with less depth than VS Code’s or JetBrains’.

These are real for some users. For users where the strengths outweigh the gaps, 1.0 is a strong product.

What I’d watch for

A few things to track in the next year:

Extension ecosystem growth. Whether developers commit to building Zed extensions in numbers. The WASM model has tradeoffs; whether the ecosystem grows determines if those tradeoffs are net positive.

Team adoption. Whether Zed’s collaboration features attract real team adoption beyond the early-adopter audience. The teams tier is the test.

AI feature pace. Cursor and Copilot are setting the pace on AI features. Zed is competitive but not leading. Whether Zed’s team can keep pace matters.

Stability of the stable channel. The 1.0 commitment requires not breaking things. The early test will be how well the team handles the tension between stability commitments and continued rapid development.

Worth trying?

If you’ve tried Zed before and bounced because of stability concerns, 1.0 is the right time to reconsider. The product is more mature; the commitments are real; the rough edges that existed are mostly polished.

If you’ve never tried Zed, the install is free and the trial is fast. An hour with Zed will tell you whether the editor’s strengths fit your workflow.

For teams considering an editor change, 1.0 + the teams tier is the version of Zed that’s enterprise-credible. The collaboration features may matter more than the AI features for some teams; Zed is differentiated on both axes.

The category implications

Zed reaching 1.0 stable is a marker. The “AI editor” category now has multiple credible production tools. Cursor, JetBrains, Zed, and (with Copilot) VS Code all clear the bar for serious team use.

The decision is increasingly about fit, not capability. All these tools can handle the basics. The differentiation is in workflow, IDE features, team collaboration, language support, and integration with the rest of your stack.

For a team picking an editor in 2026, the category is now mature enough to make a careful evaluation. The wrong choice is recoverable; the right choice produces meaningful productivity over the long run. Take the evaluation seriously rather than picking by reputation.