Plugins that declare a binaries manifest section can now have their binary assets automatically downloaded and installed into the plugin's bin/ directory.
- Controlled by
CLAUDE_CODE_PLUGIN_BINARY_ASSETSenv var ortengu_plugin_binary_assetsfeature flag. [Gradual Rollout] - Each entry in
binariesmaps a basename to a SHA-256 hash; only the first 10 entries are provisioned per pass. - Downloads are cached by hash to avoid redundant network requests.
- Binary files must remain within the plugin directory (path escape is rejected).
- The
binarieskey must be an object mapping basenames to{ sha256 }; invalid entries are skipped with a warning.
New provisioning system (search for "[pluginBinaryAssets]" and "binary asset provisioning failed")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_plugin_binary_assets Off in both readingsThe 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.196: off
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.196. It isn't a statement about your account. What a flag value here can and cannot tell you
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.
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.
New in this build: tengu_plugin_binary_assets