Extensibility
Plugin system
The plugin registry gives Jarvis a modular place to describe installed capabilities and future automation packs.
Built-in plugins
| Plugin | Capability |
|---|---|
| Visual Browser Operator | Playwright automation, browser history, DOM summaries. |
| Desktop Control | Verified app launch, app close, system actions. |
| Coding Agent | Project analysis, website generation, build scripts. |
Local manifests
Local plugins are JSON manifests stored in `backend/plugins/installed`. They can be enabled, disabled, and listed by the backend.
{
"id": "my-tool-pack",
"name": "My Tool Pack",
"description": "Custom commands for my workflow.",
"enabled": true,
"commands": ["open_workspace", "run_tests"]
}Design goals
- Keep tools modular.
- Make capabilities discoverable in the UI.
- Allow future marketplace-style installation.
- Keep permission checks centralized instead of inside each plugin.
Future expansion
The next layer can add plugin command execution contracts, schema validation, signed plugins, and per-plugin permissions.
Created by Jojin John
JX Jarvis is created by Jojin John.
