Tom Houlé
3d058c4069
When a Zed Business organization hits its token spend limit, the agent panel told the user to "check that your API key has access to this model", and did not display the error message returned by the server. The message about checking your API key was the generic 401 and 403 error for all language model providers. This is also incorrect in general since there are no API keys involved in the Zed and ChatGPT Subscription providers. So this commit changes the message for authentication errors (401s) to be provider-specific, with the current message about invalid API key as the default, and overrides for the providers that don't use API keys. And the authorization error messages (403s) now include the server error message. So the spend-limit case now reads "Permission Denied — Token-based spending limit reached." instead of talking about API keys. <img width="1888" height="426" alt="grafik" src="https://github.com/user-attachments/assets/cf9e07cd-66f0-4f8d-828c-79b875edcf2d" /> Telemetry event names (`invalid_api_key`, `no_api_key`) are kept unchanged to avoid breaking existing dashboards. Release Notes: - Fixed agent panel errors telling users to check their API key when the provider doesn't use one (Zed account, ChatGPT subscription). Permission errors also now show the provider's actual message.
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).
Other platforms are not yet available:
- Web (tracking discussion)
Developing Zed
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
Zed source code is licensed primarily under GPL-3.0-or-later, with Apache-2.0 components where marked.
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.
Sponsorship
Zed is developed by Zed Industries, Inc., a for-profit company.
If you’d like to financially support the project, you can do so via GitHub Sponsors. Sponsorships go directly to Zed Industries and are used as general company revenue. There are no perks or entitlements associated with sponsorship.