PR #49849: fix(config): change nativeSkills default from "auto" to false

• Repository: openclaw/openclaw
• Author: ademczuk
• State: closed | merged: False
• Link: https://github.com/openclaw/openclaw/pull/49849

Description (problem / solution / changelog)

What

Flips the commands.nativeSkills default from "auto" to false.

The auto default registers every installed skill as a native platform command on Discord and Telegram. That works fine with a handful of skills, but once you hit 42+ (standard bundled set plus a few ClawHub installs), Telegram's 100-command hard cap kills the gateway startup. The error looks like a network problem, so users end up debugging the wrong thing for hours.

Changing the default to false means fresh installs won't hit this wall. Existing users who want the native menus back just add one line:

{ commands: { nativeSkills: "auto" } }

Related prior work - this issue has been circling for a while:

• #6172 proposed selective native command registration (closed)
• #4292 tried a nativeSkills whitelist approach for Telegram (closed)
• #10875 spawned 7 PRs trying to deduplicate skill commands in the Telegram menu
• #22558 fixed an earlier schema default alignment issue

Changes

src/config/zod-schema.session.ts - default value in both the field schema and the factory src/config/types.messages.ts - JSDoc annotation src/config/schema.help.ts - help text now explains why it's off by default src/config/commands.test.ts - 5 new tests covering schema default + explicit override paths docs/tools/slash-commands.md - config example + explanation docs/.generated/config-baseline.json + .jsonl - regenerated CHANGELOG.md

How the resolution works

resolveNativeCommandSetting in src/config/commands.ts checks provider-level setting first, then falls back to the global setting. With false as the global default, it short-circuits to disabled before reaching resolveAutoDefault. Users who set nativeSkills: "auto" or true explicitly still get the old behavior - nothing changed there.

Testing

• src/config/commands.test.ts - 13/13 (was 8, added 5 for schema defaults)
• src/security/audit.test.ts - 65/65
• src/config/schema - 51/51
• pnpm check clean, pnpm tsgo clean

CI failures in contracts/channels/extensions are from the Plugin SDK refactor, not this PR. None of the changed files touch those paths.

Fixes #49273

cc @obviyus - you offered to take a look, and this is squarely in your domain. Would appreciate your eyes on whether the default flip makes sense or if you'd rather see a warning/deprecation approach first.

Changed files

• CHANGELOG.md (modified, +1/-0)
• docs/.generated/config-baseline.json (modified, +568/-70)
• docs/.generated/config-baseline.jsonl (modified, +67/-25)
• docs/tools/slash-commands.md (modified, +3/-2)
• src/config/commands.test.ts (modified, +38/-0)
• src/config/schema.help.ts (modified, +1/-1)
• src/config/types.messages.ts (modified, +1/-1)
• src/config/zod-schema.session.ts (modified, +2/-2)

PR #50191: Improve native command overflow warnings to mention nativeSkills config

• Repository: openclaw/openclaw
• Author: heyitstony97-max
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/50191

Description (problem / solution / changelog)

Summary

• When Discord/Telegram hit their 100-command platform limit, warning messages now point users to commands.nativeSkills: false (or per-provider channels.<provider>.commands.nativeSkills: false) instead of the nuclear commands.native: false which disables all native commands
• Updated all four overflow/retry warning paths across Discord and Telegram to include actionable config guidance
• Updated test assertion to match new log message

Context

Addresses #49273 — rather than changing the default from "auto" to false (which would silently break existing users), this takes the reviewer-recommended approach of improving the overflow handling messages so users can self-diagnose and apply the targeted fix.

Both Discord and Telegram already handle command overflow gracefully (Discord drops skill commands and keeps /skill fallback; Telegram pre-truncates and has a retry loop). The actual problem was that the log messages either pointed to the wrong config key or gave vague advice.

Test plan

• pnpm test -- extensions/telegram/src/bot-native-command-menu.test.ts — 11/11 pass
• pnpm test -- src/config/commands.test — 8/8 pass
• Verify Discord overflow warning appears correctly with 100+ skills installed
• Verify Telegram pre-truncation warning appears correctly with 100+ skills installed

🤖 Generated with Claude Code

Changed files

• extensions/discord/src/monitor/provider.ts (modified, +2/-2)
• extensions/telegram/src/bot-native-command-menu.test.ts (modified, +1/-1)
• extensions/telegram/src/bot-native-command-menu.ts (modified, +4/-4)
• extensions/telegram/src/bot-native-commands.ts (modified, +2/-3)