Scenario 6: Add plugin constraints to a plugin

Use this when your environment depends on Claude plugins and you want the plugin to describe not just files, but also expected plugin versions.

Frequency: Rare · Status: Shipped

← Back to scenarios index

Use this when your environment depends on Claude plugins and you want the plugin to describe not just files, but also expected plugin versions.

Typical commands:

harnesstap plugin edit my-setup --add formatter@team-marketplace --type plugin_pin --version "^2.1.0"
harnesstap plugin edit my-setup --remove formatter@team-marketplace --type plugin_pin
harnesstap plugin show my-setup

This is especially useful for team-wide setups where the harness environment should stay compatible across machines. See Scenario 16 for enforcing the constraints in CI.