Zed Editor v1.5.5 リリースZed Editor Releases v1.5.5

Zed Editor has shipped version 1.5.5, a point release that broadens the editor's support for Anthropic's Claude models and corrects a defect in its Git repository handling. The update is incremental rather than sweeping, but it touches two areas that have become central to the way many developers work inside modern code editors: AI-assisted coding and version control.

The headline change is the addition of Claude Fable 5 to Zed's Anthropic provider under its bring-your-own-key, or BYOK, configuration. BYOK lets users supply their own API credentials directly to the editor, so that requests to the model are billed through the developer's personal or organizational Anthropic account rather than routed through a Zed-managed subscription or proxy. By exposing Claude Fable 5 as a selectable option, Zed allows users who already have access to the model to point the editor's assistant, inline completions, and related AI features at it without waiting for a deeper platform integration. For teams with existing Anthropic contracts, this approach also keeps usage and spending within their own billing and governance controls.

The BYOK model has become a common pattern across AI-enabled editors, in part because it sidesteps the cost and complexity of bundling model access into a product subscription. It also gives users flexibility to switch between providers and model versions as new releases appear. Anthropic's Claude family is frequently offered alongside models from other vendors in these integrations, and adding a newer model variant is typically a matter of registering its identifier and any associated parameters rather than re-architecting the provider. That makes incremental additions like this one relatively low-risk, while still giving users early access to capabilities the newer model may offer.

The second notable change in v1.5.5 is a bug fix affecting Git repositories. In prior builds, clicking the trust button for a repository reportedly had no effect, leaving users unable to complete the action through the interface. Repository trust prompts are a security-oriented mechanism: editors increasingly ask users to confirm that they trust a project's source before enabling features that could execute code or read sensitive configuration, a concept popularized by workspace trust in other editors. When such a control fails to respond, it can block the intended workflow and create confusion about whether the repository is actually trusted. Restoring the button's functionality removes that friction and ensures the trust state can be set as designed.

For readers less familiar with the project, Zed is a high-performance, multiplayer-capable code editor built largely in Rust and developed by Zed Industries, a team that includes several people behind the earlier Atom editor. Zed emphasizes low latency and GPU-accelerated rendering, and over successive releases it has steadily layered in collaborative editing, language server support, an integrated terminal, native Git tooling, and an AI assistant. The editor is positioned in a competitive segment that includes Visual Studio Code and AI-forward tools such as Cursor, where the integration of large language models directly into the editing surface has become a key point of differentiation.

The combination of an AI provider update and a Git interface fix in a single patch reflects how tightly these capabilities are now woven into everyday editing. Version control trust dialogs and model selection menus sit close together in the modern editor's surface, and both need to behave reliably for the overall experience to feel dependable. A release of this kind appears aimed at keeping the editor current with the latest model availability while resolving small but disruptive interface regressions before they accumulate.

Users running earlier versions can typically obtain the update through Zed's built-in auto-update mechanism or by downloading the latest build from the project's distribution channels. Those who intend to use Claude Fable 5 will need a valid Anthropic API key and should confirm that their account has access to the model, since BYOK configurations depend on the credentials and entitlements tied to the user's own provider account rather than anything bundled with the editor. As with any point release, reviewing the published release notes is advisable to confirm the full list of changes and any version-specific requirements.