openclaw - 💡(How to fix) Fix [Bug]: command-dispatch skill routing strips arguments from slash commands [1 comments, 2 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#59228Fetched 2026-04-08 02:27:12
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Timeline (top)
labeled ×2commented ×1

Slash commands with arguments (e.g., /command 115) do not pass arguments to the skill dispatch script. Only the base command name is received — arguments are stripped.

Root Cause

Slash commands with arguments (e.g., /command 115) do not pass arguments to the skill dispatch script. Only the base command name is received — arguments are stripped.

Fix Action

Fix / Workaround

Slash commands with arguments (e.g., /command 115) do not pass arguments to the skill dispatch script. Only the base command name is received — arguments are stripped.

  1. Configure a skill with command-dispatch: tool and command-exec pointing to a dispatch script
  2. Send a slash command with arguments via Telegram (e.g., /command 115)
  3. The dispatch script receives NO arguments — only the base command

The dispatch script should receive the full command including arguments (e.g., command 115 or just 115)

Code Example

metadata:
  openclaw:
    command-dispatch: tool
    command-tool: exec
    command-exec: "~/.openclaw/skills/taskboard/scripts/dispatch.sh"
    user-invocable: true

---

~/.openclaw/skills/<command>/SKILL.md
~/.openclaw/skills/<command>/scripts/dispatch.sh
~/.openclaw/skills/<command>/scripts/commands.py
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Slash commands with arguments (e.g., /command 115) do not pass arguments to the skill dispatch script. Only the base command name is received — arguments are stripped.

Steps to reproduce

  1. Configure a skill with command-dispatch: tool and command-exec pointing to a dispatch script
  2. Send a slash command with arguments via Telegram (e.g., /command 115)
  3. The dispatch script receives NO arguments — only the base command

Expected behavior

The dispatch script should receive the full command including arguments (e.g., command 115 or just 115)

Actual behavior

The dispatch script receives only command with no arguments

OpenClaw version

2026.3.28

Operating system

Linux 6.12.75+rpt-rpi-v8 (arm64) — Raspberry Pi

Install method

npm install -g openclaw

Model

minimax-m2.7-cloud:latest (via Ollama)

Provider / routing chain

Ollama → MiniMax cloud

Additional provider/model setup details

  • OpenClaw version: 2026.3.28 (current, broken)
  • Last working version: 2026.3.23
  • Regression: YES — broke somewhere between 3.23 and 3.28
  • Channel: Telegram
  • Skill config:
metadata:
  openclaw:
    command-dispatch: tool
    command-tool: exec
    command-exec: "~/.openclaw/skills/taskboard/scripts/dispatch.sh"
    user-invocable: true

Logs, screenshots, and evidence

• Debug log from dispatch.sh shows only Args: command received, no argument • Telegram API getUpdates approach failed due to race condition (gateway consumes update first) • Hooks system does not have subagent.completion or command.args event • Similar issues #56471 and #54767 closed Mar 31 — possibly related

Impact and Severity • Impact: Slash commands with arguments are non-functional. Users cannot pass parameters to skills via Telegram slash commands. • This is a regression. Core slash command functionality is broken.

Additional Information

Workaround: Assistant handles /command 115 as natural language and calls the commands.py script directly, bypassing command-dispatch.

Files:

• ~/.openclaw/skills/<command>/SKILL.md
• ~/.openclaw/skills/<command>/scripts/dispatch.sh
• ~/.openclaw/skills/<command>/scripts/commands.py

Additional information

No response

extent analysis

TL;DR

The most likely fix for the regression issue with slash commands and arguments is to modify the command-dispatch configuration to handle arguments correctly or use a workaround by bypassing command-dispatch and calling the commands.py script directly.

Guidance

  • Review the command-dispatch configuration in the skill.yaml file to ensure it is set up to handle arguments correctly.
  • Consider using the workaround mentioned in the issue, where the Assistant handles the slash command as natural language and calls the commands.py script directly.
  • Investigate the changes made between OpenClaw versions 2026.3.23 and 2026.3.28 to identify the cause of the regression.
  • Check the debug log from dispatch.sh to see if there are any clues about why the arguments are being stripped.

Example

No code snippet is provided as the issue does not contain enough information to create a specific example.

Notes

The issue is a regression, and the last working version was 2026.3.23. The workaround mentioned in the issue may not be a permanent solution, and the root cause of the issue should be investigated.

Recommendation

Apply workaround: The workaround mentioned in the issue can be used as a temporary solution until the root cause of the issue is identified and fixed. This will allow users to pass parameters to skills via Telegram slash commands, although it may not be the most elegant solution.

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…

FAQ

Expected behavior

The dispatch script should receive the full command including arguments (e.g., command 115 or just 115)

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 [Bug]: command-dispatch skill routing strips arguments from slash commands [1 comments, 2 participants]