Summary

• registerTelegramNativeCommands() calls listSkillCommandsForAgents({ cfg }) without passing agentIds, so every Telegram bot registers all agents' skill commands
• When multiple agents share skill names (e.g. two agents both have "butler", "housekeeper"), the shared used Set causes de-duplication suffixes (/butler_2, /housekeeper_2)
• With enough agents/skills, total commands exceed Telegram's 100-command limit → BOT_COMMANDS_TOO_MUCH errors

This fix passes the bound agent's ID to listSkillCommandsForAgents() so each Telegram bot only registers its own agent's skill commands. The function already accepts agentIds — it just wasn't wired from the Telegram path.

What changed

One file: src/telegram/bot-native-commands.ts

// Before (line 260):
const skillCommands =
  nativeEnabled && nativeSkillsEnabled ? listSkillCommandsForAgents({ cfg }) : [];

// After:
const boundRoute = resolveAgentRoute({ cfg, channel: "telegram", accountId });
const boundAgentIds = boundRoute?.agentId ? [boundRoute.agentId] : undefined;
const skillCommands =
  nativeEnabled && nativeSkillsEnabled
    ? listSkillCommandsForAgents({ cfg, agentIds: boundAgentIds })
    : [];

resolveAgentRoute is already imported (line 25) and accountId is already a parameter of registerTelegramNativeCommands.

Before/After

Testing

• Tested locally with 2 Telegram agents (park-rob, park-kyla) sharing 6 workspace skills
• Verified zero dedup entries in gateway logs after fix
• Verified zero BOT_COMMANDS_TOO_MUCH errors
• Verified /housekeeper and /butler invoke correctly on the bound agent's bot
• Single-agent setups unaffected (when boundRoute.agentId is undefined, agentIds defaults to all)

AI Disclosure

🤖 AI-assisted (Claude Opus 4.5). The root cause was identified by tracing the code path from registerTelegramNativeCommands → listSkillCommandsForAgents → shared used Set. The fix was tested on a production multi-agent Clawdbot instance before submitting.