Skip to content

v0.0.0

Choose a tag to compare

@github-actions github-actions released this 11 Nov 13:05
· 37 commits to master since this release
v0.0.0
8f8c034

[0.0.0] - 2026-11-10

Added

  • opencode.icons and opencode.vendor, with assets/icon.svg, icon-128.png and icon-256.png from the family icon kit, the three exports and files entries, and the icons stage of npm run check.
  • An actionlint stage, and an actionlint job in CI.
  • One typed code table, src/codes.ts, with a test that fails when a code in src is missing from it, or when a README or guide table drifts from it.
  • A test that parses every example in docs/scripting.md and the README: the method, the location header, the strict envelope and the tool's own fields.

Changed

  • Each Tavily skill's first line says how to sign in when the tools are absent: /connect, or on Jelly jelly_connection_request.

  • Every tool is allowed by default. The generated block allows the five tools and the tavily_* namespace, so a tool Tavily adds later runs at once. The Jelly declaration's tools are all allow. Restrict it with access, with an agent's own rules, or with a rule per tool; the README's Permissions section, docs/configuration.md and SECURITY.md say what an all-allow default means and how to restrict it.

  • The access option, "all" (the default), "ask-changes" and "read-only" (there is no earlier option to map). All five tools only read, so the value decides what a tool Tavily adds later does: run, ask or be denied. It generates the default rules, and status and the dialog show it.

  • The host stage runs the host suite on every tested OpenCode SDK, 2.2.3, 2.2.4, 2.2.5 and 2.2.6: each release but the dev pin is installed from npm outside the lockfile into a temp folder, and the stage fails when a release did not run, as it does in CI. The pack stage keeps running every tested stock binary.

  • docs/scripting.md carries the family's envelope, location section, unload note, result wording and refusal table, word for word, and says which of UPSTREAM_ERROR's two next steps applies.

  • tools RPC v2: every known tool is scriptable under a prior explicit allow. tavily.web.tools keeps one method per known tool, each with its class (read for all five), and resolves the rule before dispatch: only an allow runs, and an ask is refused with no prompt and no tool call. describe reports each method's class, and — given a session — that session's permission, plus any live tool this plugin does not classify. A saved "Always allow" approval no longer authorizes an ad-hoc script: a script's grant is a rule in the agent's or the session's config, or a Jobs jobs_run_script run session. opencode api callers must send -H "x-opencode-directory:$PWD", or the call reaches the service's default location and fails rpc.unavailable. Tavily's error-object handling is applied to a script's result by the same shapeResult the model's hook uses.

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 and 2.2.6, and runs on macOS or Linux. A later 2.2 release starts and is reported as untested.
  • 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.