openclaw - 💡(How to fix) Fix Bug: commands.native and commands.nativeSkills reject boolean false despite schema allowing it [1 comments, 1 participants]

Summary

The commands.native and commands.nativeSkills configuration fields reject boolean false values despite the JSON schema explicitly allowing boolean types (in addition to the string "auto").

Version

2026.4.15

Reproduction Steps

1. Set commands.native: false in openclaw.json
2. Set commands.nativeSkills: false in openclaw.json
3. Restart the gateway with launchctl load ~/Library/LaunchAgents/ai.openclaw.gateway.plist

Expected Behavior

Both native: false and nativeSkills: false should be accepted as valid configuration values, since:

• The JSON schema is defined as: anyOf([{ type: "boolean" }, { type: "string", const: "auto" }])
• The Zod schema allows: z.union([z.boolean(), z.literal("auto")]).optional()
• Both boolean true and boolean false should be valid

Actual Behavior

The validator rejects both fields with:

Invalid input (allowed: true, false, "auto")

However:

• Boolean true IS accepted ✓
• Boolean false IS rejected ✗
• String "auto" IS accepted ✓

Error Messages

From gateway logs:

config reload skipped (invalid config): 
- commands.native: Invalid input (allowed: true, false, "auto")
- commands.nativeSkills: Invalid input (allowed: true, false, "auto")

Impact

• Users cannot disable auto-registration of native slash commands
• This prevents managing the 100 slash command Discord API limit
• The only workaround is using boolean true and managing commands through manual deletion

Workaround

Use native: true and nativeSkills: true (enabled), then manually delete unused slash commands to stay under Discord's 100 command limit.

Related Issues

• Issue #63947 - Similar schema validator bug with ComfyUI config keys
• Issue #18635 - Signal groups configuration schema validation bug
• Issue #14998 - Schema rejects valid JSON Schema keys