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

Claude Code v2.1.239 ·

Cloud sessions can be handed forwarded plugin settings

Cloud sessions can accept a pushed plugin configuration, but it stays off without server values.

Nothing to try yet Notable New Features
JSON All of v2.1.239
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
PluginsArea: what it touches
New FeaturesKind: in v2.1.239,
What probably matters to youSection of the release

Forwarding enabled plugins and marketplaces into a cloud session is built but needs two remote gates that fall back to false.

What

A cloud session can now receive a plugin configuration pushed from elsewhere, carrying only a list of enabled plugins and extra known marketplaces. It is off unless two remote gates, tengu_violin_wood and tengu_violin_amati, both come back true; each falls back to false if the lookup fails, so with no server values this does nothing.

Details
  • The payload must contain exactly the one forwarding key, itself limited to enabledPlugins and extraKnownMarketplaces. Anything else is rejected as "malformed".
  • Applying it, and the marketplace reconcile and install pass that follows, is only allowed for an admitted managed cloud worker. Refusals are reported as not_managed_cloud_worker, entrypoint, disabled and hermetic.
  • If the gate read does not settle in time the outcome is flag_unsettled; a false read is flag_off.
  • Reconcile results are reported under ccr_plugin_forwarding_reconcile.
Evidence

cloudPluginsForwarded

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Feature flag
tengu_violin_wood Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.239: off

tengu_violin_amati Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.239: off

Read once, for one account on one subscription tier, against v2.1.239. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns on for tengu_violin_amati, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns off for tengu_violin_amati, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_violin_amati, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_violin_amati

See this entry in the whole of v2.1.239 →

Feedback