Zed Editor v0.40.4-rc2 Released: Usage Credits Now Available Without Upgrading

Open-source code editor Zed has released the v0.40.4-rc2 release candidate. The core change in this update is allowing users to use usage credits to access AI features without upgrading to a paid plan. For developers who want to try out AI capabilities before committing to a purchase, this lowers the barrier to entry.

What This Update Changes

According to the GitHub commit history, v0.40.4-rc2 corresponds to commit 45e6011, tagged by team member ParthSareen on October 13, 2025. The release notes contain only one clear change entry: launch: allow usage credits without upgrading (#18985).

This change literally means: during the launch phase, usage credits are allowed to be consumed without forcing users to first upgrade to a paid plan. In other words, Zed has relaxed the prerequisites for accessing AI features, allowing free-tier users to use AI-related services by consuming credits rather than being blocked by an upgrade prompt.

The commit itself is verified with a GitHub-verified signature (GPG key ID: B5690EEEBB952194), confirming it as an official release candidate.

Release Candidate (RC) is a stage in the software release process: features are frozen, major bugs are fixed, but it hasn't yet been officially released as a stable version. RC versions are typically released first to users willing to validate early, in order to catch the last batch of regression issues before the official release. The rc2 in v0.40.4-rc2 indicates this is the second candidate iteration of the same version, meaning rc1 may have already exposed issues that needed patching. Therefore, RC versions can be installed and used, but are not recommended as the sole dependency for production environments—they are better suited for developers who want to evaluate new behavior ahead of time.

GPG signature verification is a common method for open-source projects to ensure the credibility of commit sources. GitHub marks commits with Verified, indicating that the commit was signed by someone holding the corresponding private key, matching the public key registered on the platform. The GPG key ID: B5690EEEBB952194 mentioned in this article is one such identity credential. It doesn't guarantee code quality by itself, but it confirms that the change genuinely came from an official project member rather than a forged third-party commit—this layer of source verification is especially important for changes that touch payment and credit logic.

Why This Change Is Worth Noting

Zed is a code editor that has generated significant discussion in the developer community over the past two years, known for its high-performance UI rendering and native collaboration capabilities, with AI features being an important direction for its productization. Previously, AI capabilities were often tied to paid upgrades, which to some extent limited new users' perception of the core selling points.

Decoupling "usage credits" from "paid upgrades" is essentially a product strategy to lower the cost of trying things out. Users can first consume their existing usage credits to evaluate Zed's AI editing experience, then decide whether to convert to a paid user. For a product that needs to compete head-on with the data-intensive VS Code ecosystem, this strategic adjustment is more practical than simply stacking features.

Compared with similar products, this approach also aligns with the "free credits + pay-as-you-go" model commonly adopted by current AI programming tools.

Usage credits are a common billing abstraction in AI products: users are deducted credits based on tokens consumed or number of requests, rather than being directly bound to a fixed subscription tier. It separates "can I use it" from "am I a paid user" into two things—free or low-tier users can make calls as long as they have credits remaining, and can choose to top up or upgrade once depleted. Zed's change essentially makes credits an independent pass separate from paid plans, consistent with the "free credits + pay-as-you-go" approach of tools like Cursor and GitHub Copilot, and also means users don't have to bear subscription costs upfront during the evaluation phase.

Version Positioning and Cadence

rc2 indicates this is a release candidate version, used for final validation before the official release. Version number v0.40.4 belongs to the 0.40.x iteration line as a minor patch, primarily carrying small-scale changes rather than a large feature set.

Looking at the release cadence, Zed maintains a high iteration frequency. This release carries only one change note, which is typical of a minor patch. For developers already using Zed, the practical benefit of this version centers on a smoother trial path for AI features, rather than major changes to the editing experience itself.

Who Should Pay Attention

If you've been watching Zed's AI programming capabilities but didn't want to pay just to try them out, this release candidate provides a more direct evaluation entry point. If you already use Zed but have never enabled AI features, you can now use your existing credits to try it directly, then judge whether it's worth a long-term commitment.

Note that as a release candidate, stability may not match the official release. When using in production environments, it's advisable to watch for subsequent official release announcements.

How to Get It

Zed releases are published on the GitHub repository's tags page. The v0.40.4-rc2 tag is already visible, and users can obtain it through regular version update channels. For specific installation and update methods, refer to the official release notes.