Manage OpenClaw multi-user session routing by validating and enforcing session.dmScope. Use when users ask for shared vs isolated chat context, DM/group session mapping, or dmScope persistence after upgrades.
Use this skill to keep session.dmScope valid and stable, especially when multiple Feishu users/chats talk to one bot.
per-window (recommended): maps to per-channel-peer.
shared: maps to main.
per-peer: maps to per-peer.
per-account-channel-peer: maps to per-account-channel-peer.Never set per-channel (invalid in current OpenClaw schema).
openclaw config get session.dmScope --jsonpython3 scripts/dmscope_guard.py ensure --mode per-windowpython3 scripts/dmscope_guard.py install-systemd --mode per-window --cleanup-legacysystemctl --user status openclaw-gateway --no-pageropenclaw config get session.dmScope --jsonopenclaw channels status --probe --json~/.openclaw/skills/openclaw-multiuser-session-guard-skill so OpenClaw upgrades do not overwrite it.dmScope.--mode shared.references/session-policy.mdscripts/dmscope_guard.py