Cline is Cline Bot Inc.’s open-source AI harness for VS Code, JetBrains, the terminal, a desktop app, and as an SDK: a coding agent that makes language models operational through tools, MCP servers and an approval system. As of 20 September 2026.
What is Cline?
Cline is developed by Cline Bot Inc. and published in the cline/cline repository under the Apache-2.0 licence; per its GitHub history, the first versions shipped in July 2024. Originally launched as a VS Code extension, the project now describes itself as an “autonomous coding agent as an SDK, IDE extension, or CLI assistant,” and is accordingly available as a VS Code extension, a JetBrains plugin, a native desktop app for macOS and Windows, a terminal CLI, and a Node.js SDK. The CLI is installed via npm install -g cline and started by running cline inside a project directory; the IDE extension is available from the VS Code Marketplace and the JetBrains plugin repository.
Cline as an AI harness
Per the project, all surfaces share the same agent core, so Plan/Act mode, MCP servers, checkpoints, rules and provider configuration behave identically everywhere. In Plan mode, Cline explores the codebase read-only and drafts a strategy; in Act mode it executes it - every file edit and terminal command requires approval per the documentation, unless auto-approve is enabled. In the CLI, tool calls are auto-approved by default; --auto-approve false forces confirmation per call, and a sandbox mode forced via the CLINE_SANDBOX environment variable further isolates runs in a dedicated data directory. Tools are extended through native MCP servers (managed with cline mcp) and through the SDK, which can add custom tools and lifecycle hooks; project rules live in .clinerules/. A coordinator agent can break complex tasks into subtasks and delegate them to specialist agents in team mode (--team-name).
Models and model access
Per its documentation, Cline is not tied to a single provider: supported options include Claude, GPT and Gemini, plus OpenRouter, AWS Bedrock, Azure/GCP Vertex, Vercel AI Gateway, and local models via Ollama or LM Studio. A custom OpenAI-compatible endpoint is set in the IDE extension via the “OpenAI Compatible” provider with a base URL, API key and model ID; in the CLI, setup runs through the same interactive authentication flow (cline auth) or the global -P/--provider and -k/--key options - the vendor does not currently document a dedicated command-line option for the base URL. That means Cline can be run through the AI Gateway, provided the gateway is registered as a custom OpenAI-compatible endpoint.
Enterprise use: data protection and governance
When run in your own VPC, per the vendor requests flow directly from your own environment to the chosen model provider without Cline itself seeing your code or prompts; repositories are, per the documentation, never indexed or cached. Cline Enterprise names SSO, a three-tier role hierarchy, and central configuration for model access, MCP controls and workflows, plus VPC, on-premises and air-gapped deployments. Regardless of the harness used, source code and prompts go to whichever model provider is chosen, and that flow belongs in the record of processing activities beforehand.
Orchestrating Cline with herdr
Per herdr’s own documentation, herdr lists Cline as “detected but less thoroughly tested,” based on a screen manifest; a reliable statement on its integration role is not currently documented. Details and the full list of supported harnesses are on the herdr page.
Where it fits: developer harness and enterprise harness
Cline is a harness for developers working in an IDE, terminal or desktop app - for business users, CompanyGPT is the matching harness, with MCP tools, enterprise knowledge, and roles sourced from Entra ID or Keycloak. The AI Gateway provides the shared cost and governance layer across both. Our overview of all AI harnesses covers further coding agents and orchestrators. We help organizations integrate Cline and comparable harnesses cleanly into existing identity, cost and compliance structures.
