Cline CLI 3.0.71 loads plugins inside its hub instead of a separate node or bun process and adds a cline hub plugins command

Overview

Cline’s command-line agent has a new plugin loading model. According to the CLI v3.0.71 release notes, “Plugins now load inside the hub instead of a separate node or bun process, so the CLI no longer needs a JavaScript runtime on your PATH to run plugins.” GitHub’s release timestamp for the tag is 08:56 UTC on October 13, 2026.

What the Release Notes Say

The v3.0.71 notes pair the change with new visibility into plugin failures. A plugin that fails to load no longer silently loses its tools, the notes say. Cline now prints a warning naming the plugin and the error, cline config tools --json lists the failure as a plugin_failure entry, and what the notes call the new cline hub plugins command shows each plugin’s status and last error. Adding --reload <plugin> re-imports one plugin without restarting the hub. Users who want the previous behavior can set CLINE_PLUGIN_MODE=sandbox, which the notes say keeps the old subprocess behavior.

The notes list other changes in the same release:

• --thinking now applies in ACP mode (--acp); before, the notes say, ACP sessions always ran with reasoning off.
• cline hook accepts agent_error events. The notes say it previously exited with an error and no response.
• A provider API key set in the environment, such as OPENROUTER_API_KEY, now counts as configured at startup for providers that read a single environment variable. Before, the notes say, the terminal interface asked users to set up the provider anyway.
• With no model chosen, the Cline provider uses the first model in Cline’s recommended list, which the notes name as Claude Sonnet 5.5.
• Turning reasoning off now works on every provider, according to the notes.
• Screenshots and other images no longer inflate the token estimate, which the notes say had made auto-compaction run long before a conversation neared its limit.
• For scheduled runs, queued runs now start instead of staying pending, a run whose model call fails is marked failed with the error, and after downtime only the latest missed occurrence of a schedule runs.
• Rule files that are symlinks now load, and skills in .claude/skills are now discovered.

The SDK Release Published Earlier the Same Day

Cline’s SDK v0.0.93 release, which GitHub timestamps at 08:26 UTC on October 13, 2026, uses nearly identical wording: “Plugins load in-process through one registry per process instead of a node/bun subprocess, so the compiled CLI and its hub no longer need a runtime on PATH.” It adds that the registry tracks each plugin’s state as loading, ready, degraded, failed or disabled, along with its last error, and that CLINE_PLUGIN_MODE=sandbox keeps the subprocess sandbox. The SDK notes also say each session gets its own copy of every plugin module, so plugins that keep per-session state at module level keep working.

The CLI notes do not say that the CLI change is built on the SDK change. The matching wording suggests a connection, but that is an inference, not something either set of notes states.

Context From the Previous CLI Release

The v3.0.70 notes, timestamped October 8, 2026, say cline dashboard is now cline hub dashboard, with the old command still working as a hidden alias. They also say that options which were accepted but never did anything, such as cline history --page, now fail with “unknown option”, and tell users to remove them from scripts.

What We Don’t Know

• The release notes do not discuss whether running plugins inside the hub changes how isolated they are from the rest of the process, beyond offering CLINE_PLUGIN_MODE=sandbox as a way to keep the old subprocess behavior.
• The notes do not say which release introduced the original node or bun subprocess model, or how many users rely on plugins.
• This article is based on Cline’s own release notes. No independent testing of the behavior is reported here, and the descriptions of fixes are the maintainers’ wording.