Skip to content
BENIBIX Learn

strictPluginOnlyCustomization

AI⌨️ Claude CodeConfiguration

Also known as strictPluginOnlyCustomization setting

The key that lets add-ons come only from plugins.

Think of it like

It is like a kitchen where you may only cook from the boxes the shop sells. Home recipes are not allowed.

Example

Lucy's company wants every skill to be reviewed first. IT locks skills to plugins from its own marketplace.

Why it matters

A plugin goes through a marketplace a company can check. A file in a repo does not.

Definition

strictPluginOnlyCustomization is a key for managed settings. It blocks skills, agents, hooks and MCP servers that come from user and project files. They can then only come from plugins. Set it to true to lock all four, or to a list such as skills and hooks to lock some. Pair it with the key that picks where plugins come from.

Example code

json
{
  "strictPluginOnlyCustomization": ["skills", "hooks"]
}
Lock skills and hooks to plugins only.

Common mistake

Locking skills but not the plugin stores. Unless the store key is set too, any plugin can still bring them in.

Key takeaways

  1. 1
    Plugins only. For add-ons.
  2. 2
    All or some. true or a list.
  3. 3
    Pair with marketplaces. Pick the source.