PR #81592: [codex] Route Telegram management commands to the control lane

• Repository: openclaw/openclaw
• Author: Kyzcreig
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/81592

Description (problem / solution / changelog)

Summary

Routes Telegram /steer, /tell, and /queue text commands onto the existing per-chat control sequentialization lane.

Why

Telegram updates are sequentialized by chat/thread so normal messages do not race with each other. That is correct for conversational messages, but management commands that are intended to affect an active run should not wait behind the same long-running message they are trying to control.

/stop and status commands already bypass the normal chat lane. This gives /steer, its /tell alias, and /queue the same immediate lane behavior.

Validation

• vitest run extensions/telegram/src/sequential-key.test.ts
• oxfmt --check --threads=1 extensions/telegram/src/sequential-key.ts extensions/telegram/src/sequential-key.test.ts

Changed files

• extensions/telegram/src/sequential-key.test.ts (modified, +22/-0)
• extensions/telegram/src/sequential-key.ts (modified, +20/-0)

PR #81613: fix(steer): fallback to sibling direct/DM lanes when slash lane has no active run

• Repository: openclaw/openclaw
• Author: freeter226
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/81613

Description (problem / solution / changelog)

Summary

Fixes #81594

When /steer targets a slash-command session lane but no active embedded run exists there, the command reports "no active run" even though the user has an active run on the sibling direct/DM lane for the same peer.

Root Cause

resolveSteerSessionId() in src/auto-reply/reply/commands-steer.ts only checks the resolved target session key. When the key resolves to a :slash: lane (because the /steer text command is dispatched through the slash lane), it finds no active run and gives up immediately, without checking sibling lanes.

Fix

After the initial active-run lookup fails on the slash lane, check if the session key contains :slash: and try the corresponding :direct: and :dm: sibling keys. Return the first sibling with an active embedded run.

This matches the approach suggested in the issue and mirrors the pattern used by other channel dispatch paths (Telegram, Discord) where the active run lives on the direct/DM lane.

Testing

• Code reviewed line-by-line against the existing session resolution pattern
• Logic verified: only falls back when the original target is a slash lane AND has no active run
• No side effects: if neither sibling has an active run, existing behavior (return undefined → fallback prompt) is preserved

AI-assisted

This PR was written with AI assistance. I have reviewed and understand every line of the change.

Changed files

• src/auto-reply/reply/commands-steer.ts (modified, +14/-0)