Skip to main content
The SDK is split into layered packages. Dependencies flow downward: core depends on agents, llms, and shared; agents depends on llms and shared; llms depends on shared.

Package Stack

Packages

@cline/core

Node runtime/orchestration layer. Key exports include: Capabilities include:
  • local/hub/remote runtime backends
  • session manifests and message artifacts
  • built-in tools
  • tool approvals
  • automation/scheduling services
  • telemetry hooks
  • plugin/extension loading
  • team/sub-agent tools
Depends on: @cline/shared, @cline/llms, @cline/agents.

@cline/agents

Browser-compatible agent execution loop. Key exports include: Methods on AgentRuntime include run, continue, abort, subscribe, restore, and snapshot. Depends on: @cline/shared, @cline/llms.

@cline/llms

Provider and model layer. Key exports include: Depends on: @cline/shared.

@cline/shared

Foundation package for shared contracts and utilities. Key exports include: No higher-layer dependencies.

Install

@cline/sdk re-exports everything from @cline/core. Install @cline/agents or @cline/llms directly only if you need lower-level control.

Design Principles

Strict dependency direction

Dependencies flow downward only. Lower layers stay embeddable without pulling in the full runtime.

Browser-compatible agent loop

@cline/agents exposes a browser-compatible runtime. It does not own session storage, built-in file/shell tools, hub transports, or Node-specific orchestration.

Core as orchestration layer

@cline/core owns Node runtime integration: session persistence, built-in tools, automation, hub/remote transports, telemetry, and extension loading.