openclaw - 💡(How to fix) Fix Feature request: Add message tool for agents to send messages with inline buttons [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#59573Fetched 2026-04-08 02:43:02
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
Participants

Fix Action

Fix / Workaround

Current Workaround

RAW_BUFFERClick to expand / collapse

Problem

Currently, agents running in OpenClaw can receive and reply to messages, but they don't have access to a tool that would allow them to send outbound messages with interactive elements like inline buttons.

While the CLI command supports sending Telegram inline buttons via the flag, agents cannot invoke this functionality directly during conversations.

Use Case

When a user says 'menu' or 'commands', the agent should be able to reply with a message containing inline buttons that execute commands when clicked. For example:

Clicking a button would send the corresponding command to the agent.

Current Workaround

  • Agents can use to run but this:
    1. Requires tool access and approval workflow
    2. Is not a natural conversation flow
    3. Requires the agent to know the target user's chat ID

Proposed Solution

Add a tool (similar to the existing tool) that agents can call with:

  • : telegram, discord, etc.
  • : target user/chat ID
  • : text content
  • : array of inline keyboard buttons (Telegram)

This would enable natural conversational interfaces with button menus while keeping the security model intact (tool policy controls access).

Additional Context

  • Telegram inline buttons are already configured and working
  • The CLI command already demonstrates this is technically feasible
  • This feature would greatly improve UX for frequently-used commands

extent analysis

TL;DR

Implement a new tool that allows agents to send outbound messages with interactive elements like inline buttons, similar to the existing tool, to enable natural conversational interfaces.

Guidance

  • Identify the requirements for the new tool, including platform, target user/chat ID, text content, and array of inline keyboard buttons.
  • Determine the security model and access controls for the new tool, ensuring it aligns with the existing tool policy.
  • Consider the technical feasibility of the proposed solution, given that Telegram inline buttons are already configured and working, and the CLI command demonstrates this capability.
  • Evaluate the potential impact on user experience, particularly for frequently-used commands, and prioritize the development of the new tool accordingly.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The proposed solution requires careful consideration of security and access controls to ensure the new tool does not introduce vulnerabilities or compromise the existing security model.

Recommendation

Apply a workaround by implementing the proposed new tool, as it addresses the current limitation and improves the user experience, while maintaining the security model intact.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING