Skip to content

[Bug] Subagent RPC callback to WeChat session key routed to main session instead #69443

Description

@chen11221

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 {

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.staleMarked as stale due to inactivity

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions