acp-editor-integrations.mdx 6.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216
  1. ---
  2. title: "ACP: Editor Integrations"
  3. description: "Use Cline in JetBrains, Neovim, Zed, and other editors via the Agent Client Protocol"
  4. ---
  5. Cline CLI supports the [Agent Client Protocol (ACP)](https://agentclientprotocol.com/), an open standard that enables AI coding agents to work across different editors and IDEs. This means you can use the full Cline agent—with all its capabilities including Skills, Hooks, and MCP integrations—in your preferred development environment.
  6. ## Why ACP?
  7. - **Editor flexibility**: Use Cline in JetBrains, Neovim, Zed, or any ACP-compatible editor
  8. - **No feature compromises**: Full access to Cline's capabilities regardless of editor
  9. - **Team consistency**: Same AI assistant across different developer workflows
  10. - **Open standard**: Built on Zed's open Agent Client Protocol specification
  11. ## JetBrains IDEs
  12. [JetBrains](https://www.jetbrains.com) IDEs include IntelliJ IDEA, PyCharm, WebStorm, and more. They offer built-in AI Assistant with ACP support.
  13. <Note>
  14. **Recommended: Native JetBrains Plugin**
  15. For the best JetBrains experience, install the [native Cline plugin](/getting-started/installing-cline#jetbrains-ides) from the JetBrains Marketplace. It provides full IDE integration and the complete Cline experience.
  16. The ACP setup below is an alternative way to use Cline CLI features in JetBrains IDEs.
  17. </Note>
  18. Alternatively, you can run Cline CLI in IntelliJ IDEA, PyCharm, WebStorm, and all other JetBrains IDEs through their built-in AI Assistant with ACP support.
  19. <video
  20. src="https://storage.googleapis.com/cline_public_images/cline-acp-jetbrains.mp4"
  21. autoPlay
  22. loop
  23. muted
  24. playsInline
  25. style={{ width: "100%", borderRadius: "8px", marginTop: "16px", marginBottom: "16px" }}
  26. />
  27. ### Setup
  28. 1. **Install Cline CLI** (if not already installed):
  29. ```bash
  30. npm i -g cline
  31. ```
  32. 2. **Authenticate with Cline**:
  33. ```bash
  34. cline auth
  35. ```
  36. 3. **Configure JetBrains AI Assistant**:
  37. - Open your JetBrains IDE
  38. - Navigate to `Settings | Tools | AI Assistant | Agents`
  39. - Click "Add Custom Agent"
  40. - This opens/creates `~/.jetbrains/acp.json`
  41. 4. **Add Cline to `acp.json`**:
  42. ```json
  43. {
  44. "agent_servers": {
  45. "Cline": {
  46. "command": "cline",
  47. "args": ["--acp"],
  48. "env": {}
  49. }
  50. }
  51. }
  52. ```
  53. 5. **Use Cline**:
  54. - Open the AI Chat tool window
  55. - Select "Cline" from the agent dropdown
  56. - Start coding with Cline in your JetBrains IDE!
  57. <Tip>
  58. JetBrains AI Assistant can expose its built-in MCP server to Cline, giving Cline access to IDE-specific tools and context.
  59. </Tip>
  60. ## Neovim
  61. [Neovim](https://neovim.io) is a hyperextensible Vim-based text editor loved by developers for its speed and flexibility. Use Cline in Neovim through the [agentic.nvim](https://github.com/carlos-algms/agentic.nvim) or [avante.nvim](https://github.com/yetone/avante.nvim) plugins, which provide ACP integration.
  62. <video
  63. src="https://storage.googleapis.com/cline_public_images/cline-acp-neovim-avante.mp4"
  64. autoPlay
  65. loop
  66. muted
  67. playsInline
  68. style={{ width: "100%", borderRadius: "8px", marginTop: "16px", marginBottom: "16px" }}
  69. />
  70. ### Setup with agentic.nvim
  71. 1. **Install Cline CLI** (if not already installed):
  72. ```bash
  73. npm i -g cline
  74. ```
  75. 2. **Authenticate with Cline**:
  76. ```bash
  77. cline auth
  78. ```
  79. 3. **Install agentic.nvim** using lazy.nvim:
  80. ```lua
  81. {
  82. "carlos-algms/agentic.nvim",
  83. opts = {
  84. provider = "cline-acp",
  85. acp_providers = {
  86. ["cline-acp"] = {
  87. command = "cline",
  88. args = {"--acp"},
  89. },
  90. },
  91. },
  92. keys = {
  93. {"<C-\\>", function() require("agentic").toggle() end, mode={"n","v","i"}, desc="Toggle Cline Chat"},
  94. },
  95. }
  96. ```
  97. 4. **Use Cline**:
  98. - Press `<C-\>` to toggle Cline chat
  99. - Start coding with Cline in Neovim!
  100. ### Setup with avante.nvim
  101. Follow the [avante.nvim documentation](https://github.com/yetone/avante.nvim) for configuring external ACP agents and point it to `cline --acp`.
  102. ## Zed
  103. [Zed](https://zed.dev) is a high-performance, multiplayer code editor built from the ground up for speed and collaboration. Zed's team created the Agent Client Protocol, making Cline a natural fit for this editor.
  104. ### Setup
  105. 1. **Install Cline CLI** (if not already installed):
  106. ```bash
  107. npm i -g cline
  108. ```
  109. 2. **Authenticate with Cline**:
  110. ```bash
  111. cline auth
  112. ```
  113. 3. **Configure Zed**:
  114. - Open Zed settings (`Cmd/Ctrl + ,`)
  115. - Add Cline to your `settings.json`:
  116. ```json
  117. {
  118. "agent_servers": {
  119. "Cline": {
  120. "type": "custom",
  121. "command": "cline",
  122. "args": ["--acp"],
  123. "env": {}
  124. }
  125. }
  126. }
  127. ```
  128. 4. **Use Cline**:
  129. - Open the AI assistant panel
  130. - Select "Cline" from the agent dropdown
  131. - Start coding with Cline in Zed!
  132. ## Other Editors
  133. Any editor that supports the Agent Client Protocol can run Cline. Check your editor's documentation for ACP configuration instructions, then point it to:
  134. ```bash
  135. cline --acp
  136. ```
  137. ## Troubleshooting
  138. ### Agent not appearing
  139. - Ensure Cline CLI is installed globally: `npm i -g cline`
  140. - Verify authentication: `cline auth`
  141. - Check that `cline --acp` runs without errors
  142. - Restart your editor after configuration changes
  143. ### Permission errors
  144. If Cline can't access files or run commands:
  145. - Check that your editor's ACP integration passes the correct working directory
  146. - Verify file permissions in your project
  147. - Ensure Cline has approval settings configured correctly
  148. ### Connection issues
  149. - Make sure no other Cline instance is using the same configuration directory
  150. - Check editor logs for ACP-related errors
  151. - Try running `cline --acp` manually to test the connection
  152. ## Learn More
  153. <Columns cols={2}>
  154. <Card title="CLI Overview" icon="terminal" href="/cline-cli/overview">
  155. Learn about Cline CLI's core capabilities and use cases.
  156. </Card>
  157. <Card title="Headless Mode" icon="robot" href="/cline-cli/three-core-flows">
  158. Run Cline autonomously in scripts, CI/CD pipelines, and automated workflows.
  159. </Card>
  160. <Card title="Skills" icon="graduation-cap" href="/customization/skills">
  161. Understand how Cline's Skills work across all editors via ACP.
  162. </Card>
  163. <Card title="Hooks" icon="link" href="/customization/hooks">
  164. Learn how to enforce policies with Hooks in any editor.
  165. </Card>
  166. </Columns>