fix(telegram): bypass sequentializer for approval callback_queries

[nk3750]

Summary

Fixes #64977 — plugin approval buttons on Telegram deadlock because the Grammy sequentializer queues the approval callback_query behind the blocked agent turn.

One file changed, one pattern followed. Same fix as abort requests (telegram:<chatId>:control) and btw requests (telegram:<chatId>:btw).

Root Cause

getTelegramSequentialKey() returns the same key (telegram:<chatId>) for both:

• The user message that starts the agent turn (which blocks on plugin.approval.waitDecision)
• The approval callback_query from clicking the inline button

The @grammyjs/runner sequentializer processes same-key updates sequentially. Deadlock: the callback can't run because the lane is held, and the lane can't release because it's waiting for the callback.

Fix

Detect approval callback_query updates via parseExecApprovalCommandText(data) and return a separate sequential key: telegram:<chatId>:approval.

This is the same pattern already used for:

• Abort requests → telegram:<chatId>:control (line 40-44)
• Btw requests → telegram:<chatId>:btw (line 46-54)

Before / After (gateway logs, same machine, same guardrail)

Before — approval times out after 300s, resolve arrives too late:

plugin.approval.waitDecision 299961ms  ✓  (timed out)
plugin.approval.resolve 0ms  ✗  errorCode=INVALID_REQUEST errorMessage=unknown or expired approval id
plugin.approval.resolve 1ms  ✗  errorCode=INVALID_REQUEST errorMessage=unknown or expired approval id

After — approval resolves in 3s:

plugin.approval.waitDecision 3147ms  ✓  (resolved by button click)
plugin.approval.resolve 564ms  ✓

Audit log confirms: decision: "approval_required" at 19:22:32, resolution: "allow-once", userResponse: "approved" at 19:22:35.

Changes

File	Change
extensions/telegram/src/sequential-key.ts	Add data?: string to callback_query context type. Detect approval callbacks via parseExecApprovalCommandText and return telegram:<chatId>:approval key.
extensions/telegram/src/sequential-key.test.ts	4 new tests: plugin approval, exec approval, allow-always variant, non-approval callback (no false positives). All 23 tests pass.

Test plan

• pnpm test -- extensions/telegram/src/sequential-key.test.ts — 23/23 pass (19 existing + 4 new)
• Plugin approval callback → telegram:<chatId>:approval key
• Exec approval callback → telegram:<chatId>:approval key
• always alias callback → telegram:<chatId>:approval key
• Non-approval callback → normal telegram:<chatId> key (no false positives)
• Live e2e: ClawLens guardrail require_approval → Telegram button click → resolves in 3s (was 300s timeout)

Environment

• OpenClaw: 2026.4.10 (44e5b62) base, tested on 2026.4.11-beta.1 (faf9fe7)
• Plugin: ClawLens (returns requireApproval from before_tool_call guardrails)
• Channel: Telegram DM

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

This PR fixes a sequentializer deadlock on Telegram where approval callback_query updates shared the same lane key (telegram:<chatId>) as the blocked agent turn waiting on plugin.approval.waitDecision. The fix follows the established pattern used for abort (telegram:<chatId>:control) and btw (telegram:<chatId>:btw) requests, adding a dedicated telegram:<chatId>:approval lane by detecting approval callbacks via parseExecApprovalCommandText. The change is minimal, well-commented, and tested with 4 new cases (plugin approval, exec approval, always alias, and non-approval no-false-positive).

Confidence Score: 5/5

Safe to merge — targeted single-file fix that correctly resolves a real deadlock following the established lane-separation pattern.

No P0/P1 findings. The fix is minimal, correct, follows existing patterns for abort and btw lanes, uses a properly exported SDK function, and is covered by 4 new targeted tests.

No files require special attention.

_{Reviews (1): Last reviewed commit: "fix(telegram): bypass sequentializer for..." | Re-trigger Greptile}

[obviyus]

Verified the Telegram approval deadlock path: approval button callback queries were sharing the blocked chat lane, and the PR fixes that by routing /approve ... callbacks onto a separate sequentializer key.

Maintainer follow-up: trimmed the added explanatory comments, rebased onto latest main, and added the unreleased changelog entry for this user-facing fix.

Local gate: pnpm test extensions/telegram/src/sequential-key.test.ts.

[obviyus]

Landed on main.

• Landed source commit: c1fd4fa
• Merge commit: 22b53a4

Thanks @nk3750.