Skip to content
Proposals/Switch Cline plugins to worker mode and drop CLI
proposaldeveloperP5High impactCline

Switch Cline plugins to worker mode and drop CLINE_PLUGIN_MODE=in_process

Cline CLI 3.0.72 runs plugins in a worker (in_process removed), warns in cline config tools, cline hub plugins, and session start if plugins cannot run, adds hub --json/--discovery-path flags, retries mid-stream errors 3 times, and defaults the Cline provider to Gemini 4 Argon.

Why this loop

cli-v3.0.72 is a breaking plugin-isolation change: plugins no longer execute inside the hub, and CLINE_PLUGIN_MODE=in_process is unsupported. Quiet in-hub fallback is gone; inability to run plugins is now reported by cline config tools, cline hub plugins, and session-start warnings. Leaving in_process in shell profiles, CI, or compose files will fail or be ignored. Set worker (default) or sandbox, then confirm plugin status with those commands before relying on skills. Hub bring-up also gained --json (URL and auth token), --allow-port-fallback, --no-connectors, --login-shell-path, and --discovery-path, which are better for scripts than scraping human output. Mid-stream provider errors retry up to 3 times and failed requests log the provider request id—use that id in support tickets. Separately, an unset Cline-provider model now lands on Gemini 4 Argon (Grok 4.7 left the recommended list; the free list swapped Step 5 Preview for Nemotron 3.5 Super VL). Pin your previous model if that default is not intended.

Proposed actions

  1. grep -RIn --include='.env' --include='.yml' --include='.yaml' --include='.sh' --include='.zshrc' --include='.bashrc' 'CLINE_PLUGIN_MODE=in_process' . "$HOME"/.bashrc "$HOME"/.zshrc "$HOME"/.zprofile "$HOME"/.profile 2>/dev/null; unset CLINE_PLUGIN_MODE; export CLINE_PLUGIN_MODE=worker
  2. cline config tools; cline hub plugins
  3. cline hub ensure --json --allow-port-fallback
  4. If cline config tools, cline hub plugins, or session-start warnings say this build cannot run plugins, stop assuming plugins still execute in the hub; upgrade the CLI or set CLINE_PLUGIN_MODE=sandbox instead of in_process.
  5. On the Cline provider, explicitly select your previous model so Gemini 4 Argon is not adopted by the empty-model default; do not expect Grok 4.7 on the recommended list or Step 5 Preview on the free list. When a model call fails after the 3 mid-stream retries, paste the logged provider request id into the Cline support ticket.

Agent prompt

Paste into your agent or query via MCP (get_agent_prompt) — free, no extra AI cost

Cline / .clinerules task

DevAgentRadar → Cline

You are helping me adopt a real coding-assistant change. Work only from the facts below. Do not invent features.

Context

Assistant: Cline Proposal: Switch Cline plugins to worker mode and drop CLINE_PLUGIN_MODE=in_process Summary: Cline CLI 3.0.72 runs plugins in a worker (in_process removed), warns in cline config tools, cline hub plugins, and session start if plugins cannot run, adds hub --json/--discovery-path flags, retries mid-stream errors 3 times, and defaults the Cline provider to Gemini 4 Argon. Primary source: https://github.com/cline/cline/releases/tag/cli-v3.0.72

Why it matters

cli-v3.0.72 is a breaking plugin-isolation change: plugins no longer execute inside the hub, and CLINE_PLUGIN_MODE=in_process is unsupported. Quiet in-hub fallback is gone; inability to run plugins is now reported by cline config tools, cline hub plugins, and session-start warnings. Leaving in_process in shell profiles, CI, or compose files will fail or be ignored. Set worker (default) or sandbox, then confirm plugin status with those commands before relying on skills. Hub bring-up also gained --json (URL and auth token), --allow-port-fallback, --no-connectors, --login-shell-path, and --discovery-path, which are better for scripts than scraping human output. Mid-stream provider errors retry up to 3 times and failed requests log the provider request id—use that id in support tickets. Separately, an unset Cline-provider model now lands on Gemini 4 Argon (Grok 4.7 left the recommended list; the free list swapped Step 5 Preview for Nemotron 3.5 Super VL). Pin your previous model if that default is not intended.

