Skip to content

v0.0.5

Choose a tag to compare

@github-actions github-actions released this 18 Nov 18:42
· 5 commits to master since this release
2c98163

[0.0.5] - 2026-11-18

Changed

  • Admits OpenCode 2.3.1 and 2.3.2: TESTED_HOSTS in src/host-version.ts is 2.2.3 to 2.3.2, which the host, pack
    and stock stages and CI read.
  • Tested on OpenCode 2.2.3, 2.2.4, 2.2.5, 2.2.6, 2.2.7, 2.3.0, 2.3.1 and 2.3.2. The supported range is unchanged
    (>=2.2.3 <2.4.0).

Known limits

  • Five tools. The plugin knows the five Tavily tools. A tool Tavily adds later is not classed by the plugin: the access option decides whether it runs, asks or is denied, and /tavily-status counts it as unknown.
  • Research and crawl cost the most. Research takes minutes with no progress shown, and a call stops after 15 minutes. Crawl reads up to 50 pages by default. The plugin sets no spending limit: each call spends Tavily credits as the tool does.
  • No retries. A failed call returns UPSTREAM_ERROR with its next step. The plugin does not retry it.
  • Web content is not trusted. A page can carry instructions, and nothing asks by default. The tavily skill tells the model not to follow them, but that is a rule for the model, not a guard in the plugin.
  • A shell key does not reach the server. A TAVILY_API_KEY exported only in a terminal does not reach a running OpenCode server. See Sign in.
  • Hosts and platforms. The plugin is tested on 2.2.3, 2.2.4, 2.2.5, 2.2.6, 2.2.7, 2.3.0, 2.3.1 and 2.3.2, and runs on macOS or Linux. A later 2.2 or 2.3 release starts and is reported as untested.
  • Web search needs the key. Only a Tavily API key serves OpenCode's websearch; signed in with a Tavily account alone, it uses Tavily's keyless access.
  • Jelly. The settings declare their choices and bounds, which only a Jelly that includes app#1301 reads; an older Jelly refuses the plugin's declaration.
  • Updates are not automatic for a Git install, and opencode plugin update and opencode plugin check do not work on one: to move to a newer release, remove the old entry and add the new tag.