OpenClaw brings search provider configuration and live API verification into settings UI

OpenClaw contributors submitted PR #154135 on September 21, 2026, overhauling web search configuration by moving search provider setup and connection verification directly into the Settings user interface. Previously, configuring search backends like Brave Search, Tavily, Google Serper, or DuckDuckGo required manually editing raw JSON configuration files in the agent directory. When operators entered invalid API keys, misconfigured rate limits, or pointed to expired endpoints, the errors only surfaced mid-run during autonomous tool execution, abruptly crashing active multi-step workflows. PR #154135 introduces dedicated provider fields with an interactive 'Verify Search' action in Settings that executes a live test query against the chosen API and validates schema responses before persisting credentials. Concurrently, issue #154220 reports a severe Windows installer regression introduced in release 9.5: running 'openclaw gateway install --force' under global npm installations writes a broken schtasks command script that fails to launch the background gateway. In tandem, PR #153573 resolves issue #153543 by fixing a cross-channel routing bug in heartbeat tasks where failure notices were sent to the channel owner of the previous task rather than the active task's designated owner.

The facts

- PR #154135 implements interactive search provider configuration and live API verification directly in OpenClaw's Settings interface. - Enables operators to test credentials and network connectivity for Brave, Tavily, and Serper before starting autonomous workflows. - Prevents mid-turn tool crashes caused by syntax errors in hand-edited JSON files or expired third-party search credentials. - Issue #154220 reveals that openclaw gateway install --force generates a malformed schtasks gateway.cmd file on Windows npm-global setups. - PR #153573 fixes cross-channel heartbeat failure notifications from misrouting error alerts to the wrong channel owners.

Why it matters

Web search is a frontline external dependency for autonomous coding and research agents. Delegating credential validation to runtime tool execution guarantees that API key typos, billing exhaustion, or provider outages manifest as catastrophic turn failures after compute and reasoning tokens have already been spent. Embedding live connection verification at configuration time shifts failure discovery to the operator setup phase. Concurrently, ensuring that Windows background service scripts generate cleanly and that heartbeat alerts reach the correct channel owner preserves operational containment across diverse host environments.

Current

Inspected on 2026-09-21. The OpenClaw stable-channel baseline is v2026.9.5 published 2026-09-19T01:55:23Z. The primary source was open (not merged) when captured. Mainline merges, open proposals and packaged releases are distinct availability states; the release baseline does not establish that a proposal has shipped.

Evidence

Primary evidence: openclaw/openclaw PR #154135 (https://github.com/openclaw/openclaw/pull/154135). Supporting context: openclaw/openclaw issue #154220 (https://github.com/openclaw/openclaw/issues/154220); openclaw/openclaw PR #153573 (https://github.com/openclaw/openclaw/pull/153573). The source bodies and linked context were inspected. Test results quoted from contributors remain attributed reports, not independently reproduced experiments.

Operator take

Configuration verification must be active and pre-flight rather than passive and post-failure. Tooling platforms that force operators into manual configuration file edits without validation are inviting preventable runtime outages. Teams managing OpenClaw deployments should mandate pre-flight API verification for all external search providers. In addition, administrators running OpenClaw on Windows environments should inspect existing scheduled task definitions to ensure gateway background daemons are executing legitimate binaries rather than failing silently on broken command scripts.

Caveat

PR #154135 is currently an open pull request under review and has not yet been integrated into a tagged production release. The Windows gateway installer defect in issue #154220 remains unpatched in v2026.9.5, requiring manual task creation in Windows Task Scheduler until an official installer fix is cut.