Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]:QQBot channel fails to send messages due to missing "to" parameter mapping [1 pull requests, 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#44461•Fetched 2026-04-08 00:46:38
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
eest-2026eest-2026
Participants
ai-nurmamatai-nurmamateest-2026eest-2026
Timeline (top)
labeled ×2commented ×1cross-referenced ×1

The QQBot channel extension has a bug where the CLI --target parameter is not properly mapped to the internal to field required by the QQBot channel implementation, causing message sending to fail.

OpenClaw version: 2026.3.11 (29dc654) OS: macOS 15.7.3 (arm64) Node.js: v25.8.0 QQBot extension: @sliverp/qqbot@latest (unpinned version) Additional Context:

Error Message

Observe the error: ToolInputError: to required The QQBot channel throws a ToolInputError: to required error, indicating that the internal to parameter is missing despite the CLI providing the correct --target parameter. The target format qqbot:c2c:USER_ID is correctly validated by the CLI (as shown by the "Unknown target" error when using incorrect format)

Root Cause

The QQBot channel extension has a bug where the CLI --target parameter is not properly mapped to the internal to field required by the QQBot channel implementation, causing message sending to fail.

OpenClaw version: 2026.3.11 (29dc654) OS: macOS 15.7.3 (arm64) Node.js: v25.8.0 QQBot extension: @sliverp/qqbot@latest (unpinned version) Additional Context:

Fix Action

Fixed

PR fix notes

PR #44537: fix: map CLI --target param to args.to in message-action-runner

Description (problem / solution / changelog)

When CLI passes --target parameter, it was stored in args.target but resolveActionTarget only checked args.to. This caused message send operations via CLI --target to fail with missing target error.

This fix adds a mapping from args.target to args.to when args.to is not present, enabling proper CLI --target parameter handling.

AI-ASSISTED

Fixes #44461

Changed files

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Summary

The QQBot channel extension has a bug where the CLI --target parameter is not properly mapped to the internal to field required by the QQBot channel implementation, causing message sending to fail.

OpenClaw version: 2026.3.11 (29dc654) OS: macOS 15.7.3 (arm64) Node.js: v25.8.0 QQBot extension: @sliverp/qqbot@latest (unpinned version) Additional Context:

Steps to reproduce

Configure QQBot channel with valid credentials Run command: openclaw message send --channel qqbot --target "qqbot:c2c:VALID_USER_ID" --message "test message" Observe the error: ToolInputError: to required Expected Behavior: The CLI --target parameter should be automatically converted to the to field expected by the QQBot channel, and the message should be successfully delivered.

Expected behavior

The monitoring script should work end-to-end without any manual intervention, sending real-time information directly to QQ agent.

Actual behavior

The QQBot channel throws a ToolInputError: to required error, indicating that the internal to parameter is missing despite the CLI providing the correct --target parameter.

OpenClaw version

2026.3.11 (29dc654)

Operating system

macOS 15.7.3 (arm64)

Install method

pnpm

Model

bailian/qwen3-max-2026-01-23

Provider / routing chain

Local OpenClaw Agent → Local Gateway (127.0.0.1:18789) → Alibaba Cloud DashScope API (coding.dashscope.aliyuncs.com/v1) → Qwen3-Max Model

Config file / key location

No response

Additional provider/model setup details

The target format qqbot:c2c:USER_ID is correctly validated by the CLI (as shown by the "Unknown target" error when using incorrect format) However, once the target format is correct, the QQBot channel implementation fails to extract the to field from the CLI parameters This appears to be a parameter mapping issue between the OpenClaw CLI layer and the QQBot channel extension

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

To resolve the issue, we need to properly map the --target parameter to the internal to field in the QQBot channel implementation.

Here are the steps:

  • Update the QQBot channel extension to parse the --target parameter and extract the USER_ID.
  • Map the extracted USER_ID to the internal to field.

Example code snippet:

// In the QQBot channel extension
const target = cliParams.target;
const userId = target.split(':')[2]; // Extract the USER_ID from the target parameter
const toField = `c2c:${userId}`; // Map the USER_ID to the to field

// Use the toField in the QQBot channel implementation
const message = {
  to: toField,
  message: cliParams.message
};

Verification

To verify the fix, run the following command:

openclaw message send --channel qqbot --target "qqbot:c2c:VALID_USER_ID" --message "test message"

The message should be successfully delivered to the specified QQ user.

Extra Tips

  • Ensure that the --target parameter is correctly validated and parsed in the QQBot channel extension.
  • Consider adding error handling for cases where the --target parameter is invalid or missing.

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 monitoring script should work end-to-end without any manual intervention, sending real-time information directly to QQ agent.

#api#ssr#installation#tensor shape#autograd error#dependency conflict#environment setup#docker error#permission error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING