crunes-use-plugin

Using Plugins

Discover plugins

crunes -p marketplace browse              # list all plugins from all configured sources
crunes -p marketplace search <query>      # search by name or keyword
crunes -p marketplace list                # list configured marketplace source URLs

Install a plugin

crunes -p plugin install <marketplace>@<plugin>

Example:

crunes -p plugin install official@git-helper

Install adds the plugin to the global registry (~/.crunes/plugins.json) and enables it in .crunes/config.json for the current project. You will be prompted to review and consent to the plugin's declared permissions.

Manage installed plugins

crunes -p plugin list                     # all installed plugins + enabled status per project
crunes -p plugin enable <plugin>          # add to this project's enabled list
crunes -p plugin disable <plugin>         # remove from this project's enabled list
crunes -p plugin update                   # update all installed plugins
crunes -p plugin update <plugin>          # update one plugin
crunes -p plugin uninstall <plugin>       # remove globally

On update, only new or escalated permissions trigger re-consent — not the full permission set.

Use plugin rune keys

crunes -p run my-plugin:rune-key          # CLI
crunes -p run my-plugin:rune-key arg1     # with positional arg

In hook tokens (resolved automatically in prompts):

$$my-plugin:rune-key
$$my-plugin:rune-key(arg1,arg2)
$$my-plugin:rune-key[-s section]
$$my-plugin:rune-key[-s section](arg1)

Permission model

Plugin runes run in an isolated sandbox. Each rune's permissions are declared in the plugin's plugin.json and consented to at install time. Plugin runes always get read access to their own plugin directory automatically (@plugin/**). Any additional access (project files, network, shell, env) must be declared and consented.