Skip to content
BENIBIX Learn

Plugin Install Scope

AI⌨️ Claude CodeClaude Code Concepts

Also known as plugin scope, --scope project, enabledPlugins

Who gets a plugin: just you, your team, or you in one repo.

Think of it like

It is like a toy. You can share it with the class, keep it in your bag, or leave it on one desk.

Example

Emma installs a formatter for the project and commits the settings file. Each person on her team runs the install once in their own copy. Then it is on for all of them.

Why it matters

It decides who else gets the plugin. A project scope shares it with the team, while user and local scope keep it to you.

Definition

A plugin install scope says where a plugin you install is turned on. User scope turns it on for you in every project. Project scope turns it on for everyone in a repo, through the shared settings file. Local scope turns it on just for you in one repo. When two scopes disagree, local beats project, and project beats user.

Example code

bash
claude plugin install formatter@your-org --scope project
Turn the plugin on for everyone who works in this repo.
The scope is the last step of an install. It decides where the plugin is turned on.

Common mistake

Thinking that a committed project entry downloads the plugin for the whole team. It only turns it on. Each person still runs the install once in their copy of the repo.

Key takeaways

  1. 1
    User. You, in every project.
  2. 2
    Project. Your team, in one repo.
  3. 3
    Local. You, in one repo.