pi-plugins-control

Manage persistently configured Pi extensions from an interactive /manage-exts screen.

Install

Install globally through Pi:

pi install npm:pi-plugins-control

For project-local installation:

pi install -l npm:pi-plugins-control

Restart Pi or run /reload after the initial installation. Then open the manager:

/manage-exts

Controls

• Type to search by extension name.
• Use Up/Down to navigate.
• Press Space or Enter to switch between enabled and disabled.
• Press Escape to save all changed toggles and reload Pi once.

Closing an unchanged list does not reload Pi.

Scope

The manager lists persistently configured and auto-discovered Pi extensions, including extensions disabled by Pi filters.

• User extensions are written to global Pi settings.
• Project extensions are written to project-local Pi settings.
• The plugin manager is always enabled and locked in its own list.
• Direct local extension-file package sources and bare local-directory fallback extensions remain visible but locked. Pi 0.83.0 cannot safely toggle those forms with package filters.
• Local packages with a pi manifest or a conventional extensions/ directory remain toggleable.
• Temporary extensions passed with pi -e are not listed because Pi does not expose a complete temporary-extension catalog through its public API.

This package does not install, remove, or update packages, and it does not manage skills, prompts, or themes.

Compatibility

Resolver behavior is verified against Pi 0.83.0. The extension uses public Pi APIs, but other Pi versions have not yet been live-tested.

Recovery and advanced configuration

The manager uses the same exact include/exclude filter model as Pi's configuration system. If an extension or this package cannot load, use:

pi config

Use Tab in pi config to switch between global and project settings, then repair the relevant extension filter. You can also edit the corresponding settings.json after backing it up.

Development

npm install
npm test
npm run typecheck
npm pack --dry-run