GitHubGitHub RepoNeeds Review

cline/cline

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

GitHub · Trending today

Open Source Open Markdown Open JSON

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

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/codexBoth 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-sdkBoth 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 layerThe 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 layerCursor’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

toolscoding#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.