Skip to content
Proposals/Move Agent Plugins into ~/.agents/plugins and Hu
proposalteamP5Worth a lookCline

Move Agent Plugins into ~/.agents/plugins and Hub-enable them in Settings → Customize

Cline Desktop v0.0.23 discovers Agent Plugins only from ~/.agents/plugins via the shared Hub. Workspace .agents/plugins is ignored. Put packages with plugin.json there so skills and MCP servers start automatically, then enable each plugin under Settings → Customize.

Why this loop

desktop-v0.0.23 routes Agent Plugins through the shared Hub: packages under ~/.agents/plugins are validated from plugin.json, valid Agent Skills become available, and stdio / Streamable HTTP / SSE MCP servers start automatically. Settings → Customize now lists Agent Plugins separately from Cline Plugins (description, badge, contributed tools) with Hub-managed per-plugin enable/disable. Workspace .agents/plugins is intentionally ignored, so repo-local plugin folders will silently stop working. Relocate packages, keep plugin.json valid, and enable only the plugins this machine should run so Hub auto-start of MCP servers matches intent. The same release also stops a wedged MCP server from blocking shutdown of the rest, so leftover plugin processes should no longer leak after disable or quit.

Proposed actions

  1. mkdir -p ~/.agents/plugins && if [ -d .agents/plugins ]; then echo 'Workspace .agents/plugins is ignored in desktop-v0.0.23 — copy each package into ~/.agents/plugins/<name> with its plugin.json'; ls -la .agents/plugins; fi
  2. For every directory in ~/.agents/plugins, open plugin.json and keep only packages whose declared Agent Skills and MCP servers (stdio, Streamable HTTP, or SSE) you want the Hub to validate and start automatically.
  3. In Cline Desktop open Settings → Customize, use the Agent Plugins list (not Cline Plugins), read each plugin's description, badge, and contributed tools, then Hub-enable only the plugins this machine should run.
  4. Add workspace .agents/plugins to .gitignore and replace any team docs or onboarding that install plugins in the repo with ~/.agents/plugins as the sole install path.
  5. After enabling plugins, quit Cline once and confirm Hub-started MCP processes for disabled or unused plugins exit (wedged-server shutdown leak is fixed in this release).

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: Move Agent Plugins into ~/.agents/plugins and Hub-enable them in Settings → Customize Summary: Cline Desktop v0.0.23 discovers Agent Plugins only from ~/.agents/plugins via the shared Hub. Workspace .agents/plugins is ignored. Put packages with plugin.json there so skills and MCP servers start automatically, then enable each plugin under Settings → Customize. Primary source: https://github.com/cline/cline/releases/tag/desktop-v0.0.23

Why it matters

desktop-v0.0.23 routes Agent Plugins through the shared Hub: packages under ~/.agents/plugins are validated from plugin.json, valid Agent Skills become available, and stdio / Streamable HTTP / SSE MCP servers start automatically. Settings → Customize now lists Agent Plugins separately from Cline Plugins (description, badge, contributed tools) with Hub-managed per-plugin enable/disable. Workspace .agents/plugins is intentionally ignored, so repo-local plugin folders will silently stop working. Relocate packages, keep plugin.json valid, and enable only the plugins this machine should run so Hub auto-start of MCP servers matches intent. The same release also stops a wedged MCP server from blocking shutdown of the rest, so leftover plugin processes should no longer leak after disable or quit.

Suggested actions

  1. mkdir -p ~/.agents/plugins && if [ -d .agents/plugins ]; then echo 'Workspace .agents/plugins is ignored in desktop-v0.0.23 — copy each package into ~/.agents/plugins/<name> with its plugin.json'; ls -la .agents/plugins; fi
  2. For every directory in ~/.agents/plugins, open plugin.json and keep only packages whose declared Agent Skills and MCP servers (stdio, Streamable HTTP, or SSE) you want the Hub to validate and start automatically.
  3. In Cline Desktop open Settings → Customize, use the Agent Plugins list (not Cline Plugins), read each plugin's description, badge, and contributed tools, then Hub-enable only the plugins this machine should run.
  4. Add workspace .agents/plugins to .gitignore and replace any team docs or onboarding that install plugins in the repo with ~/.agents/plugins as the sole install path.
  5. After enabling plugins, quit Cline once and confirm Hub-started MCP processes for disabled or unused plugins exit (wedged-server shutdown leak is fixed in this release).

Config surfaces this release may change

  • skills (high confidence) — check your repo before applying
  • MCP servers — 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-desktop-v0-0-23-move-agent-plugins-into-agents-plugins-and-hub-ena and mark Applied, Skipped, or Failed. Proposal id: 0c40bd33-79cc-47ac-b6a8-8526d535d836

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.

agentmcpsecuritycliRelease 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

Clinedesktop-v0.0.23Sep 3, 2026

desktop-v0.0.23 Desktop v0.0.23

Agent Plugins are now discovered and run by the shared Hub. · Packages under ~/.agents/plugins are validated from their plugin.json, their valid Agent Skills become available to the agent, and their stdio / Streamable HTTP / SSE MCP servers start automatically. · Settings → Customize lists Agent Plugins separately from Cline Plugins, with each plugin's description, badge, and contributed tools, and enable/disable is Hub-managed per plugin. · Workspace .agents/plugins directories are intentionally ignored · +9 more changes
Verified excerpt — the source's own words
  • Agent Plugins are now discovered and run by the shared Hub. Packages under ~/.agents/plugins are validated from their plugin.json, their valid Agent Skills become available to the agent, and their stdio / Streamable HTTP / SSE MCP servers start automatically. Settings → Customize lists Agent Plugins separately from Cline Plugins, with each plugin's description, badge, and contributed tools, and enable/disable is Hub-managed per plugin. Workspace .agents/plugins directories are intentionally ignored
  • The "Cline Hub was updated" dialog no longer appears on every launch and reconnect. The app no longer prompts about a Hub running the same core version it does — a desktop and CLI release cut from different commits bundle the same core but never share a build fingerprint, so anyone with both installed got a dialog whose "Update and restart" looped on "no app update available". The build-mismatch dialog now also waits until an app update is actually staged, and "Later" sticks across session switches, reloads, and relaunches instead of resurfacing every time. A Hub the app genuinely cannot talk to still warns every time

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

Primary source ↗