Skip to content

Releases

v0.0.6

Choose a tag to compare

@github-actions github-actions released this 20 Nov 13:32
2fd4bb2

[0.0.6] - 2026-11-20

Changed

  • The tools RPC transport is source-contract's tools-rpc module, pinned to v0.2.0 and bundled into dist/index.js. src/host/tools-rpc.ts is Tavily's part of it. The vendored copy and its check-copies pin are gone.
  • The five tools spend credits, so they are not free reads. At access: "all" they run. At "ask-changes" each asks.
    At "read-only" each is denied, and a tool Tavily adds later follows the same rule. This changes what a user at
    "ask-changes" or "read-only" sees: before, all five ran without asking at either value. In Jelly the five are no
    longer read-only: a read-only helper can't use them, and at Ask before changes each asks. OpenCode's own websearch
    tool, which uses Tavily while the websearch option is on, is not affected: set "websearch": false or deny
    websearch to stop it. The plugin sets no spending limit.

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.

v0.0.5

Choose a tag to compare

@github-actions github-actions released this 18 Nov 18:42
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.

v0.0.4

Choose a tag to compare

@github-actions github-actions released this 15 Nov 18:27
97dc590

[0.0.4] - 2026-11-15

Added

  • For jelly: jelly.cost, the line jelly shows on the plugin's review before it installs: "Every search, extract,
    map, crawl and research call spends Tavily credits from the signed-in account or key. A research task costs 4-110
    credits with mini and 15-250 with pro, and a crawl reads up to 50 pages by default. The plugin sets no spending
    limit."

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 and 2.3.0, 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.

v0.0.3

Choose a tag to compare

@github-actions github-actions released this 15 Nov 12:53
96c614a

[0.0.3] - 2026-11-15

Changed

  • OpenCode 2.3 is admitted: the host range is >=2.2.3 <2.4.0 (it was >=2.2.3 <2.3.0), tested on 2.2.3, 2.2.4, 2.2.5, 2.2.6, 2.2.7 and 2.3.0.
    The host and pack stages, CI and the release's install check run every one of them. A later 2.2 or 2.3 release
    starts and status calls it untested; the HOST_UNTESTED example host is now 2.4.0.
  • Apart from the status fix below, OpenCode 2.3 needs nothing else from this plugin. It does not call the subagent tool or read session.tool.failed;
    the five tools are Tavily's MCP tools, which OpenCode runs and stops itself when the person presses Stop; and it has
    no use for the new session.fork hook.

Fixed

  • Status, /tavily-status and the /tavily dialog could report that Tavily is not the web search default right after
    OpenCode started, when it is. OpenCode applies the plugin's web search choice only when something reads its web search
    state, and on 2.3.0 nothing may have yet; status now reads that state first.

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 and 2.3.0, 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.

v0.0.2

Choose a tag to compare

@github-actions github-actions released this 14 Nov 21:10
1b51e64

[0.0.2] - 2026-11-14

Added

  • test/fixtures/live-tools.json, Tavily's tool list for a signed-in user, captured live on 14 November 2026, and a
    test that fails when the declaration and that list disagree. The declaration already matches it: 5 tools, each
    readOnly as Tavily's readOnlyHint says, each allow.

Changed

  • Jelly: the key sign-in's label is "Tavily API key" (it was "Tavily"), so the card says it is a key. docs/jelly.md
    says that only the key serves OpenCode's websearch; with the account alone, web search uses Tavily's keyless
    access. Turning the websearch setting off only stops the plugin choosing Tavily as OpenCode's web search provider.
  • The icon is Tavily's Brand Mark, unmodified, on a white rounded holding tile with clear space of its own height, used under Tavily's brand guidelines. opencode.vendor.mark is true, and the README names Tavily Inc. as the trademark owner.
  • package.json is "private": true, so nothing can be published to npm by mistake. Installs from the GitHub release
    tag are unaffected.
  • test/unit/check-icons.test.ts checks scripts/check-icons.mjs (contract revision 2) on scratch copies of this package: the family rules without opencode.vendor.mark, and the vendor's own mark, its README notice and trademark line with it.

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.
  • 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.

v0.0.1

Choose a tag to compare

@github-actions github-actions released this 13 Nov 16:50
d30c02d

[0.0.1] - 2026-11-13

Added

  • The jelly settings declare their choices: access offers Jelly's three choices, Allowed, Ask before changes and Read only, and executionTimeoutMs is declared as a whole number from 60000 to 3600000, the options parser's bounds (needs a jelly that includes app#1301).

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.
  • 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.

v0.0.0

Choose a tag to compare

@github-actions github-actions released this 11 Nov 13:05
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.