Amy Duquette
4abf6ef818
# Objective Document how to use Poolside in Zed through the ACP Registry, Poolside Agent CLI, manual Custom Agent configuration, and Terminal Threads. ## Solution - Add Poolside paths to the AI by Company guide. - Document ACP Registry installation and in-thread login. - Document CLI-assisted and manual Custom Agent configuration. - Explain the settings-path and PATH requirements. - Link to the public Poolside Agent CLI repository and Poolside’s Zed documentation. ## Testing - Ran `./script/prettier`. - Ran `git diff --check`. - Verified Poolside’s live ACP Registry entry. - Verified the commands, configuration, and authentication behavior against the Poolside and Zed implementations. ## Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks are not applicable - [x] The content follows Zed’s documentation and UI conventions - [x] Code tests are not applicable to this documentation-only change - [x] Performance impact is not applicable --- 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 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.