Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: [Feishu] Multi-account: all sub-accounts resolve to default account's bot open_id [1 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#71017•Fetched 2026-04-25 06:08:37
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
jiaoxiaoxiao2025-dotjiaoxiaoxiao2025-dot
Participants
jiaoxiaoxiao2025-dotjiaoxiaoxiao2025-dot
Timeline (top)
labeled ×2

When configuring multiple Feishu accounts under channels.feishu.accounts, all sub-accounts (j--ceo, j--cto, j--coo) resolve to the same bot open_id as the default/main account. As a result, all agent replies are sent to the main account's chat window instead of each sub-account's own chat window.

Root Cause

When configuring multiple Feishu accounts under channels.feishu.accounts, all sub-accounts (j--ceo, j--cto, j--coo) resolve to the same bot open_id as the default/main account. As a result, all agent replies are sent to the main account's chat window instead of each sub-account's own chat window.

Fix Action

Fix / Workaround

As a result:

  1. When user sends a private message to CEO bot, the message is received correctly by j--ceo and dispatched to the CEO agent (confirmed in logs)
  2. But the reply is sent to the main account's chat window, not CEO's window
  3. Group @mention detection fails — all bots think they are the same bot, so they cannot distinguish which bot was @mentioned
  4. The user sees only the main account (J姐幸福团队-Main) responding, while CEO/CTO/COO appear silent
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

When configuring multiple Feishu accounts under channels.feishu.accounts, all sub-accounts (j--ceo, j--cto, j--coo) resolve to the same bot open_id as the default/main account. As a result, all agent replies are sent to the main account's chat window instead of each sub-account's own chat window.

Steps to reproduce

Version: 2026.4.21

Problem: When using multiple Feishu accounts (accounts config), all sub-accounts (j--ceo, j--cto, j--coo) resolve to the same bot open_id as the default account, causing all replies to appear in the default account's chat window.

Log evidence: feishu[j--ceo]: bot open_id resolved: ou_2797f385... (same as default) feishu[j--cto]: bot open_id resolved: ou_2797f385... (same as default) feishu[j--coo]: bot open_id resolved: ou_2797f385... (same as default)

Each account has its own appId/appSecret configured correctly. API verification shows each account returns different open_id:

  • default: ou_2797f385...
  • CEO: ou_2d2a5d21...
  • CTO: ou_c6e9f5e6...
  • COO: ou_d3d8b3f4...

Expected behavior

Each sub-account should resolve its own bot open_id independently:

feishu[default]: bot open_id resolved: ou_2797f385bf940c5b89f78d43d55d1eae feishu[j--ceo]: bot open_id resolved: ou_2d2a5d21357efd8c6a95f674430353f7 ← each unique feishu[j--cto]: bot open_id resolved: ou_c6e9f5e69eaf1706b1520ae261a7aa45 ← each unique feishu[j--coo]: bot open_id resolved: ou_d3d8b3f464a2bec1e7200f1166415a08 ← each unique

So that:

  1. Each bot replies in its own chat window (not the main account's window)
  2. Group @mention detection works correctly for each bot
  3. Multiple AI agents (CEO/CTO/COO) can collaborate in the same Feishu group

Actual behavior

Actual Behavior

All sub-accounts resolve to the main account's bot open_id:

feishu[default]: bot open_id resolved: ou_2797f385bf940c5b89f78d43d55d1eae feishu[j--ceo]: bot open_id resolved: ou_2797f385bf940c5b89f78d43d55d1eae ← same as default feishu[j--cto]: bot open_id resolved: ou_2797f385bf940c5b89f78d43d55d1eae ← same as default feishu[j--coo]: bot open_id resolved: ou_2797f385bf940c5b89f78d43d55d1eae ← same as default

As a result:

  1. When user sends a private message to CEO bot, the message is received correctly by j--ceo and dispatched to the CEO agent (confirmed in logs)
  2. But the reply is sent to the main account's chat window, not CEO's window
  3. Group @mention detection fails — all bots think they are the same bot, so they cannot distinguish which bot was @mentioned
  4. The user sees only the main account (J姐幸福团队-Main) responding, while CEO/CTO/COO appear silent

OpenClaw version

2026.4.21 (f788c88)

Operating system

OS: Ubuntu 24.04 (WSL2 on Windows)

Install method

No response

Model

  • Primary model: volcengine-plan/ark-code-latest - Provider: Volcengine (BytePlus/ByteDance Ark) - Routing: Multi-agent bindings via openclaw.json

Provider / routing chain

Binding config: bindings: - agentId: CEO match: channel: feishu accountId: j--ceo - agentId: CTO match: channel: feishu accountId: j--cto - agentId: COO match: channel: feishu accountId: j--coo

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue can be resolved by ensuring that each Feishu account's appId and appSecret are correctly configured and used to resolve the unique bot open_id for each sub-account.

Guidance

  • Verify that the appId and appSecret for each Feishu account are correctly set in the channels.feishu.accounts configuration.
  • Check the API verification logs to confirm that each account returns a different open_id.
  • Review the binding configuration in openclaw.json to ensure that each agent is correctly matched with its corresponding Feishu account.
  • Test the configuration by sending a private message to each sub-account and verifying that the reply is sent to the correct chat window.

Example

No code snippet is provided as the issue seems to be related to configuration rather than code.

Notes

The issue may be caused by a misconfiguration in the channels.feishu.accounts setting or the binding configuration in openclaw.json. Ensuring that each account's appId and appSecret are correctly set and used to resolve the unique bot open_id should resolve the issue.

Recommendation

Apply workaround: Verify and correct the configuration settings for each Feishu account to ensure that each sub-account resolves to its own unique bot open_id. This should allow each agent to respond in its own chat window and enable group @mention detection to work correctly.

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

Each sub-account should resolve its own bot open_id independently:

feishu[default]: bot open_id resolved: ou_2797f385bf940c5b89f78d43d55d1eae feishu[j--ceo]: bot open_id resolved: ou_2d2a5d21357efd8c6a95f674430353f7 ← each unique feishu[j--cto]: bot open_id resolved: ou_c6e9f5e69eaf1706b1520ae261a7aa45 ← each unique feishu[j--coo]: bot open_id resolved: ou_d3d8b3f464a2bec1e7200f1166415a08 ← each unique

So that:

  1. Each bot replies in its own chat window (not the main account's window)
  2. Group @mention detection works correctly for each bot
  3. Multiple AI agents (CEO/CTO/COO) can collaborate in the same Feishu group
#api#agent setup#task chaining#parallel task#integration issue

Still need to ship something?

×6

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

Back to top recommendations

TRENDING