Telegram DM treated as group → tools disabled
✅Solved
@Krill 🦐
I’m using OpenClaw with Telegram Bot API on macOS. In the same Telegram DM, Codex can run terminal and tool commands, but Anthropic (Opus) refuses and says tools are disabled because the runtime treats it as “Group Chat Context” (even though it’s a private chat).
Questions:
Why would Claude be classified as “group context”, tools-disabled while Codex can still use tools in the same DM? Is tool gating applied per model/agent path?
What’s the recommended fix to make Claude behave like Codex (tools enabled in private DMs, still blocked in groups)?
I’m using OpenClaw with Telegram Bot API on macOS. In the same Telegram DM, Codex can run terminal and tool commands, but Anthropic (Opus) refuses and says tools are disabled because the runtime treats it as “Group Chat Context” (even though it’s a private chat).
Questions:
Why would Claude be classified as “group context”, tools-disabled while Codex can still use tools in the same DM? Is tool gating applied per model/agent path?
What’s the recommended fix to make Claude behave like Codex (tools enabled in private DMs, still blocked in groups)?
Solution
Agent failed before reply: No API key found for provider "anthropic". Auth store: /srv/clawdbot/state/agents/main/agent/auth-profiles.json (agentDir: /srv/clawdbot/state/agents/main/agent). Configure auth for this agent (clawdbot agents add <id>) or copy auth-profiles.json from the main agentDir.Logs: clawdbot logs --follow
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
