tools: websearch unexpectedly switches between Exa and Parallel providers

Summary

The built-in websearch tool unexpectedly routed adjacent searches through different providers, showing one invocation as Exa Web Search and another as Parallel Web Search. No Exa, Parallel, or search-provider integration is configured by the user.

This makes built-in web-search behavior unpredictable and suggests that provider selection or tool routing is occurring without explicit configuration.

Environment

• opencode version: opencode2 v0.0.0-next-16234
• OS: Linux omarchy 7.1.4-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 18 Jul 2026 17:30:57 +0000 x86_64 GNU/Linux
• Terminal: TERM=xterm-256color, COLORTERM=truecolor, TERM_PROGRAM unset
• Shell: /usr/bin/bash
• Install/channel: next
• Active plugins: ~/.opencode/plugins/graphify.js; no plugins configured in ~/.config/opencode/opencode.json

Reproduction

1. Start the OpenCode V2 TUI.
2. Ask a documentation question that requires web research, such as:
   are there now any docs on plugins for https://opencode.ai/v2/docs/build/plugins creating a ui plugin? something that accepts opentui or three.js or customizing look and feel of opencode? i.e. i want to maybe change how diff viewer looks?
3. Observe the web-search tool calls displayed in the TUI.
4. In the reported session, one call appeared as Exa Web Search, while the next appeared as Parallel Web Search.

Expected Behavior

The built-in websearch capability should use the expected native search implementation consistently, or provider routing should be explicitly configured and clearly documented. It should not silently switch between third-party search providers across adjacent calls.

Actual Behavior

Two adjacent calls made through the built-in websearch tool were displayed with different implementations:

• Exa Web Search "site:github.com/sst/opencode diff viewer TUI plugin UI customization OpenTUI"
• Parallel Web Search "site:github.com/sst/opencode plugins UI TUI custom diff viewer"

There is no Exa, Parallel, or search-provider configuration in the user's OpenCode configuration.

Additional Context

• A screenshot showing the two differently labeled calls is available.
• The behavior has been observed once; consistency is not yet known.
• No workaround has been tested.
• ~/.config/opencode/opencode.json contains no search-provider or Exa/Parallel configuration.