Skip to content

[Bug]: Feishu dynamicAgentCreation feature not working #42837

Description

@cwlong163-afk

Bug type

Regression (worked before, now fails)

Summary

Bug: Feishu dynamicAgentCreation feature not working

Description:

  • Enabled channels.feishu.dynamicAgentCreation.enabled: true
  • Agent and Binding are created (visible in config)
  • But messages still route to agent:main instead of separate agents per user

Expected behavior:

  • Each Feishu DM user should have an independent agent/session

Actual behavior:

  • All DM user messages go to agent:main session

Environment: OpenClaw 2026.3.3

Steps to reproduce

Bug: Feishu dynamicAgentCreation feature not working

Description:

  • Enabled channels.feishu.dynamicAgentCreation.enabled: true
  • Agent and Binding are created (visible in config)
  • But messages still route to agent:main instead of separate agents per user

Expected behavior:

  • Each Feishu DM user should have an independent agent/session

Actual behavior:

  • All DM user messages go to agent:main session

Environment: OpenClaw 2026.3.3

Expected behavior

Bug: Feishu dynamicAgentCreation feature not working

Description:

  • Enabled channels.feishu.dynamicAgentCreation.enabled: true
  • Agent and Binding are created (visible in config)
  • But messages still route to agent:main instead of separate agents per user

Expected behavior:

  • Each Feishu DM user should have an independent agent/session

Actual behavior:

  • All DM user messages go to agent:main session

Environment: OpenClaw 2026.3.3

Actual behavior

Bug: Feishu dynamicAgentCreation feature not working

Description:

  • Enabled channels.feishu.dynamicAgentCreation.enabled: true
  • Agent and Binding are created (visible in config)
  • But messages still route to agent:main instead of separate agents per user

Expected behavior:

  • Each Feishu DM user should have an independent agent/session

Actual behavior:

  • All DM user messages go to agent:main session

Environment: OpenClaw 2026.3.3

OpenClaw version

2026.3.3

Operating system

mac OS 15.4

Install method

No response

Model

minimax

Provider / routing chain

minimax

Config file / key location

No response

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.bugSomething isn't workingclawsweeper: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.no-staleExclude from stale automationregressionBehavior that previously worked and now fails

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions