openclaw - 💡(How to fix) Fix Feishu group chat delivery fails with 400: group chat_id sent as open_id [1 comments, 2 participants]

Bug Description

Feishu group chat @mention → agent responds successfully, but the reply delivery to the Feishu group fails with HTTP 400. The same agent works perfectly in DM (private chat) context.

Root Cause

The delivery layer is sending the group chat ID (oc_b73f99293486353055ef6cf3e05cd0b4) as an open_id parameter to the Feishu API, instead of using the correct chat_id parameter. Feishu returns:

Invalid ids: [group:oc_b73f99293486353055ef6cf3e05cd0b4]

Evidence

Agent Session — Reply Generated Successfully

[agent:nested] session=agent:tech:feishu:group:oc_b73f99293486353055ef6cf3e05cd0b4
"百胜 6,904 chunks，继续跑着。" ← Agent DID produce a reply

Delivery — Failed to Post to Group

[feishu] feishu[tech]: dispatch complete (queuedFinal=false, replies=0)
sessions_send announce delivery failed
delivery-recovery Retry failed: Request failed with status code 400
Invalid ids: [group:oc_b73f99293486353055ef6cf3e05cd0b4]

Streaming Card — Timed Out Waiting for Delivery

phase transition rejected (from=idle, to=completed, source=onIdle)
elapsed=62054ms, replies=0

LLM — Timed Out After 5 Minutes

lane task error: lane=session:agent:tech:feishu:group:oc_b73f99293486353055ef6cf3e05cd0b4
durationMs=301352 error="FailoverError: LLM request timed out."

Reproduction

1. Configure a Feishu bot account with useStreamingCards: true and replyMode: "streaming"
2. Enable requireMention: true for the Feishu group
3. @mention the bot in the Feishu group chat
4. Agent generates a reply (confirmed in logs)
5. Reply delivery fails with 400 — group oc_xxx ID sent as open_id instead of chat_id

Expected Behavior

Group chat replies should use the Feishu chat_id (oc_xxx format) API endpoint, not the open_id (ou_xxx format) endpoint.

Environment

• OpenClaw version: v2026.5.3-1
• Channel: Feishu (Lark)
• Chat type: group (not p2p)
• Agent: tech (custom agent with useStreamingCards: true)
• OS: Darwin 25.5.0 (arm64)

Impact

All Feishu group chat bots are completely non-functional. DMs work fine. This is a delivery routing regression — the agent generates replies but they never reach the group.

Config Snippet

{
  "channels": {
    "feishu": {
      "accounts": {
        "tech": {
          "streaming": {
            "useStreamingCards": true,
            "replyMode": "streaming"
          },
          "groupAllowFrom": ["oc_b73f99293486353055ef6cf3e05cd0b4"]
        }
      }
    }
  }
}

Notes

• Verified that the agent session completes and produces output
• Verified that DM delivery (same agent, private chat) works flawlessly
• The sessions_send backend DM chat works perfectly — this confirms the agent logic is fine
• Issue is specifically in the Feishu group message delivery path
• Hermes (another debugging tool) independently confirmed the same root cause: replyResolver collects the reply but delivery routes it through the wrong Feishu API parameter type