docs/generated/plugins.mdgenerated from code
How Agentflare works · 3 min read
Plugins
What a plugin is, and the ones that come with Agentflare.
A plugin adds one command to agentflare, like agentflare issue or agentflare action. Core af keeps files, access, and sync; everything else is a plugin, with no access but what its plugin.toml declares.
The plugins that come with af
agentflare init installs these in every project.
| Plugin | Command | What it adds |
|---|---|---|
| actions | agentflare action | Run checks, tests, and deploys on each version of main, sandboxed on your machines. |
| discussions | agentflare discussion | Discussions and decisions: threads anyone on the project reads and replies to. |
| issues | agentflare issue | Track work for people and agents: open, claim, and resolve issues, with the time and tokens each took. |
| messaging | agentflare message | Messages and mentions between the people and agents on a project. |
| secrets | agentflare secret | Secrets a check needs, like a deploy key, sealed so only the machines allowed to use them can read them. |
More plugins
These ship with agentflare, in the plugins folder beside it (~/.local/bin/plugins/ from the install line), but agentflare init doesn't install them. Install one from there, like agentflare plugin install ~/.local/bin/plugins/reviewer.
| Plugin | Command | What it adds |
|---|---|---|
| mcp | agentflare mcp | Pushes your LVCS notifications to an agent harness as MCP events, as they happen. |
| reviewer | agentflare review | Live review: another agent reads each save and sends its findings to whoever made it, who can accept a suggestion. |
Each command has its own help: agentflare action --help, agentflare discussion --help, agentflare issue --help, agentflare mcp --help, agentflare message --help, agentflare review --help, agentflare secret --help.
Add a plugin
A plugin is a directory holding its plugin.toml, which names the command it adds and the access it needs. Install it from that directory:
1agentflare plugin install ./my-plugin2agentflare plugin listInstalling gives the plugin a key of its own and exactly the access its plugin.toml lists. When it acts for you, it can do only what you can, and its saves read as yours via the plugin, like gabe via issues.
A plugin runs on your machine and reaches af only through it. One that runs on another computer, like a bridge to another service, needs --allow-remote <role> at install, naming a role its plugin.toml declares.
Not yet: installing a plugin straight from another project or from a link. Today it's a directory on your machine.
agentflare plugin upgrade and agentflare plugin remove, which takes its access back, are in the CLI reference, with every flag.
The af plugins for Claude Code and OpenCode are something else: they plug af into those coding agents. The Agent guide says how to set them up.