Repository navigation
v1.0.1
First prebuilt npm release for OpenCode V1
This historical release uses the OpenCode V1 plugin API. Its installation baseline was OpenCode 1.18.31; it does not support the V2 plugin API, despite the original manifest's unbounded >=1.18.0 host range.
Install this version
opencode plugin -g opencode-tui-context@1.0.1The explicit version preserves this historical release. To replace an existing package entry with 1.0.1 while keeping tuple options, append --force. Restart OpenCode and open the sidebar. No source checkout, Bun installation, or compilation is required.
For manual installation, download opencode-tui-context-1.0.1.zip and extract the included directory. Keep package.json and dist/tui.js together. Add the directory to the plugin array in tui.json, using an absolute path or a path relative to that configuration file. For example, after placing it in local-plugins/ beside tui.json:
{
"plugin": ["./local-plugins/opencode-tui-context"]
}English guide · 中文指南 · 日本語ガイド
Changes
- First npm distribution with a prebuilt TUI entrypoint and no runtime dependencies.
- Matching npm and manual-install ZIP contents, with
SHA256SUMSfor both attached archives. - Ubuntu and Windows CI, checked packaging, and a version-tag release workflow.
- Multilingual installation, configuration, troubleshooting, and maintainer documentation.
Validation recorded at release
The source passed type checking, all 72 tests, and archive validation on Ubuntu and Windows. On Windows with OpenCode 1.18.31, both the then-current unversioned npm command and an explicit @1.0.1 installation succeeded with fresh isolated configuration and caches. OpenCode wrote the correct tui.json entry, loaded the package from npm, and reported it enabled and active. The installed bundle matched the CI archive, custom options were read correctly, and both runs exited without WARN/ERROR log entries.
No model calls were made. This established installation and activation, not live-conversation rendering. The initial npm publication used the exact verified main-branch CI archive and did not carry GitHub Actions OIDC provenance.
The registry served the Chinese README and correct installation metadata. GitHub documentation and the preview SVG were reachable. The npm website's visual rendering was not verified because its Cloudflare challenge blocked automated access. These are the original release's validation limits; updating this description does not change the package or assets.