Manage plugins

Inspect what Red loaded

red --runtime-files
red --self-check
red plugin list

--runtime-files shows visible plugins and themes with their source. --self-check reports the activation status of bundled plugins. red plugin list lists installed external packages.

Install a package

red plugin catalog
red plugin install --catalog go-language
red plugin install owner/repository
red plugin install --path ~/code/my-red-plugin

Catalog packages use immutable release archives with recorded checksums. GitHub and local-path sources remain explicitly unreviewed. Installing a package never grants implicit approval to execute a native Tree-sitter grammar.

Enable, update, or remove a package

red plugin disable replay
red plugin enable replay
red plugin update replay
red plugin update --all
red plugin remove replay
red plugin remove replay --purge

Ordinary removal preserves the plugin's namespaced data for a later reinstall. --purge deletes that data as well. Failed updates leave the previous installation active.

Customize a bundled plugin

red --eject plugins/fidget.hk

The copy in your configuration directory shadows the bundled file. Remove the copy to return to the version shipped with Red.

Plugins that spawn processes need an explicit allowlist:

[plugin_permissions.project_search]
process = ["rg"]