Plugin & Tool Catalog
Every built-in plugin and the tools it exposes to the agent — 38 plugins, ~291 tools.
This is the complete catalog of tools the agent can call. Each plugin (in
MeghaOS) registers one or more tools; the LLM picks the right tool for your
request (ranked by a relevance index — see the Plugin System). You
rarely call these by name — you describe what you want in /chat and the agent routes to
the tool. The example prompts show typical phrasings.
Counts reflect the built-in capabilities. Auto-created plugins (written at runtime by self-extension) and MCP servers add more tools on top of these.
Prefer one page per tool? The Tool Index has a dedicated page for every
tool — with its full parameter table, an example chat prompt, a workflow-step snippet, and
a POST /execute_tool call you can copy.
Platform availability
Capabilities are available per edition:
- All editions — works on the Linux DE, the Linux OS, and the macOS app.
- macOS — uses native Apple apps; available in the macOS edition (the Communication Apple integrations and every native macOS group below).
- Linux (DE & OS) — desktop/compositor-level controls (window management, session power).
Web & research
Communication & messaging
Productivity (native macOS)
Files & documents
Finance, analysis & compliance
System & hardware control
Audio, display, network, and Bluetooth controls work on all editions. Window management
and session power (power_manager, window_manager) are Linux (DE & OS) features — on
macOS those are handled by the OS itself.
Vision, screen & computer control
Core agents (always available)
Three agents are eviction-protected — never unloaded — so the system can always plan, control the OS, and extend itself:
| Agent | Role |
|---|---|
| self-extension | Writes new plugins at runtime (Creating Plugins) |
system | Core OS-level the core system layer — launch_app, set_volume, set_brightness, toggle_wifi, clipboard, screenshots, downloads, archives, file ops |
| Browser automation | Browser automation |
Extending the catalog
Add a Python file to the built-in capability set and the agent picks it up.
If a workflow needs a missing tool, self-extension writes it on the fly.
Register external tools in Settings (Model Context Protocol).
The UI side of the catalog — every renderable component.