# cline/cline

Source: [GitHub](https://github.com/cline/cline)  
Feed7 permalink: https://feed7.dev/p/cline-03xl2ea  
Published: Unknown  
Trust: Needs Review (needs_review)

## Why Included

Cline now presents one open agent core across IDE, CLI, desktop, and SDK surfaces, with custom tools, persistent teams, schedules, and headless automation.

## Source Summary

Cline exposes its agent as a Node.js SDK, terminal UI, headless CLI, VS Code extension, desktop app, and JetBrains client. The shared engine supports custom tools, MCP, **multi-agent teams**, persistent schedules, checkpoints, and human approval.

## Practical Implication

Builders can use **@cline/sdk** to embed the same core behind custom tools and lifecycle hooks, or run JSON-producing headless jobs in CI. Put repository conventions in .clinerules and decide explicitly where auto-approval is safe.

## Agent-Ready Context

Cline exposes its agent as a Node.js SDK, terminal UI, headless CLI, VS Code extension, desktop app, and JetBrains client. The shared engine supports custom tools, MCP, **multi-agent teams**, persistent schedules, checkpoints, and human approval.

Builders can use **@cline/sdk** to embed the same core behind custom tools and lifecycle hooks, or run JSON-producing headless jobs in CI. Put repository conventions in .clinerules and decide explicitly where auto-approval is safe.

The JetBrains plugins are **not open source**, despite using the shared core. Broad command, web, connector, and scheduling access also increases the need for scoped credentials, access control, and review boundaries.

## Connected Context

Feed7 judgment across 807 accumulated Signals:

Cline confirms that a coding-agent core can serve embedded products, interactive clients, and headless automation without separate engines. Compared with the candidates, its differentiator is the breadth of first-party lifecycle surfaces, but portability and convenience do not erase runtime-specific behavior, host-process exposure, credential scope, or approval design.

- [openai/codex](https://feed7.dev/p/codex-1jzl221) — Both expose one coding-agent project across terminal, editor, desktop, and hosted-style workflows, reinforcing surface choice as an interface decision while leaving isolation and capability differences to be tested.
- [github/copilot-sdk](https://feed7.dev/p/copilot-sdk-0vwjjou) — Both support embedding an existing coding-agent runtime into applications; Copilot broadens language coverage, while Cline pairs its Node.js SDK with its own clients, schedules, teams, and checkpoints.
- [Cline is now available in the AI SDK harness layer](https://feed7.dev/p/cline-harness-adapter-1sv80a0) — The adapter provides an additional shared application boundary for Cline, but clarifies that only its tools are sandboxed while the agent remains in the host, narrowing any isolation claim.
- [Cursor is now available in the AI SDK harness layer](https://feed7.dev/p/cursor-ai-sdk-harness-adapter-0nbmzmh) — Cursor’s adapter reinforces the value of a common harness interface for runtime selection, while its stated limits support testing Cline-specific controls and behavior rather than assuming interchangeability.

## Context Map

- Layer: tools
- Domains: coding
- Topics: coding-agents, agent-sdks, dev-ux

## Uncertainty

- The JetBrains plugins are **not open source**, despite using the shared core. Broad command, web, connector, and scheduling access also increases the need for scoped credentials, access control, and review boundaries.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.