code-yeongyu/oh-my-openagent

[Feature]: Add Volcano Engine as a configurable websearch provider

Aperta

#2692 aperta il 19 mar 2026

 (1 commento) (0 reazioni) (1 assegnatario)TypeScript (4692 fork)batch import
enhancementhelp wantedtriage:feature-request

Metriche repository

Star
 (57.825 stelle)
Metriche merge PR
 (Merge medio 1g 13h) (641 PR mergiate in 30 g)

Descrizione

Prerequisites

  • I will write this issue in English (see our Language Policy)
  • I have searched existing issues and discussions to avoid duplicates
  • This feature request is specific to oh-my-opencode (not OpenCode core)
  • I have read the documentation or asked an AI coding agent with this project's GitHub URL loaded and couldn't find the answer

Problem Description

Summary

Add Volcano Engine's Web Search API (Volcano Ark) as a third provider option alongside Exa and Tavily.

Motivation

Now that websearch is configurable between Exa and Tavily (#1371), it would be natural to extend the provider list further. Volcano Engine is ByteDance's enterprise AI cloud platform and offers a dedicated Web Search API through Volcano Ark that is well-suited for agent use cases — including structured results, citations, and coverage of real-time data categories like weather, flights, and local services.

Implementation notes

Proposed Solution

Following the same pattern as the existing Exa/Tavily toggle:

{
  "websearch": {
    "provider": "volcengine", // "exa" | "tavily" | "volcengine"
    "volcengine": {
      "api_key": "${VOLCENGINE_API_KEY}"
    }
  }
}

Alternatives Considered

Workaround today: disable the built-in websearch MCP via disabled_mcps and wire up a custom Volcano Engine MCP in .mcp.json. Works, but bypasses the unified provider config.

Doctor Output (Optional)

Additional Context

No response

Feature Type

Configuration Option

Contribution

  • I'm willing to submit a PR for this feature
  • I can help with testing
  • I can help with documentation

Guida contributor