zed-editor

AI-assisted editing in Zed requires enabling ACP support, configuring an ACP-compatible agent (like Claude Code) in your settings, and starting a task from the command palette to verify JSON-RPC messaging between editor and agent works end-to-end.

The Agent Client Protocol (ACP) is a JSON-RPC communication standard that enables Zed Editor to send code context, file access requests, and tool calls to AI agents over stdio, allowing real-time agent-assisted editing and cross-file collaboration.

Yes, Zed supports configuring multiple ACP-compatible agents in settings and binding them to different tasks, enabling collaborative workflows where agents share file access, terminal execution, and tool capabilities through the editor's mediation layer.

Agent endpoints and automated workflows are configured through Zed's settings file, where you specify ACP agent bindings, JSON-RPC endpoints, and task triggers; the editor then handles mediated file and terminal access for each connected agent.

An ACP-compatible agent must support JSON-RPC over stdio communication, respond to editor requests for file operations and tool execution, and accept agent configuration parameters passed from Zed settings.

Yes, ACP includes streaming progress support, allowing agents to report task status, code changes, and collaborative updates in real time as they work across multi-file projects within Zed.