Files
cline/docs/cline-cli/acp.mdx
T
Arafatkatze 40191c28e4 feat: add ACP server integration for Zed and custom clients
- Add ACP (Agent Client Protocol) stdio server at dist-standalone/cline-acp.js
- Implement ACP session management with tool call notifications and message conversion
- Create standalone build configuration with esbuild for ACP entrypoint
- Add message-to-ACP notification conversion for text, reasoning, and tool calls
- Support workspace context and MCP server forwarding from ACP clients
- Add documentation for building, running, and connecting to Zed editor
2026-01-12 14:51:11 -08:00

75 lines
1.9 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
title: "ACP Integration (Zed + Custom Clients)"
description: "Run Cline as an Agent Client Protocol (ACP) server and connect it to Zed or any ACP-compatible client."
---
## Overview
Cline ships an ACP-compatible stdio server so you can run it inside editors like Zed or any client that speaks the Agent Client Protocol.
The ACP entrypoint lives at `dist-standalone/cline-acp.js` after building the standalone bundle.
## Build the ACP server
From the Cline repo root:
```bash
npm install
npm run compile-standalone
```
The ACP server will be available at:
```text
dist-standalone/cline-acp.js
```
## Run manually
```bash
node dist-standalone/cline-acp.js --config ~/.cline
```
Notes:
- `--config` sets the Cline data directory (same as `CLINE_DIR`). If omitted, Cline defaults to `~/.cline`.
- Logs go to stderr to keep ACP JSON-RPC traffic clean on stdout.
## Connect to Zed
Add a custom ACP agent to your Zed `settings.json` (open with `zed: open settings`):
```json [settings]
{
"agent_servers": {
"Cline (ACP)": {
"type": "custom",
"command": "node",
"args": [
"/absolute/path/to/cline/dist-standalone/cline-acp.js",
"--config",
"/absolute/path/to/.cline"
],
"env": {}
}
}
}
```
Then open the Agent Panel in Zed and start a new thread for **Cline (ACP)**.
Zed will:
- Provide the workspace `cwd` for each session.
- Forward MCP servers you configured in Zed to Cline over ACP.
## Limitations
- Cline currently supports one ACP session at a time; starting a new session closes the previous one.
- Some Cline UI affordances (like special buttons for "start new task") are represented as standard prompts in ACP clients.
## Troubleshooting
- Check Zeds ACP logs (`Help` → `Open ACP Logs`) if the agent fails to start.
- Ensure the path to `cline-acp.js` is absolute and your Node binary is on `PATH`.