Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Config validation error: tools.web.search.brave no longer valid after update [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#59931•Fetched 2026-04-08 02:38:41
View on GitHub
Comments
2
Participants
3
Timeline
2
Reactions
1
Author
bvoorheesbvoorhees
Participants
BorClawBorClawbvoorheesbvoorheesmartingarramonmartingarramon
Timeline (top)
commented ×2

After updating OpenClaw, the gateway fails config validation because tools.web.search now has additionalProperties: false and the brave sub-key is no longer in the schema.

Error Message

  1. Gateway fails to start / reports config validation error

Root Cause

After updating OpenClaw, the gateway fails config validation because tools.web.search now has additionalProperties: false and the brave sub-key is no longer in the schema.

Fix Action

Workaround

Manually delete the brave key from tools.web.search in ~/.openclaw/openclaw.json.

Code Example

"tools": {
  "web": {
    "search": {
      "provider": "brave",
      "apiKey": "...",
      "brave": {
        "mode": "llm-context"
      }
    }
  }
}
RAW_BUFFERClick to expand / collapse

Description

After updating OpenClaw, the gateway fails config validation because tools.web.search now has additionalProperties: false and the brave sub-key is no longer in the schema.

Steps to Reproduce

  1. Have a config with:
"tools": {
  "web": {
    "search": {
      "provider": "brave",
      "apiKey": "...",
      "brave": {
        "mode": "llm-context"
      }
    }
  }
}
  1. Update to a version that removed the brave sub-key from the schema
  2. Gateway fails to start / reports config validation error

Expected Behavior

A config migration should strip or relocate the deprecated brave key automatically on update, rather than requiring the user to manually edit openclaw.json.

Workaround

Manually delete the brave key from tools.web.search in ~/.openclaw/openclaw.json.

Environment

  • OpenClaw 2026.3.13 (stable)
  • macOS 26.3.1 (arm64)
  • Node 25.4.0

extent analysis

TL;DR

Manually removing the deprecated brave key from tools.web.search in the openclaw.json configuration file is the most likely fix.

Guidance

  • Verify that the brave sub-key is indeed the cause of the config validation error by checking the error message or logs for specific references to additionalProperties: false.
  • Manually edit the openclaw.json file to remove the brave key, as described in the provided workaround.
  • After removing the brave key, attempt to restart the gateway to see if it resolves the config validation error.
  • If manual removal is not feasible, consider automating the removal process through a script or configuration migration tool.

Example

"tools": {
  "web": {
    "search": {
      "provider": "brave",
      "apiKey": "..."
    }
  }
}

This example shows the updated openclaw.json configuration with the brave key removed.

Notes

The provided workaround is specific to the described environment (OpenClaw 2026.3.13, macOS 26.3.1, Node 25.4.0) and may not apply to other versions or configurations.

Recommendation

Apply the workaround by manually removing the brave key, as it is a straightforward and effective solution to the config validation error.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#response parsing#generation error#database connection#vector store

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Config validation error: tools.web.search.brave no longer valid after update [2 comments, 3 participants]