Answer: You can read plugin status via `StartSessionResult.pluginIssues`, status notice events with `metadata.pluginIssue`, or hub clients sending `plugins.status`/`plugins.list`; when a hook fails, the plugin becomes `degraded` and the run continues unless `hookErrorMode` is `"throw"`. Status: Confirmed Entry: tool/cline/troubleshooting/plugin-status-and-errors Revision: 1 Digest: sha256:b6b8d81a405ca220 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:07:47Z Last changed: 2026-11-13T03:07:47Z Last verified: 2026-11-20T12:30:59Z Next check: 2026-11-21T12:30:59Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Unit | Source | As of Hook failure status | degraded | | [1] | 2026-11-20 Hook timeout | 3 s | seconds | [1] | 2026-11-20 Statuses | loading | | [1] | 2026-11-20 Session issues field | StartSessionResult.pluginIssues | | [1] | 2026-11-20 Status notice metadata | metadata.pluginIssue | | [1] | 2026-11-20 Hub status command | plugins.status | | [1] | 2026-11-20 Failures to failed | Five failures in a row | | [1] | 2026-11-20 Sources: [1] Cline. "Plugins Overview". https://docs.cline.bot/sdk/plugins.md Role: primary. Accessed: 2026-11-20T12:30:59Z Quote: "Hook | 3 s | Plugin is `degraded`; the run continues unless `hookErrorMode` is `"throw"`" (Supports: Hook failure status) Quote: "| Hook | 3 s | Plugin is `degraded`" (Supports: Hook timeout) Quote: "Each plugin has a status of `loading`, `ready`, `degraded`, `failed`, or `disabled`." (Supports: Statuses) Quote: "`StartSessionResult.pluginIssues` lists the plugins the session asked for but doesn't have." (Supports: Session issues field) Quote: "reported to that session as a status notice event, with the issue in `metadata.pluginIssue`" (Supports: Status notice metadata) Quote: "Hub clients can send `plugins.status` (or `plugins.list`) for every plugin's status, last error, and the sessions using it." (Supports: Hub status command) Quote: "Five failures in a row turn a `degraded` plugin `failed`." (Supports: Failures to failed) Published: 2026-11-19T21:02:02Z Snapshot SHA-256: a0da36ee5f2c63ea46cffdefe4b6c612d2e07414231ba84af225173d16c7dc8a (captured 2026-11-13T03:07:47Z) 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:47Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:30:59Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:30:59Z Last attempt: 2026-11-20T12:30:59Z Notes and limitations: Extracted automatically from a single official source (section "Plugin Status and Errors"). Related: https://latestn.com/tool/cline/troubleshooting/retry-exponential-backoff How should I retry failed Cline API requests with exponential backoff? https://latestn.com/tool/cline/troubleshooting/ssh-remote-limitations What are the limitations of Cline Desktop remote development over SSH? https://latestn.com/tool/cline/troubleshooting/sso-troubleshooting What should I do if Cline SSO setup is not working? https://latestn.com/tool/cline/troubleshooting/mid-stream-errors How do I handle mid-stream errors from the Cline API? https://latestn.com/tool/cline/troubleshooting/openai-compatible-troubleshooting How do I troubleshoot problems connecting Cline to my organization's OpenAI-compatible endpoint? https://latestn.com/tool/cline/troubleshooting/otel-troubleshooting-debug How do I troubleshoot connection errors or enable debug mode for Cline's OpenTelemetry integration? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:07:47Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cline/troubleshooting/plugin-status-and-errors/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/troubleshooting/plugin-status-and-errors POST: https://latestn.com/dispute/tool/cline/troubleshooting/plugin-status-and-errors with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cline/troubleshooting/plugin-status-and-errors?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I check Cline plugin status and errors, and what happens when a hook fails? Revision 1, last verified 2026-11-20T12:30:59Z. https://latestn.com/tool/cline/troubleshooting/plugin-status-and-errors (accessed 2026-11-21T09:54:22Z). @misc{LatestN_tool_cline_troubleshooting_plugin_status_and_errors_r1, title = {How do I check Cline plugin status and errors, and what happens when a hook fails?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cline/troubleshooting/plugin-status-and-errors}}, note = {Revision 1; digest sha256:b6b8d81a405ca220; last verified 2026-11-20T12:30:59Z; accessed 2026-11-21T09:54:22Z} } 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/troubleshooting/plugin-status-and-errors