Answer: The Cline SDK's design principles include strict dependency direction, where dependencies flow downward only and lower layers stay embeddable without pulling in the full runtime. It also has a browser-compatible agent loop in `@cline/agents` and treats `@cline/core` as the orchestration layer owning Node runtime integration. Status: Confirmed Entry: tool/cline/features/sdk-design-principles Revision: 1 Digest: sha256:10ae9477c5d644e6 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:07:32Z Last changed: 2026-11-13T03:07:32Z Last verified: 2026-11-20T12:30:20Z Next check: 2026-11-21T12:30:20Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Dependency direction | Dependencies flow downward only. | [1] | 2026-11-20 Lower layer property | Lower layers stay embeddable without pulling in the full runtime. | [1] | 2026-11-20 Browser-compatible runtime package | @cline/agents | [1] | 2026-11-20 Orchestration layer package | @cline/core | [1] | 2026-11-20 Sources: [1] Cline. "Packages". https://docs.cline.bot/sdk/architecture/overview.md Role: primary. Accessed: 2026-11-20T12:30:20Z Quote: "Dependencies flow downward only." (Supports: Dependency direction) Quote: "Lower layers stay embeddable without pulling in the full runtime." (Supports: Lower layer property) Quote: "`@cline/agents` exposes a browser-compatible runtime." (Supports: Browser-compatible runtime package) Quote: "`@cline/core` owns Node runtime integration: session persistence, built-in tools, automation, hub/remote transports, telemetry, and extension loading." (Supports: Orchestration layer package) Published: 2026-11-20T06:00:33Z Snapshot SHA-256: f8d8baa9c978a7dda3686e571f20a417c7b718ca931da05d7272743495291549 (captured 2026-11-13T03:07:31Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:07:32Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:30:20Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:30:20Z Last attempt: 2026-11-20T12:30:20Z Notes and limitations: Extracted automatically from a single official source (section "Design Principles"). Related: https://latestn.com/tool/cline/features/sdk-package-stack What are the Cline SDK packages and how do they depend on each other? https://latestn.com/tool/cline/features/sdk-packages-overview Which packages does the Cline SDK include and what does each one do? https://latestn.com/tool/cline/features/ssh-remote-how-it-works How does Cline Desktop connect to a remote machine over SSH without installing anything? https://latestn.com/tool/cline/features/review-and-ship-changes How do I review diffs and commit or open a PR for a task in Cline Kanban? https://latestn.com/tool/cline/features/review-changes-inline-comments How do I review and comment on changes made by Cline Kanban agents? https://latestn.com/tool/cline/features/scheduling-supported-products Which Cline products support scheduled agents (CLI, SDK, Kanban vs VSCode/JetBrains)? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:07:32Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cline/features/sdk-design-principles/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cline/features/sdk-design-principles POST: https://latestn.com/dispute/tool/cline/features/sdk-design-principles with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cline/features/sdk-design-principles?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What are the design principles and dependency direction rules for the Cline SDK? Revision 1, last verified 2026-11-20T12:30:20Z. https://latestn.com/tool/cline/features/sdk-design-principles (accessed 2026-11-21T09:57:34Z). @misc{LatestN_tool_cline_features_sdk_design_principles_r1, title = {What are the design principles and dependency direction rules for the Cline SDK?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cline/features/sdk-design-principles}}, note = {Revision 1; digest sha256:10ae9477c5d644e6; last verified 2026-11-20T12:30:20Z; accessed 2026-11-21T09:57:34Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cline/features/sdk-design-principles