← ClaudeAtlas

create-codevisor-pluginlisted

Create, install, and iterate on a Codevisor plugin — a local HTTP server whose panes render inside Codevisor on every connected device. Use when the user asks for a new pane, panel, viewer, dashboard, or tool inside Codevisor (e.g. "make me a pane that shows X"), or asks to build or modify a Codevisor plugin.
851-labs/codevisor · ★ 9 · AI & Automation · score 71
Install: claude install-skill 851-labs/codevisor
# Create a Codevisor plugin A plugin is a folder with a manifest and any program that serves HTTP on `$PORT` (loopback). Codevisor supervises the process, proxies pane traffic to it, and renders its pages in webview panes on every client (macOS, iOS, remote). You can scaffold, install, and show a working pane in under a minute. ## Workflow 1. **Scaffold** a folder with `codevisor-plugin.json` + a single-file server (templates below). Prefer zero dependencies. 2. **Install it (dev mode)** so Codevisor discovers it: - Tool: `plugins.link` with the folder's absolute path, or - CLI: `codevisor plugin link <absolute-path>` 3. **Open a pane** so the user sees it immediately: use the `workspaces.open_plugin_pane` tool (or tell the user it's on the New Tab page). Pane records need `providerId: "plugin:<pluginId>"` and the pane `type`; do not persist icon metadata in the workspace record. 4. **Iterate**: edit files → `plugins.restart` → open panes reload automatically on every connected device. HMR-capable dev servers (Vite etc.) also work without restarting, since WebSockets are proxied. Read runtime logs via the plugin's output terminal (Settings → Plugins → Show Output) when something fails. ## Manifest — `codevisor-plugin.json` ```json { "protocolVersion": 1, "id": "<owner>.<name>", "name": "My Plugin", "description": "One line about what it does", "version": "0.1.0", "iconPath": "/assets/icon.svg", "panes": [{ "type": "main", "titl