Cline CLI v3.0.72 moves plugins into a worker process

Plugin execution moves out of the hub and into a worker, which is now the default. If a build cannot run plugins, the CLI reports this in cline config tools, cline hub plugins and session-start warnings rather than running them silently inside the hub. The CLINE_PLUGIN_MODE=in_process setting is no longer supported, so users must pick worker or sandbox.

Provider errors that interrupt a response mid-stream are now retried up to three times before the turn fails, and failed model requests log the provider's request id. cline hub ensure and cline hub start gain a --json flag that prints the hub URL and auth token, along with --allow-port-fallback, --no-connectors and --login-shell-path. cline hub also accepts --discovery-path, and hub commands no longer count as a CLI activation in usage stats.

The model catalog was refreshed with Boundless and Standard Compute providers added and SambaNova loading from the catalog, with MiniMax M3 as its default. With no model chosen, the Cline provider now uses Gemini 4 Argon, which also becomes the default for several other providers, while Grok 4.7 leaves the recommended list.

Agents that launch Cline through the hub should check plugin behavior on builds that cannot run plugins, since warnings now replace silent execution. Any configuration that sets CLINE_PLUGIN_MODE=in_process needs to move to worker or sandbox. Agents that rely on provider defaults should re-check their model choice, because many defaults changed in this release.