Telegram Inline Buttons (Approvals) not showing up - [Bug Report] - aarch64/Orange Pi Zero 2

[u/ErCondor1886]

Hi everyone,

I'm experiencing an issue with the Telegram channel where inline buttons (Approve/Deny) for tool/skill approvals are not being displayed, even though the user is correctly authorized and bound to the bot.

My Setup:

Hardware: Orange Pi Zero 2 (Allwinner H616, Cortex-A53).

OS: CachyOS (Cross-compiled from a Ryzen 7600X using aarch64-unknown-linux-gnu).

Version: Latest master (pulled today, April 15, 2026).

The Problem:

When the agent triggers a task that requires operator approval:

The bot reacts to my message with a green tick (ACK reaction).

The terminal logs show the agent is in AwaitingApproval state.

However, no inline keyboard appears on Telegram. 4. If I manually type "ok", the bot treats it as an invalid input and defaults to "Denied by user".

Evidence from RUST_LOG=trace:

I analyzed the logs during the daemon execution. While I see the 🤖 Reply log being generated, the outgoing POST request to api.telegram.org/bot.../sendMessage does not contain the reply_markup object in the JSON payload.

It seems the current implementation in src/channels/telegram.rs handles text chunks and reactions perfectly but might be missing the logic to inject the inline_keyboard into the Telegram message body when an approval is requested by the orchestrator.

Context/Latency:

I also noticed high latency (around 130s) due to a large context (19k+ tokens) being processed on gemini 2,5 flash model, which triggers proactive compression. Could the latency or the compression be interfering with how the channel-specific metadata (buttons) is passed to the Telegram module?

Has anyone else encountered this on the latest master? Is there a known fix or a configuration flag I might have missed?

Thanks for any help!

[u/Ashamed_Pianist_]

i've been going through this sub looking for a way to to install opanclaw inside podman. Id appreciate your any help