Suggested actions

  1. grep -RIn --include='.env' --include='.yml' --include='.yaml' --include='.sh' --include='.zshrc' --include='.bashrc' 'CLINE_PLUGIN_MODE=in_process' . "$HOME"/.bashrc "$HOME"/.zshrc "$HOME"/.zprofile "$HOME"/.profile 2>/dev/null; unset CLINE_PLUGIN_MODE; export CLINE_PLUGIN_MODE=worker
  2. cline config tools; cline hub plugins
  3. cline hub ensure --json --allow-port-fallback
  4. If cline config tools, cline hub plugins, or session-start warnings say this build cannot run plugins, stop assuming plugins still execute in the hub; upgrade the CLI or set CLINE_PLUGIN_MODE=sandbox instead of in_process.
  5. On the Cline provider, explicitly select your previous model so Gemini 4 Argon is not adopted by the empty-model default; do not expect Grok 4.7 on the recommended list or Step 5 Preview on the free list. When a model call fails after the 3 mid-stream retries, paste the logged provider request id into the Cline support ticket.

Config surfaces this release may change

  • skills (high confidence) — check your repo before applying

After you finish

Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.

Tell the human: open https://devagentradar.com/proposals/cline-cli-v3-0-72-switch-cline-plugins-to-worker-mode-and-drop-cline-plu and mark Applied, Skipped, or Failed. Proposal id: 7513ec21-513f-4f8c-b48c-551fd60b5121

Your job

  1. Restate the change in one sentence.
  2. Propose a minimal plan for my repo (or a throwaway pilot).
  3. Implement only what I approve; prefer small diffs and tests.
  4. Call out risks (permissions, breaking APIs, cost).

Start by confirming you understood the proposal.

modelsecurityclibreakingRelease source ↗

Your loop

This browser · no sign-in · not shared as “you”

After you run the prompt

Only you can mark this. Agents cannot write your loop.

Your decision stays on this device. A public tally appears after a few votes.

Originating release signal

ClineCLI 3.0.72Oct 16, 2026

cli-v3.0.72 CLI v3.0.72

Plugins now run in a worker instead of directly inside the hub. · If this build can't run plugins, Cline says so in cline config tools, cline hub plugins, and the session-start warnings instead of quietly running them inside the hub. CLINE_PLUGIN_MODE=in_process is no longer supported; use worker (the default) or sandbox · When a provider error interrupts a response mid-stream, Cline retries it up to 3 times before failing the turn · Failed model requests now log the provider's request id, which makes support tickets easier to trace · +8 more changes
Verified excerpt — the source's own words
  • Plugins now run in a worker instead of directly inside the hub. If this build can't run plugins, Cline says so in cline config tools, cline hub plugins, and the session-start warnings instead of quietly running them inside the hub. CLINE_PLUGIN_MODE=in_process is no longer supported; use worker (the default) or sandbox
  • When a provider error interrupts a response mid-stream, Cline retries it up to 3 times before failing the turn
  • Failed model requests now log the provider's request id, which makes support tickets easier to trace
  • cline hub ensure and cline hub start gain --json (prints the hub URL and auth token), --allow-port-fallback, --no-connectors, and --login-shell-path. cline hub accepts --discovery-path to use a dedicated discovery record
  • cline hub commands no longer count as a CLI activation in usage stats
  • With no model chosen, the Cline provider now uses Gemini 4 Argon, the new first model in Cline's recommended list
  • Refreshed the model catalog. Adds the Boundless and Standard Compute providers, and SambaNova now comes from the catalog with MiniMax M3 as its default. The Cline recommended list adds Gemini 4 Argon and drops Grok 4.7,

Excerpt ends here — this release continues at the source ↗.

Primary source ↗