Zed+Claude Code/GLM Code & ACP Overview: You need to KNOW ABOUT THIS!

Key Concepts:

1. Introduction and Overview

The video discusses Zed's new Claude Code integration and the expanded Agent Client Protocol (ACP).
The ACP aims to make agent integrations more accessible and easier to understand.

2. Gemini CLI Integration

Zed previously launched a Gemini CLI integration in collaboration with Google.
This integration provided first-class, official support for Gemini CLI within Zed.
The Gemini CLI agent was integrated into Zed's agent panel, offering a graphical interface while retaining its original capabilities.

3. Agent Client Protocol (ACP)

ACP allows agents like Gemini CLI and Claude Code to seamlessly integrate with interfaces like Zed.
Developers only need to support ACP for their tools to be compatible with any interface that also supports ACP.
The Zed team and contributors used ACP to integrate Claude Code into Zed's agent panel.

4. Claude Code Integration in Zed

The integration allows users to run Claude Code as a first-class citizen within Zed's high-performance editor, rather than just in a terminal.
The "follow-along" feature enables users to observe edits across multiple files with full syntax highlighting and language server support.
Users can review and approve granular changes, unlike the all-or-nothing approach in the terminal-based Claude Code.
Claude Code's task list can be anchored in the sidebar for constant visibility.
Claude Code slash commands are seamlessly integrated, allowing users to use custom workflows.

5. ACP Adoption and Benefits

Code Companion in NeoVim also supports ACP.
The speaker hopes more editors will support ACP, enabling users to use the best agent for their task without compromising on their editor of choice.
ACP documentation is available from the Zed team.
ACP uses JSON RPC and reuses MCP types to avoid redundant data type representations.

6. ACP Technical Details

The agent runs in the background and interfaces with the editor based on the ACP protocol.
The editor provides the agent with context about files and MCP servers.
The agent requires user approval for tool calls.
MCP settings are inherited by the agents.
For editor-provided tools (e.g., linting, language server checks), the editor creates an MCP proxy to integrate these tools into an MCP server.
The MCP proxy acts as a relayer, while the actual tool resides within the editor.

7. Demonstration of Claude Code Integration in Zed

In Zed's agent panel, users can add the Claude Code agent.
Files can be mentioned using the "@" symbol, and slash commands can be accessed via the slash option.
The "follow" option allows users to monitor Claude Code's progress.
The agent prompts for approval of tool calls.
New agents can be added via the settings, similar to configuring MCP.

8. Benefits and Use Cases

ACP streamlines agent integrations.
The ability to integrate various editors (JetBrains, Zed, VS Code) with the same agent is highlighted.
This is particularly useful for enterprise teams using different editors but requiring the same agent for specific tasks.
The Claude Code integration is beneficial for Zed users who prefer a graphical interface over the terminal.
GLM coding plans with Claude Code are supported, requiring proper setup in the Claude Code settings file.

9. Future Improvements

The Zed team is working on displaying the model being used in the interface, pending Claude Code SDK capabilities.

10. Conclusion

The speaker expresses enthusiasm for the ACP and Claude Code integration in Zed.
The integration offers a seamless and high-performance experience for Claude Code users within the Zed editor.
The ACP has the potential to revolutionize agent integrations across different editors and tools.