Skip to content

Commit 8749c81

Browse files
committed
docs(feishu): explain legacy dynamic agent cap
1 parent e05df6f commit 8749c81

2 files changed

Lines changed: 4 additions & 0 deletions

File tree

docs/channels/feishu.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -417,6 +417,8 @@ This is essential for public bots where you want each user to have their own pri
417417

418418
<Note>
419419
Dynamic bindings include the normalized Feishu `accountId`, so default and named accounts route each sender to the correct dynamic agent.
420+
421+
If a named account created an unscoped dynamic agent on an older release, that legacy agent still counts toward `maxAgents`. Confirm that it is not used by the default account before removing it, or temporarily increase `maxAgents`; OpenClaw cannot safely infer which account owns ambiguous legacy state.
420422
</Note>
421423

422424
### Quick setup

extensions/feishu/src/dynamic-agent.ts

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -110,6 +110,8 @@ export async function maybeCreateDynamicAgent(params: {
110110
}
111111
const agentId = resolveDynamicAgentId(accountId, senderOpenId);
112112
const currentAgentExists = (currentCfg.agents?.list ?? []).some((agent) => agent.id === agentId);
113+
// Legacy unscoped agents are indistinguishable from valid default-account state.
114+
// Keep maxAgents as a hard cap instead of auto-rebinding or deleting ambiguous user data.
113115
if (!currentAgentExists && isAtDynamicAgentLimit(currentCfg, currentDynamicCfg)) {
114116
log(
115117
`feishu: maxAgents limit (${currentDynamicCfg.maxAgents}) reached, not creating agent for ${senderOpenId}`,

0 commit comments

Comments
 (0)