Bug type

Behavior bug (incorrect output/state without crash)

Summary

Telegram-paired direct sessions cannot execute elevated local commands because the runtime resolves the session channel as unknown, causing allowedByConfig: false even when elevated and allowFrom are configured.

Steps to reproduce

1. Pair Telegram DM with OpenClaw (sender: 6452992407).
2. Set config:

• tools.profile = full
• tools.elevated.enabled = true
• tools.elevated.allowFrom includes telegram/direct/unknown

3. Restart gateway.
4. In Telegram DM, run:

• /new
• /elevated full
• Run notepad.exe (or allowed local cmd)

5. Bot still replies it cannot execute local commands.
6. Run:

• openclaw sandbox explain --session agent:main:telegram:direct:6452992407
• Output shows Elevated -> channel: (unknown), allowedByConfig: false.

Expected behavior

Telegram-paired direct chat should run local exec when elevated is enabled and allowFrom is configured.

Actual behavior

Bot replies: “Still can’t run local commands from this session.”

OpenClaw version

2026.3.2 (85377a2)

Operating system

Windows 11

Install method

npm global

Logs, screenshots, and evidence

Diagnostics:

openclaw sandbox explain --session agent:main:telegram:direct:6452992407

Effective sandbox:
runtime: direct
...
Elevated:
enabled: true
channel: (unknown)
allowedByConfig: false

Notes:
tools.profile set to full
tools.elevated.enabled set to true
tools.elevated.allowFrom configured for telegram/direct/unknown
gateway restarted
/new and /elevated full tried in Telegram
Suspected issue:
Provider/channel resolution for this Telegram session is unknown, causing elevated allowFrom gate mismatch even when configured.

Impact and severity

Affected users/systems/channels: Users on OpenClaw 2026.3.2 using Telegram direct sessions for paired bot control with elevated local execution enabled.

Severity: Workflow-blocking for Telegram-based automation use cases (cannot run local commands from Telegram despite correct setup). Not a data-loss issue, but a core feature failure.

Frequency: Always reproducible in this setup (every attempt fails after restart, /new, and /elevated toggles).

Consequence: Blocks onboarding/testing of Telegram-triggered local automation (e.g., launching apps/scripts), causes repeated troubleshooting loops, wasted time/tokens, and poor first-run experience.

Additional information

No response