code-yeongyu/oh-my-openagent

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

Open

#2692 opened on Mar 19, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (57,825 stars) (4,692 forks)batch import
enhancementhelp wantedtriage:feature-request

Description

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

Contributor guide

Tech stack
typescriptnodejs
Domain
backendapisearch
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
TypeScript basicsNode.js environmentExisting websearch provider code
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
Review the existing websearch provider interface in src/mcp/websearch.ts, particularly how Exa and Tavily are implemented. Create a new Volcano Engine provider following the same pattern, using the OpenAI compatible API format. Add the provider option to the configuration schema and ensure the API key is read from environment variable. Test the integration by running the existing websearch functionality with the new provider.