Something went wrong while processing your request. Please try again, or use /new to start a fresh

[soft hollow]

After my agent tried to add "group:messaging" to the agent’s tool list, now everything I try to do, I get this error:

⚠️ Something went wrong while processing your request. Please try again, or use /new to start a fresh session.

I am using telegram threads, I tried doctor fix and repair and restarted the gateway but didn’t work.

[hexed scarab]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[hollow zinc]

Williams, first thing: what does openclaw --version print?

group:messaging is a valid tool group on current OpenClaw, and it expands to the message tool. So if adding it made every Telegram thread fail, I’d suspect one of these:

1. You’re on an older version where that group name is not recognized.
2. The config got written in the wrong shape, for example tools: ["group:messaging"] instead of tools: { allow: ["group:messaging"] }.
3. The agent now has a too-restrictive allowlist and lost tools it needs for normal session handling.

Fastest recovery path:

openclaw --version
openclaw status --all
openclaw logs --follow

Then inspect the agent/tool config and temporarily remove the tool override that was added. If you want a messaging-oriented allowlist, current docs show either:

[hollow zinc]

{
  tools: {
    profile: "messaging"
  }
}

or, for a specific agent:

{
  agents: {
    list: [
      {
        id: "your-agent-id",

[hollow zinc]

        tools: {
          profile: "messaging"
        }
      }
    ]
  }
}

If you only want to add message access to an existing coding setup, don’t replace the whole allowlist with only group:messaging; keep the existing profile/allow entries and add message or group:messaging alongside them.

Docs:
https://docs.openclaw.ai/help/faq
https://docs.openclaw.ai/tools
https://docs.openclaw.ai/gateway/configuration-reference#tools

[hollow zinc]

If the log shows “allowlist contains unknown entries” or a config parse/type error, paste that redacted log line here.

[soft hollow]

.

[hollow zinc]

Yep, that log confirms the breakage: your active config has tools.allow: ["group:messaging"], and in this Telegram embedded run there is no registered message tool, so the allowlist filters every tool out and the run aborts before the model starts.

Recovery:

openclaw config unset tools.allow
openclaw config validate
openclaw gateway restart

If you also set it on a specific agent, check and remove that too:

openclaw config get agents.list --json

Look for the agent entry with tools.allow. If it is the first entry, for example:

[hollow zinc]

openclaw config unset agents.list[0].tools.allow
openclaw config validate
openclaw gateway restart

After that, try /new in Telegram.

Important bit: don’t use tools.allow: ["group:messaging"] by itself for this setup. It is too restrictive here. Use no explicit allowlist, or a broader profile such as:

openclaw config set tools.profile coding

Please still share openclaw --version too, because current docs list group:messaging, but your runtime says no matching tool is registered for that channel/run. If this is latest, that may be worth filing as a GitHub issue: https://github.com/openclaw/openclaw/issues