Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug] Subagent RPC callback to WeChat session key routed to main session instead

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…
RAW_BUFFERClick to expand / collapse

Bug Description

When a subagent (熊猫/Panda) uses gateway call agent RPC with to set to a WeChat session key (e.g., agent:main:openclaw-weixin:direct:[email protected]), the message is incorrectly routed to the main session (agent:main:main) instead of the specified WeChat session.

Steps to Reproduce

  1. Have a WeChat channel connected via openclaw-weixin plugin
  2. WeChat user sends a message, creating a session: agent:main:openclaw-weixin:direct:[email protected]
  3. A subagent (熊猫) is spawned and tasked with async work
  4. 熊猫 uses gateway call agent RPC to callback with results: 
    openclaw gateway call agent \
  --url ws://127.0.0.1:18789 \
  --token <token> \
  --params {

extent analysis

TL;DR

The issue may be resolved by verifying the to parameter in the gateway call agent RPC to ensure it correctly matches the intended WeChat session key.

Guidance

  • Review the gateway call agent RPC request to confirm the to parameter is set to the correct WeChat session key (e.g., agent:main:openclaw-weixin:direct:[email protected]) instead of the main session key.
  • Verify that the WeChat session key is correctly formatted and matches the session created when the WeChat user sends a message.
  • Check the routing logic in the openclaw-weixin plugin to ensure it correctly handles the to parameter and routes messages to the intended session.
  • Test the gateway call agent RPC with a different to parameter to isolate if the issue is specific to the WeChat session key or a more general routing problem.

Example

No code snippet is provided as the issue is related to the usage of the gateway call agent RPC and the openclaw-weixin plugin, and not a specific code implementation.

Notes

The root cause of the issue is likely related to the routing logic in the openclaw-weixin plugin or the gateway call agent RPC implementation. Without more information about the plugin or the RPC implementation, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Verify and correct the to parameter in the gateway call agent RPC to ensure it matches the intended WeChat session key, as this is the most likely cause of the incorrect routing.

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…
#SSR setup#ISR setup#authentication setup#request error#file not found

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] Subagent RPC callback to WeChat session key routed to main session instead