Answer: The plugin design guidelines are: use factory functions when the plugin needs configuration, keep setup() synchronous and fast, register all tools in setup() rather than lifecycle hooks, use lifecycle hooks for observation rather than modifying agent behavior, and handle errors gracefully in hooks. Status: Confirmed Entry: tool/cline/agents-and-automation/plugin-design-guidelines Revision: 1 Digest: sha256:eb930dfa607b2536 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:07:42Z Last changed: 2026-11-13T03:07:42Z Last verified: 2026-11-20T12:30:47Z Next check: 2026-11-21T12:30:47Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Factory functions guideline | Use factory functions (like `createGitHubPlugin`) when the plugin needs configuration. | [1] | 2026-11-20 Setup guideline | Keep `setup()` synchronous and fast. | [1] | 2026-11-20 Tool registration guideline | Register all tools in `setup()`, not in lifecycle hooks. | [1] | 2026-11-20 Lifecycle hooks guideline | Use lifecycle hooks for observation (logging, metrics, auditing), not for modifying agent behavior. | [1] | 2026-11-20 Error handling guideline | Handle errors gracefully in hooks. | [1] | 2026-11-20 Sources: [1] Cline. "Writing Plugins". https://docs.cline.bot/sdk/guides/writing-plugins.md Role: primary. Accessed: 2026-11-20T12:30:47Z Quote: "Use factory functions (like `createGitHubPlugin`) when the plugin needs configuration." (Supports: Factory functions guideline) Quote: "Keep `setup()` synchronous and fast." (Supports: Setup guideline) Quote: "Register all tools in `setup()`, not in lifecycle hooks." (Supports: Tool registration guideline) Quote: "Use lifecycle hooks for observation (logging, metrics, auditing), not for modifying agent behavior." (Supports: Lifecycle hooks guideline) Quote: "Handle errors gracefully in hooks." (Supports: Error handling guideline) Published: 2026-11-20T06:00:20Z Snapshot SHA-256: 63649596d759760d9cb1da0bf922ae4d84cc8396fe984b387b450ead95795776 (captured 2026-11-13T03:07:41Z) 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:42Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:30:47Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:30:47Z Last attempt: 2026-11-20T12:30:47Z Notes and limitations: Extracted automatically from a single official source (section "Plugin Design Guidelines"). Related: https://latestn.com/tool/cline/agents-and-automation/register-tools How do I register tools in Cline? https://latestn.com/tool/cline/agents-and-automation/restore-snapshot-agent-state How do I restore or snapshot Cline Agent conversation state? https://latestn.com/tool/cline/agents-and-automation/resume-team-session How do I resume a Cline agent team session? https://latestn.com/tool/cline/agents-and-automation/link-tasks-dependency-chain How do I link tasks together in Cline Kanban so the next task starts automatically? https://latestn.com/tool/cline/agents-and-automation/manage-schedules How do I manage, pause, or delete existing Cline schedules? https://latestn.com/tool/cline/agents-and-automation/parallel-agents-worktrees How does Cline Kanban run multiple agents in parallel without conflicts? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:07:42Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cline/agents-and-automation/plugin-design-guidelines/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/agents-and-automation/plugin-design-guidelines POST: https://latestn.com/dispute/tool/cline/agents-and-automation/plugin-design-guidelines with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cline/agents-and-automation/plugin-design-guidelines?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What guidelines should I follow when designing a Cline plugin? Revision 1, last verified 2026-11-20T12:30:47Z. https://latestn.com/tool/cline/agents-and-automation/plugin-design-guidelines (accessed 2026-11-21T09:59:10Z). @misc{LatestN_tool_cline_agents_and_automation_plugin_design_guidelines_r1, title = {What guidelines should I follow when designing a Cline plugin?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cline/agents-and-automation/plugin-design-guidelines}}, note = {Revision 1; digest sha256:eb930dfa607b2536; last verified 2026-11-20T12:30:47Z; accessed 2026-11-21T09:59:10Z} } 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/agents-and-automation/plugin-design-guidelines