升级 2026.2.12 后消息处理全挂：Session path 报错的可执行回退方案
问题/场景：更新到 2026.2.12 后 Discord/Telegram 全部消息处理失败，报 `Session file path must be within sessions directory`。前置条件：多代理/多渠道部署。实施步骤：复现并确认错误后，按社区验证路径回退到 2026.2.9 并重启。关键命令：`npm i -g openclaw@2026.2.9`。验证：各渠道消息可恢复响应。风险：回退可能与新配置字段不兼容，回退前需备份。
GITHUBDiscovered 2026-02-16Author Visionary007
Prerequisites
- You run OpenClaw with channel handlers (Discord/Telegram etc.) and can tolerate temporary rollback.
- Session store path is configurable and logs are accessible.
Steps
- Confirm all channel handlers fail with the same session-path error after 2026.2.12 upgrade.
- Run `openclaw doctor --fix` / `openclaw doctor --repair` once to exclude local corruption (as reported ineffective in thread).
- Rollback to v2026.2.9 with npm global install and restart gateway.
- Replay inbound test messages across all configured channels and confirm handlers recover.
Commands
openclaw doctor --fixopenclaw doctor --repairnpm i -g openclaw@2026.2.9openclaw gateway restartVerify
Incoming messages on Discord/Telegram are processed normally again with no recurring session-path rejection errors.
Caveats
- The issue is linked to security-hardening path checks; do not patch around it by weakening path validation in production.
- Keep backup of current config/session data before rollback to avoid compatibility loss.
Source attribution
This tip is aggregated from community/public sources and preserved with attribution.
Open original source ↗