Skip to content
    ↑↓ select↵ openesc close
    ranjithrajv

    Browser

    opencode-plugin-browser·v1.0.0-alpha.4·Tools & Commands

    Sidebar section listing OpenCode plugins with installed/uninstalled status, below MCPs and Skills.

    GitHub stars

    0

    Monthly installs

    33,623

    7k in 7 days

    Composite score

    47.8

    Multi-signal model

    Last commit

    7 days ago

    2026-09-27

    Install and configure

    opencode.json

    Writes to this project's opencode.json — applies to this repository only.

    opencode.json

    {
      "$schema": "https://opencode.ai/config.json",
      "plugin": ["opencode-plugin-browser@1.0.0-alpha.4"]
    }

    OpenCode loads npm dependencies through its embedded runtime on startup and caches them locally — no manual global install needed.

    CI npm License: AGPL-3.0

    Note: this plugin is published on npm as opencode-plugin-browser — the original project name, kept for package continuity. The repository and README title use opencode-plugin-manager; both refer to the same package. Install it by the npm name shown below.

    An OpenCode sidebar section listing plugins with installed/uninstalled status — placed below the built-in MCP section and the Skills list, mirroring the built-in sidebar widgets.

    What it shows

    • Installed plugins from the plugin registry (same list opencode2 plugin list shows; built-ins excluded) with their activation state: ✓ active, ✗ failed, ○ inactive.
    • LOCAL group mixes registered plugins (✓ … installed) with workspace plugin projects discovered by scanning the workspace root for sibling directories whose package.json depends on @opencode/plugin (private monorepo roots and shared libraries excluded) — those show dimmed with ○ … uninstalled and a [+] to register them, same status column as everything else.
    • Built-in plugins are listed by default (group collapsed to keep the sidebar short) and can be hidden/shown with /plugins-builtins — a view toggle only, persisted; built-ins always run. They can't be disabled individually: the runtime has no per-built-in disable mechanism — the only switch is the all-or-nothing OPENCODE_DISABLE_DEFAULT_PLUGINS env var, whose state the widget shows when the BUILT-IN group is visible. Per-built-in disable requires upstream support in OpenCode's plugin host.
    • Plugin descriptions — the registry exposes no human metadata, so the plugin ships its own catalog (builtins.ts): curated descriptions for well-known built-ins plus per-category generation (provider.*, tool.*, config.*, websearch.*). Click any row to inspect its details.

    Collapsed header shows PLUGINS (installed/total); more than two entries collapse, click (or expand) to list them — same interaction as the built-in MCP/Skills sections.

    Install

    Published on npm.

    Automatic (recommended) — add it to your OpenCode config (~/.config/opencode/opencode.json) and it installs on startup:

    { "plugins": ["opencode-plugin-browser"] }
    

    Manual:

    npm install opencode-plugin-browser
    

    Restart the TUI (or opencode2 service restart) after changing the config.

    Prerequisites

    • OpenCode V2.0.3 or newer (plugin API is beta). 2.0.3 is the floor: earlier 2.x releases ship no ./tui subpath export, so the TUI entrypoint cannot resolve @opencode/plugin/tui.

    Placement: appends to sidebar.content (below MCP/Skills). If you use multiple sidebar plugins, order in plugins controls stacking.

    Remove

    Remove the plugin's entry from the plugins array in opencode.json.

    Data sources

    • Plugin registry: client.plugin.list() (activation state included)
    • Workspace scan: sibling directories of the current location, one package.json read per candidate; result is cached through opencode-plugin-kit's createCachedStore so the sidebar restores instantly after a TUI restart.

    License

    GNU Affero General Public License v3.0 — see LICENSE.

    Similar plugins