Skip to content

fix: add format validation for gateway.nodes.denyCommands#3

Open
zelixag wants to merge 4 commits into
mainfrom
fix/validate-deny-commands-v2
Open

fix: add format validation for gateway.nodes.denyCommands#3
zelixag wants to merge 4 commits into
mainfrom
fix/validate-deny-commands-v2

Conversation

@zelixag
Copy link
Copy Markdown
Owner

@zelixag zelixag commented Mar 19, 2026

Summary

Add format validation for denyCommands config to prevent whitespace in command patterns.

Changes

  • src/config/zod-schema.ts: Added validator for denyCommands

Closes openclaw#50011

zelixag added 4 commits March 18, 2026 14:37
The schtasks commands were using default output format which depends on
system locale. On Windows systems with non-Western locales, this caused
'schtasks unavailable: unknown error' even when schtasks worked fine.

Fixes: openclaw#49187
openclaw#49988 - Connection failures to local Ollama instances are common (e.g., Ollama not running),
so they should be logged at debug level rather than warning level to avoid cluttering logs.
… unknown messageId

openclaw#49978 - Discord delivery was reporting lastDelivered: true even when message
actually failed because toDiscordSendResult returned 'unknown' as messageId
instead of properly signaling failure. Now throws an error when message ID
is missing from the send response.
openclaw#50011 - gateway.nodes.denyCommands silently accepts invalid command names.
Now validates that command names don't contain whitespace, which is a common
mistake when users try to use patterns instead of exact command names.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: gateway.nodes.denyCommands silently accepts invalid command names without warning

1 participant