Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Gap Analysis: v2026.5.27 config keys rejected as unknown by schema

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…

Several new config keys introduced in v2026.5.27 are rejected as "unknown" by the current OpenClaw schema when applied to openclaw.json. This causes the Gateway to fail to start with "Invalid config" error.

Error Message

Several new config keys introduced in v2026.5.27 are rejected as "unknown" by the current OpenClaw schema when applied to openclaw.json. This causes the Gateway to fail to start with "Invalid config" error.

Root Cause

The OpenClaw config schema has not been updated to include new config keys introduced in v2026.5.27.

When unknown keys are present in openclaw.json, the Gateway fails to start:

Invalid config at /home/henesink/.openclaw/openclaw.json.
gateway: Invalid input

Fix Action

Fix / Workaround

Current Workaround

Workaround applies security and cron keys via jq to bypass schema validation.

Code Example

Invalid config at /home/henesink/.openclaw/openclaw.json.
gateway: Invalid input
RAW_BUFFERClick to expand / collapse

Summary

Several new config keys introduced in v2026.5.27 are rejected as "unknown" by the current OpenClaw schema when applied to openclaw.json. This causes the Gateway to fail to start with "Invalid config" error.

Affected Config Keys

The following keys from the v2026.5.27 release notes are unrecognized by the current schema:

KeyPurposeStatus
telemetry.opentelemetryOpenTelemetry LLM tracing❌ Rejected
activityEphemeral Activity tab❌ Rejected
memory.embeddingLocal embedding provider config❌ Rejected
gateway.security.*Security boundary rulesRejected initially, applied via jq
cron.maxConcurrentRunsCron concurrencyApplied via jq

Root Cause

The OpenClaw config schema has not been updated to include new config keys introduced in v2026.5.27.

When unknown keys are present in openclaw.json, the Gateway fails to start:

Invalid config at /home/henesink/.openclaw/openclaw.json.
gateway: Invalid input

Reproduction

  1. Add any new config key from v2026.5.27 to openclaw.json
  2. Run openclaw gateway
  3. Observe failure

Current Workaround

Workaround applies security and cron keys via jq to bypass schema validation.

Expected Behavior

  1. Schema should accept all documented config keys for the current version
  2. Or, unknown keys should be tolerated (doctor --fix should auto-remove, not crash)

Environment

  • OpenClaw: v2026.5.27 (27ae826)
  • Platform: Ubuntu 24.04.4 LTS
  • Node: Linuxbrew managed

References

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…

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 Gap Analysis: v2026.5.27 config keys rejected as unknown by schema