Use Cline as the coding agent in Zed, JetBrains IDEs, Neovim, Emacs, and any other ACP-capable client.
Cline CLI speaks the Agent Client Protocol (ACP), an open standard that lets editors and other tools drive terminal-based coding agents. Any ACP-capable client can use Cline as its coding agent without a dedicated extension — the same agent you use in the terminal, embedded in the tool you’re already working in.
Credentials are optional up front — most clients let you sign in when the first session starts, and credentials saved by cline auth are reused automatically
You don’t run this yourself — the client launches the command and talks to Cline over stdio. Configure the client to run it, then start a thread from its agent UI.
If a client can’t spawn the agent, it may not inherit your shell’s PATH. Use the absolute path from which cline as the command.
ACP is supported by a growing ecosystem of editors, IDEs, and other tools. Setup for the most popular clients is below; the ACP client directory maintains the full list.
AI Assistant in JetBrains IDEs (IntelliJ IDEA, PyCharm, WebStorm, and others) supports ACP agents. In the AI Chat tool window, select Add Custom Agent — this creates ~/.jetbrains/acp.json — then add Cline:
Anything that speaks ACP can run Cline the same way — point it at cline --acp. The client directory includes note-taking apps like Obsidian, notebooks like marimo, mobile clients, and chat bridges for Slack, Discord, and Telegram.
Sign-in from the client — if no credentials are found, the client prompts you to sign in with Cline, ClinePass, or a ChatGPT subscription. Credentials saved by cline auth are reused automatically.
Plan/Act modes — switch between Plan and Act from the client’s mode selector.
Model and provider selection — pick any model from the active provider’s catalog, or switch providers, from the client’s model picker.
Permission prompts — file edits and commands are approved through the client’s permission UI. Nothing is auto-approved by default, but you can auto-approve all tools per session or at launch.
Session resume — conversations are persisted, so clients that support session loading can restore a thread after a restart.
Images — prompts can include images for vision-capable models.
Organization switching — Cline team accounts can switch between personal and organization billing.
By default every file edit and command goes through the client’s permission UI. To let Cline run tools without asking:
Per session — sessions expose an Auto-approve tools toggle in the client’s session settings (clients that support ACP config options, like Zed, render it alongside the model and mode pickers). Flipping it takes effect on the next tool call.
At launch — pass --auto-approve true in the client’s agent config to start every session with auto-approval on:
With auto-approval on, Cline edits files and runs commands without asking. Only enable it in workspaces where you’re comfortable with unattended changes.