pub struct SearchSection {
pub provider: Option<String>,
pub api_key: Option<String>,
pub jina_key: Option<String>,
}Expand description
[permissions] section. Wire-compatible with
crate::permissions::PermissionsConfig but lives here so config
loading does not couple to that crate.
[search] section. Web search provider configuration.
Falls back to RECURSIVE_WEB_SEARCH_PROVIDER, RECURSIVE_WEB_SEARCH_API_KEY,
and RECURSIVE_WEB_SEARCH_JINA_KEY env vars respectively.
Example:
[search]
provider = "brave"
api_key = "BSA..."
jina_key = "jina_..."Fields§
§provider: Option<String>Search provider name: brave, tavily, serper, bocha, bing.
Corresponding env var: RECURSIVE_WEB_SEARCH_PROVIDER.
api_key: Option<String>API key for the chosen search provider.
Corresponding env var: RECURSIVE_WEB_SEARCH_API_KEY.
⚠️ Like provider.api_key, storing search keys in config.toml
means an agent with run_shell can cat them out. Consider
using the env var or set-secret instead.
jina_key: Option<String>Optional Jina AI Search API key for higher quota.
Corresponding env var: RECURSIVE_WEB_SEARCH_JINA_KEY.