v0.1.9

Added

• The plugin now updates itself, the way @tarquinen/opencode-dcp does. On every boot the server entry checks npm once (10 s timeout, a failed check is ignored). When a newer release exists and the plugin came from npm with an unpinned spec, opencode reinstalls the latest on its next start, a toast says "Updated … Restart opencode to finish.", and the stats line shows an ↑ <version> badge until then. Repo checkouts and pinned specs are never touched. The check runs even with stats: "off" because it is plugin infrastructure, not stats.
• tui: "ensure" plugin option (off by default). The TUI host of opencode 1.18+ reads its plugin list only from tui.json, so an npm install left the stats line dead until a manual edit. With the option on, the server entry registers the TUI entry itself: it patches the tui.json opencode actually reads ($OPENCODE_TUI_CONFIG when set, else the global one), adds the spec only when it is missing, keeps comments and existing entries (like ["…", { "stats": "off" }]) intact, backs up the file and writes it atomically. Dev installs write nothing. The change lands on the next TUI launch. jsonc-parser is a new dependency.

Fixed

• The stats line no longer stays on the dashes placeholder when the TUI starts with no open session (a fresh start, not a restored one). The slot renders once at mount, so the session id used to stay empty for the whole run; the TUI plugin now falls back to api.route.current and picks up the session after it opens.

Changed

• Documentation: opencode plugin @srnoob2570/opencode-ollama-cloud is the primary install route (it registers the provider and TUI entries in one command). Manual tui.json edits and the new tui: "ensure" option are the alternatives.

Full changelog: v0.1.8...v0.1.9