{"version":"2.1.196","anchor":"plugin-binary-asset-provisioning","canonical_anchor":"plugin-binary-asset-provisioning","heading":"Plugin Binary Asset Provisioning","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.196\/e\/plugin-binary-asset-provisioning","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.196","markdown":"### Plugin Binary Asset Provisioning\n\nPlugins that declare a `binaries` manifest section can now have their binary assets automatically downloaded and installed into the plugin's `bin\/` directory.\n\n**Details**\n\n- Controlled by `CLAUDE_CODE_PLUGIN_BINARY_ASSETS` env var or `tengu_plugin_binary_assets` feature flag. [Gradual Rollout]\n- Each entry in `binaries` maps a basename to a SHA-256 hash; only the first 10 entries are provisioned per pass.\n- Downloads are cached by hash to avoid redundant network requests.\n- Binary files must remain within the plugin directory (path escape is rejected).\n- The `binaries` key must be an object mapping basenames to `{ sha256 }`; invalid entries are skipped with a warning.\n\n**Evidence**\n\nNew provisioning system (search for `\"[pluginBinaryAssets]\"` and `\"binary asset provisioning failed\"`)\n\n- Flag `tengu_plugin_binary_assets`: Off in both readings (read for one account on one subscription tier against v2.1.196; this account: off, anonymous baseline: off, compiled default: 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."}