Answer: A Cline plugin manifest is a `package.json` that includes a `cline` field declaring plugin entry points via a `cline.plugins` array, where each entry can be an object with a `paths` array and `capabilities`, or a plain string path to a `.ts` or `.js` file exporting an `AgentPlugin`. The host provides dependencies under the `@cline/` scope: `@cline/sdk`, `@cline/core`, `@cline/agents`, `@cline/llms`, and `@cline/shared`. Status: Confirmed Entry: tool/cline/features/plugin-manifest-format Revision: 1 Digest: sha256:44544d0ecd1e0e07 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:06:35Z Last changed: 2026-11-13T03:06:35Z Last verified: 2026-11-20T12:27:35Z Next check: 2026-11-21T12:27:35Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of manifest field | cline | [1] | 2026-11-20 plugins array | cline.plugins | [1] | 2026-11-20 entry file types | .ts | [1] | 2026-11-20 host-provided scope | @cline/ | [1] | 2026-11-20 host-provided packages | @cline/sdk | [1] | 2026-11-20 peer dependency example | @cline/sdk | [1] | 2026-11-20 Sources: [1] Cline. "Plugins". https://docs.cline.bot/customization/plugins.md Role: primary. Accessed: 2026-11-20T12:27:35Z Quote: "its `package.json` should include a `cline` field that declares plugin entry points" (Supports: manifest field) Quote: "The `cline.plugins` array accepts:" (Supports: plugins array) Quote: "Each path should point to a `.ts` or `.js` file that exports an `AgentPlugin`" (Supports: entry file types) Quote: "Dependencies under the `@cline/` scope are provided by the host runtime." (Supports: host-provided scope) Quote: "The host currently provides `@cline/sdk`, `@cline/core`, `@cline/agents`, `@cline/llms`, and `@cline/shared`." (Supports: host-provided packages) Quote: ""@cline/sdk": "*"" (Supports: peer dependency example) Published: 2026-11-20T02:33:16Z Snapshot SHA-256: 9eeac8b4038cb2ea8e5fcfe5b96c72bdc3277c6e199a0def17c051e110acc163 (captured 2026-11-13T03:06:35Z) 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:06:35Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:27:35Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:27:35Z Last attempt: 2026-11-20T12:27:35Z Notes and limitations: Extracted automatically from a single official source (section "Plugin Manifest Format"). Related: https://latestn.com/tool/cline/features/plugin-supported-surfaces Which Cline surfaces support plugins, and are plugins available in the VSCode or JetBrains extensions? https://latestn.com/tool/cline/features/restore-checkpoint How do I restore a checkpoint in Cline? 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/plan-mode-vs-act-mode What is the difference between Plan Mode and Act Mode in Cline? https://latestn.com/tool/cline/features/plan-vs-act-capabilities What can Cline do in Plan mode versus Act mode? https://latestn.com/tool/cline/features/plugin-extension-points What extension points can Cline plugins provide, such as tools, commands, hooks, rules, and events? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:06:35Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cline/features/plugin-manifest-format/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/plugin-manifest-format POST: https://latestn.com/dispute/tool/cline/features/plugin-manifest-format with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cline/features/plugin-manifest-format?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What does a Cline plugin manifest look like and which dependencies does the host provide? Revision 1, last verified 2026-11-20T12:27:35Z. https://latestn.com/tool/cline/features/plugin-manifest-format (accessed 2026-11-21T09:54:11Z). @misc{LatestN_tool_cline_features_plugin_manifest_format_r1, title = {What does a Cline plugin manifest look like and which dependencies does the host provide?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cline/features/plugin-manifest-format}}, note = {Revision 1; digest sha256:44544d0ecd1e0e07; last verified 2026-11-20T12:27:35Z; accessed 2026-11-21T09:54:11Z} } 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/plugin-manifest-format