Documentation
Plugins
Plugins extend Agent Zero with Web UI surfaces, tools, settings, scripts, hooks, model providers, and integrations. This page stays practical: how to manage them, where local plugins live, and how to stay safe.
Manage Plugins
Open Plugins from the sidebar. You can enable, disable, configure, and inspect installed plugins from the list.
Use advanced activation only when a plugin should be enabled for a specific scope instead of globally.
Plugin Hub
Use the Plugin Hub to browse community plugins, inspect details, and install trusted additions.
User Plugins Live Under usr/plugins
Put local plugins in /a0/usr/plugins/<plugin_name>/. Do not edit root plugin folders for custom work unless you are intentionally developing Agent Zero itself.
Rule of thumb: whatever is in /a0/usr, if it has the same ID as something in root /a0, the user-owned version replaces or extends the root version.
After adding or changing Web UI extension files, refresh the page so the Web UI extension list is rebuilt.
Build A Small Local Plugin First
Start with a tiny local plugin before learning every plugin surface. A good first plugin has no external dependencies, no backend API, and one visible UI behavior.
/a0/usr/plugins/unread_dot/
├── plugin.yaml
├── README.md
├── extensions/
│ └── webui/
└── webui/Follow the Create a Small Plugin guide for a complete first example.
Security Basics
- Install plugins only from sources you trust.
- Review plugins that run shell commands, install packages, read secrets, or call external services.
- Keep credentials in Secrets or project secrets, not plugin source code.
- Use plugin review before publishing or sharing a plugin.
When You Need Internals
For source-linked architecture, extension hook order, API handler details, and publishing internals, use DeepWiki for Agent Zero. The website docs keep the user journey clean on purpose.