Python
Point the web_search_provider notes at Settings > Customization
Rohit C Prasad535467a4d256
diff --git a/coworker/config.py b/coworker/config.pyindex 042a6de0..02eb4a32 100644--- a/coworker/config.py+++ b/coworker/config.py@@ -91,6 +91,8 @@ class Config:port: int = 8765# Web search provider: "duckduckgo" (keyless default) | "you" (keyless, optional key)# | "tavily" | "brave" | "serper" | "exa" | "firecrawl" (the keyed ones need a key).+ # Settings ▸ Customization writes the choice (and the keys) to the secret store's+ # `web_search:default` profile, which wins over this value.web_search_provider: str = "duckduckgo"# OpenWorker Cloud (sign-in + managed connectors). Config, never constants:# dev/staging/BYO-VPC deployments point these at their own instances.diff --git a/docs/config.example.toml b/docs/config.example.tomlindex ea35d0ec..7498e8dd 100644--- a/docs/config.example.toml+++ b/docs/config.example.toml@@ -20,8 +20,10 @@ max_iterations = 12 # max model<->tool iterations per turn before stopp# COWORKER_REASONING_EFFORT.# Web search backend: "duckduckgo" (keyless, default) | "you" (keyless, optional key)-# | "tavily" | "brave" | "serper" | "exa" | "firecrawl"-# (the keyed ones need an API key, set in the app's Settings or secret store).+# | "tavily" | "brave" | "serper" | "exa" | "firecrawl". The usual place to pick one is+# the app's Settings ▸ Customization ▸ Web search, which also keeps each service's API+# key in the secret store; a choice made there wins over this line. Keys can also come+# from the environment as {NAME}_API_KEY (e.g. BRAVE_API_KEY).web_search_provider = "duckduckgo"# Commands auto-allowed without an approval prompt (prefix match).