Summary

Approval prompts for tools like exec should appear in the same channel where the request originated, not just in Web UI.

Problem to solve

Currently, when a user triggers a tool that requires approval (such as running a shell command) from Discord, Telegram, or Slack, the approval prompt with Approve/Deny buttons only appears in the Web UI. This creates a poor user experience because:

1. Users must switch from their chat app to Web UI just to approve/deny
2. On mobile, this is particularly cumbersome
3. It discourages using chat channels for tasks that require tool execution
4. Users may be tempted to disable approvals entirely (removing security guardrails)

Proposed solution

When a user sends a message from any channel (Discord, Telegram, Slack, Web UI) requesting an action that requires approval:

1. The approval prompt appears in the same channel where the request came from
2. The user can approve/deny directly from that channel using inline buttons
3. Security guardrails remain intact — users still explicitly approve/deny

Alternatives considered

Reaction-based approval (#24639)

Use emoji reactions on approval messages:

• 👍 = Allow Once / Always Allow
• 👎 = Deny

This would work across all channels that support reactions.

Impact

Who is affected

Users who interact with OpenClaw via chat channels (Discord, Telegram, Slack) instead of Web UI. This includes:

• Mobile users who prefer chat apps over browser
• Users who have set up Discord/Telegram/Slack as primary interaction channels
• Anyone using OpenClaw on-the-go

Severity

Annoying — Blocks workflow for users who prefer chat channels. Not a crash, but significantly degrades the mobile experience and discourages using chat apps for tasks requiring tool execution.

Frequency

Always — Every time a tool requiring approval is invoked from a chat channel. This is not an edge case; it affects 100% of exec/tool calls from Discord/Telegram/Slack.

Consequence

1. Users must manually switch to Web UI to approve/deny
2. On mobile, this means opening a browser, logging in, finding the approval, then responding 3. Approval timeouts occur (~120 seconds) because users can't respond in time from chat channels
3. Some users may disable approvals entirely (security risk) to avoid the inconvenience
4. Poor UX discourages use of chat channels for legitimate tool-using workflows

Evidence/examples

Example (Telegram)

🔒 Exec approval required
Command: echo hello
Agent: main

[Allow Once] [Always Allow] [Deny]

Example (Discord)

🔒 Exec approval required
Command: echo hello
Agent: main

[✅ Allow] [⚠️ Always Allow] [❌ Deny]

Additional information

Related Issues

• feat(exec-approvals): reaction-based approval — 👍 tapback auto-approves, 👎 denies #24639 — Reaction-based approval (👍 tapback approves, 👎 denies)
• Telegram: Add inline button support for exec approval prompts #22078 — Telegram inline button support for exec approval prompts
• Exec approvals requesting confirmation despite security=full and ask=off for Discord/Telegram #26739 — Exec approvals requesting confirmation despite security=full for Discord/Telegram

Acceptance Criteria

• Approval prompts appear in the same channel as the request
• Inline buttons work for Discord, Telegram, and Slack
• Web UI approvals continue to work as before
• Security guardrails remain intact (explicit user approval required)