Thanks for the request. Zed support makes sense as part of the broader cross-harness adapter work.

The important bits I would want to verify before calling it supported are:

• where Zed expects project/user rules or assistant context to live;
• whether a .zed/ profile should be project-local, user-local, or both;
• how BYOK/OpenRouter configuration is referenced without copying keys into the repo;
• which ECC surfaces should load by default versus stay opt-in.

I am tracking this as an adapter-roadmap item for ECC 2.0. If you have a working .zed/ layout or a minimal example of what Zed reads today, please drop it here and it will make the implementation much more precise.

Update: Zed support is now implemented on main.

ECC now has a conservative zed install target for project-local .zed/ settings. The minimal profile plans the Zed adapter, writes ECC-managed files under .zed/, includes .zed/settings.json, and deliberately keeps BYOK/OpenRouter credentials out of the repo. Those should stay in Zed account/user settings or your local secret store.

You can preview it from the repo with:

./install.sh --profile minimal --target zed --dry-run

After the next package release, the equivalent npm path will be:

npx ecc install --profile minimal --target zed --dry-run

This is covered in the README Zed section and the full CI matrix is green across macOS, Linux, and Windows. Thanks for pushing on this adapter; it fit directly into the ECC 2.0 cross-harness work.

Update from the ECC side: Zed is now represented in the cross-harness evidence work rather than being left as an untracked request.

What has landed so far:

• ECC Tools can classify Zed as a supported harness evidence source.
• Zed-related config/context artifacts can be attached to hosted harness analysis without treating .zed/ as a secret store.
• The implementation keeps BYOK/provider credentials out of the evidence surface and focuses on inspectable setup metadata.

Boundary: this does not mean ECC should blindly install or overwrite a project .zed/ folder. The safer adapter path is still generated/reviewable project-local files plus clear user-local setup notes. If someone has a minimal real-world .zed/ layout that works well today, please drop it here; that is the best input for the next adapter pass.