Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

A Telegram DM continued routing to a stale Claude ACP session instead of the main agent, even though normal Telegram config pointed to the main agent and multiple session/runtime cleanup steps had already been performed.

The actual live cause was an explicit persisted binding in:

~/.openclaw/telegram/thread-bindings-default.json

Steps to reproduce

1. Bind a Telegram DM conversation to a persistent ACP session.
2. Let that ACP session become stale, failed, or otherwise no longer desired.
3. Restart OpenClaw and/or clean ordinary session/runtime state.
4. Send a new Telegram DM message.
5. Observe that the DM is still routed to the stale ACP session.
6. Inspect ~/.openclaw/telegram/thread-bindings-default.json.
7. Find a binding for the Telegram conversation pointing to the stale ACP session.

Expected behavior

The Telegram DM should route back to the normal main-agent DM session once the stale ACP session is no longer desired. A hidden Telegram binding file should not keep silently overriding expected routing without a clear unbind/reset workflow.

Actual behavior

Telegram conversation kept routing to:

agent:claude:acp:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx

instead of:

agent:main:telegram:direct:xxxxxxxxx

This persisted across:

• restart
• parent session transcript cleanup
• command log cleanup
• related SQLite runtime cleanup

OpenClaw version

2026.4.2

Operating system

Ubuntu 24.04

Install method

ansible

Model

ChatGPT 5.4

Provider / routing chain

openclaw -> OpenAI

Additional provider/model setup details

Environment

Telegram DM ACP backend: acpx ACP agent: claude Host: Linux VPS

Relevant config Normal Telegram/main-agent config appeared correct in openclaw.json. The authoritative routing override was not in top-level config; it was in:

~/.openclaw/telegram/thread-bindings-default.json

The binding entry looked like:

{ "accountId": "default", "conversationId": "xxxxxxxxxx", "targetSessionKey": "agent:claude:acp:xxxxxxxxxx", "targetKind": "acp", "boundAt": 1775159597143, "lastActivityAt": 1775194400810, "agentId": "claude", "boundBy": "system" }

Logs / output / additional context We initially found related persisted state in other places, including:

~/.openclaw/logs/commands.log ~/.openclaw/tasks/runs.sqlite But clearing those alone was not sufficient to fix the issue.

The actual restoring step was:

1. remove the binding entry from ~/.openclaw/telegram/thread-bindings-default.json
2. restart OpenClaw

After that, Telegram immediately routed correctly back to the main agent.

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response