morgankrey
5fb1e6d1a4
## Summary - Add a new "Configuration Boundaries" section to the external agents documentation explaining what settings are shared between Zed and ACP agents - Clarify bidirectional configuration story: what Zed forwards to agents AND what agents inherit from native installations - Add troubleshooting section for common user confusion points - Update MCP docs with clearer cross-links ## Context Users are confused about which Zed settings apply to external ACP agents like Claude and Codex. Common questions: - "I configured MCP in Zed but Claude can't see it" - "My Codex config.toml isn't being used" - "Do profiles apply to external agents?" ## Key Points **What Zed forwards to ACP agents:** - Model/mode selection, env vars, MCP servers (with limitations), CLAUDE.md **What's NOT forwarded:** - Profiles, tool permissions settings, `.rules` files **What agents DON'T inherit from native installations:** - `~/.claude/` config, `~/.codex/config.toml`, native MCP servers, authentication state ## Test plan - [x] Review for technical accuracy against codebase - [x] Check brand voice compliance Release Notes: - N/A
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 issue)
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
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.