Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
Home / Reference / Slash commands

/cloud-plugins

slash never mined JSON

A Claude Code slash command, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.

You now decide separately whether cloud sessions may use your plugins and your local settings.

Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.242.

First seen — never in a mined build
Last seen — never in a mined build
Builds0 / 149on this box, as of v2.1.308
Written about v2.1.242 first named in a changelog, 24 Aug 2026

In the changelogs

7

Releases whose published page names /cloud-plugins.

  1. v2.1.260
    Cloud session plugin visibility panel

    A new panel shows which plugins a connected cloud session has loaded.

    found in this entry's text, named in this entry

  2. v2.1.247
    /cloud-plugins consent text covers set-aside sessions and corrects the restart caveat

    Plugin-sharing consent wording now covers set-aside sessions and correctly says "until it restarts".

    named in this entry, found in this entry's text

  3. v2.1.247
    A saved "yes" for device hooks and cloud plugins is ignored if the session could have edited it

    A saved yes to forwarding hooks and plugins is ignored if the cloud session could have edited that file.

    found in this entry's text

  4. v2.1.247
    Cloud sessions say why a saved plugin answer was not reused

    If a cloud session could rewrite your plugin config, your saved yes is ignored and you are asked to run /cloud-plugins again.

    named in this entry, found in this entry's text

  5. v2.1.246
    Plugin forwarding to cloud sessions explains why nothing was sent

    When your plugins aren't forwarded to a cloud session, you now get the specific reason.

    found in this entry's text

  6. v2.1.242
    /cloud-plugins and a matching opt-in for sending this machine's settings to cloud sessions

    You now decide separately whether cloud sessions may use your plugins and your local settings.

    named in this entry, found in this entry's text

  7. v2.1.242
    cloud-plugins added to the slash-command map with a per-machine consent store

    A cloud-plugins command exists with a per-machine record of whether your plugins may be used in cloud sessions.

    named in this entry

First cited

5

The earliest release whose published evidence quoted /cloud-plugins was v2.1.242, 24 Aug 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

ReleaseDateThe span that was quoted
v2.1.24224 Aug 2026Your plugins are not used in cloud sessions from this machine yet: run /cloud-plugins in claude on this machine to decide.
v2.1.24625 Aug 2026run /cloud-plugins to send them
v2.1.24726 Aug 2026does not go by the saved answer: answer Yes or No in /cloud-plugins when you want to choose for it
v2.1.24726 Aug 2026the saved Yes was withdrawn (a No in /cloud-plugins, or the answer was removed)
v2.1.24726 Aug 2026the saved answer here could be changed by this session; run /cloud-plugins to decide for it

Presence across releases

0

The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the slash command does. All slash commands.

Feedback