{"version":"2.1.265","anchor":"new-plugin-settings-field-payloadslots","canonical_anchor":"new-plugin-settings-field-payloadslots","heading":"New plugin settings field: payloadSlots","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/new-plugin-settings-field-payloadslots","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### New plugin settings field: payloadSlots\n\nPlugin settings gain a new payloadSlots field alongside shell settings and hooks\n\n**Unclear.** What a plugin \"slot\" contains or is used for is not stated.\n\n**What**\n\nWhen Claude Code assembles settings contributed by plugins, it now includes a `payloadSlots` map, built from each plugin's slot entries, alongside the existing `shellSettings`, `envVars`, `sandboxSettings`, and `hooks` fields. A new helper checks whether any slots are non-empty to decide whether a plugin's settings count as meaningful (\"non-trivial\").\n\n**Why**\n\nThe finding does not say what a plugin \"slot\" holds or what it is used for, only that plugins can now contribute this additional kind of data and that it factors into whether a plugin's settings are considered non-trivial.\n\n- Area: Plugins\n- Names: `payloadSlots`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}