cargo agents use
Enable a plugin by name, and sync it into the workspace immediately.
Usage
cargo agents use <NAME> [--global]
cargo agents use <NAME> --remove [--global]
Options
| Flag | Description |
|---|---|
<NAME> | Plugin or crate name to enable |
--global | Enable for every workspace instead of just the current one |
--remove | Drop a previously recorded enablement instead of adding one |
Behavior
use is the durable, by-name form of consent. It records a use entry in the
[plugins] section of the user config:
[plugins]
use = [
"everywhere-plugin", # --global
{ name = "crate-a", workspace = "/home/me/my-project" }, # default
]
Then it runs a sync, so the plugin’s skills install right away rather than waiting for the next one.
Two things a use entry can enable:
- A dependency’s embedded plugin. Depending on a crate means compiling its
code, not letting its author inject agent context, so a dependency is not a
trust root — its embedded plugin stays off until you say otherwise.
useis the by-name way to say so ([plugins] auto-enableis the ahead-of-time way). - A dormant registry plugin. A plugin whose manifest names no dependency
has nothing to gate it on, so it loads dormant. A
useentry naming it is what wakes it.
Anything a configured registry already offers under a depends-on gate is
enabled by configuration — pointing config at a registry is the act of
trusting its curation — so use-ing it is a no-op and reports as such.
Enablement is not activation: use only adds to what may run. The plugin’s
own predicates still decide when it applies.
The name must resolve to something before it is recorded — a dormant registry
plugin, a workspace dependency, or a registry search hit — otherwise the
command errors and writes nothing. Use
cargo agents search to find the right name.
--remove
Removes the entry in the matching scope: without --global the entry recorded
for the current workspace, with it the unscoped one. A scope mismatch (or no
entry at all) is an error rather than a silent success. The sync that follows
reaps the plugin’s installed skills.
Example
cargo agents search widget # find it
cargo agents use widget-skills # enable it here
cargo agents status # confirm why it is on
cargo agents use widget-skills --remove