Zed Editor v1.13.1-pre リリースZed Editor Releases v1.13.1-pre

Zed, the Rust-based code editor built for speed and real-time collaboration, has published version 1.13.1-pre, a pre-release build that adds support for a new Anthropic model and resolves several bugs affecting documentation display, language servers, and the built-in AI assistant. The update matters most to developers who depend on Zed's AI features and want early access to the latest large language models directly inside their editor, without waiting for a stable channel release.

The headline change is the addition of Claude Opus 5 support for both the Anthropic and Amazon Bedrock BYOK providers (#61606). BYOK, short for "bring your own key," lets users connect Zed to a model provider using their own API credentials rather than routing requests through a hosted intermediary. By covering both the direct Anthropic API and Amazon Bedrock, Amazon Web Services' managed service for accessing foundation models, the release gives teams flexibility in how they authenticate, where their inference traffic is processed, and how usage is billed. Organizations already standardized on AWS, for example, can keep model access within their existing Bedrock account and governance controls, while others may prefer to call Anthropic's endpoint directly.

The pre-release designation, indicated by the "-pre" suffix, signals that this build is aimed at early testers rather than the general stable audience. Zed maintains separate release channels, and pre-release versions typically surface new capabilities and fixes ahead of their promotion to the stable track. Users on this channel should expect faster iteration but also a higher chance of encountering rough edges, which is part of why bug fixes feature prominently in the notes.

Among those fixes, the update addresses an issue where hover documentation could contain too many line breaks (#61714). Hover documentation is the pop-up panel that appears when a developer points at a symbol, function, or variable, drawing on data supplied by a language server to show type signatures, descriptions, and usage details. Excess line breaks can make that information harder to scan, so the correction is a readability improvement for a frequently used feature.

The release also fixes project settings not re-enabling language servers (#61559). Language servers implement the Language Server Protocol, or LSP, an open standard that decouples language intelligence, such as autocompletion, diagnostics, and go-to-definition, from the editor itself. When project-level settings failed to re-enable a language server, developers could lose those capabilities for affected files or projects until a workaround was applied. Restoring correct behavior here matters because Zed, like most modern editors, leans heavily on LSP for its code-awareness across many languages.

A further fix targets duplicated assistant replies, where the editor's AI assistant could repeat responses. The published changelog appears to continue beyond this entry, so additional items may be listed in the full release notes. Duplicated replies clutter the conversation view and can waste tokens and time, making this a practical quality-of-life correction for anyone using Zed's agentic and chat-style AI workflows.

For context, Zed is developed by Zed Industries, whose team previously created the Atom editor and the Tree-sitter parsing library, and the project has positioned itself around GPU-accelerated performance and collaborative editing. Its steady incorporation of AI providers reflects a broader industry trend in which editors and integrated development environments increasingly compete on how well they integrate large language models. Rivals such as Cursor, a fork of Visual Studio Code oriented around AI assistance, and the Copilot features layered onto VS Code, illustrate the same direction of travel, with model choice and provider flexibility becoming key differentiators.

The BYOK approach seen here is central to that competition. By letting users bring keys for Anthropic or Bedrock, Zed avoids locking developers into a single billing relationship and lets enterprises apply their own security, compliance, and cost controls. Adding a newly released frontier model quickly, even in a pre-release build, is likely intended to keep the editor current as model vendors iterate. As always with a pre-release, users seeking maximum stability may prefer to wait for the corresponding stable version, while those wanting the newest model support and fixes can adopt 1.13.1-pre now and report any remaining issues back to the project.