GitHub Issue：多 Telegram 账号多代理的 session path 越界排查

问题/场景：多代理 + 多 Telegram 账号出现 `Session file path must be within sessions directory` 导致无响应。前置条件：已使用 bindings 与 dmScope。实施步骤：核对 accountId→agentId、抓取 debounce flush 日志、对比 sessionsDir 与 sessionFile。关键命令：`openclaw channels status --probe`、`openclaw logs --follow`。验证：异常消失且消息恢复。风险：直接改编译产物绕过校验有安全隐患。

GITHUBDiscovered 2026-02-18Author aaaaaatong

Prerequisites

Multi-agent Telegram setup with reproducible failure path.
Operator can inspect logs and channel binding configuration.

Steps

Verify account bindings and `session.dmScope` consistency across all bot accounts.
Reproduce one failing message and capture `telegram debounce flush` logs.
Compare resolved `sessionsDir` with stored `sessionFile` path for cross-agent mismatch.
Prefer config/session rebuild fixes first, then re-test before any code patching.

Commands

openclaw channels status --probe

openclaw pairing list telegram

openclaw config get channels

openclaw logs --follow

Verify

No more session-path exceptions and repeated Telegram messages receive normal replies.

Caveats

Bypassing path checks can hide real cross-agent bugs and weaken safeguards.
Issue is still open; final upstream fix timeline is uncertain（需验证）.

Source attribution

This tip is aggregated from community/public sources and preserved with attribution.

Open original source ↗

Visit original post