[plugins] — Claude Code plugins

[plugins]
required = ["claude-code-mcp-fileshare"]

Fields

required (list of strings)

Names of Claude Code plugins the rig needs. rig doctor reports missing ones as advisory gaps — they don't block install, because plugin install isn't yet automated.

Why advisory

Claude Code's plugin install path is still evolving. Rig deliberately holds off on auto-installing plugins until the format and CLI are stable enough that a programmatic install is reliable.

Until then:

• rig init may detect plugins from existing .claude/settings.json permission patterns and record them here.
• rig doctor reports them as not-yet-installed.
• Installation is on the user (and the agent), via Claude Code's own UI.

How rig init detects them

When rig init reads .claude/settings.json, permission entries that look like plugin namespaces (e.g. Bash(plugin:foo *)) get extracted into [plugins].required. This is heuristic; review the inferred list before committing.

What to do as a user

If rig doctor lists a plugin gap:

1. Open Claude Code in the workspace.
2. Install the named plugin from the Claude Code plugin store (or wherever the rig author points you).
3. Re-run rig doctor — the gap should clear.

There's nothing rig can do here yet beyond surfacing the requirement.

See also

• [permissions] — plugins and permissions interact.
• Troubleshoot
• MVP notes — plugin handling on the roadmap.