Telegram bridge cannot send files/documents even with --accept-all

[edwardcodelab]

Describe the bug

Cheetahclaws send [approve][reject] which I can't click.

Even after setting accept-all via , the Telegram bridge cannot send files back to the user.

• Text messages, slash commands, voice notes, and photos to cheetahclaws work fine.
• Any time the AI tries to send a file no file appears in Telegram.
• The AI keeps saying “file sent” or shows the file content in the web UI, but nothing arrives in the Telegram chat.

This makes the Telegram bridge unusable for any workflow that involves file output.

Docker:
volumes:
- ./data:/data
- /path/to/workspace:/workspace:rw

[chauncygu]

Thanks for your great feedback.

We already fixed in the latest version, both halves of this issue are addressed:

1. File round-trip. --accept-all was a red herring; bridges/telegram.py simply lacked the upload path. Added:

• _tg_send_document — multipart/form-data upload, 49 MB cap, six explicit failure modes reported back to chat (missing / stat fail / empty / oversize / network / API ok:false).
• Inbound document handler — saves uploads to /workspace (Docker) or tempfile.gettempdir() with sanitized filenames, then prompts the agent with the saved path.
• !sendfile — explicit on-demand send.
• Auto-send on Write — when the model writes a file, it's mailed to the chat as a document. FIFO-paired with the in-flight file_path, skipped on Error: / Denied: results, de-duplicated per turn.

2. Clickable [approve][reject]. The text-bracket pseudo-buttons are now real Telegram inline_keyboard buttons (✅ Approve / ❌ Reject / ✅✅ Accept all). The bridge:

• Widens allowed_updates to ["message", "callback_query"].
• Validates each click's chat_id (auth) and a per-prompt prompt_id baked into callback_data (so stale clicks on older prompts don't bleed in).
• Acknowledges via answerCallbackQuery to dismiss the spinner.
• Edits the original message to append ✓ Selected: y for visible scroll-back.
• Falls back gracefully: Markdown failure → no-parse_mode keyboard → plain text without keyboard. The [y/N/a] text hint stays in the prompt body for fallback paths.

Docs: new "Permission prompts" + "File support" sections in docs/guides/bridges.md

Slack / WeChat / terminal are unaffected — they ignore the new options= parameter on ask_input_interactive and keep using the existing text path. PR coming shortly.

[chauncygu]

All fixed, please use the latest version.

Thanks again for your great feedback.

Best,

[edwardcodelab]

Slash commands (/help, /monitor, etc.) give no response

Description:

After the latest update, all Telegram slash commands are completely broken:

• Commands like /help, /monitor, /model, /status etc. produce zero response from the bot.
• The commands never appear in docker compose logs -f (only normal messages are logged).

I think if it is Handle_slash problems?

Thank you

[chauncygu]

Hi @edwardcodelab, thanks a lot for your feedback. I will look at that and try to fix it soon.

Thanks again!

[chauncygu]

Hi @edwardcodelab, we already fixed the issue. Please use the latest version in the main branch and rebuild your Docker image; /help, /monitor, /model, /status should all respond now. Thanks for the useful feedback.

[edwardcodelab]

Big thanks to the CheetahClaws team for the latest update! Really appreciate the continuous improvements and fast iterations.

However, the Telegram bridge still cannot show the [Approve] / [Reject] inline buttons when a sensitive action needs confirmation.

Reproduction Steps

1. In Telegram, ask CheetahClaws to do something that normally requires approval, for example:

   Create a folder named "test_folder" in the current directory
   

   or directly:

   mkdir test_folder
   

2. The model understands the request and plans to run the command, but:

   • No [Approve] [Reject] buttons appear.
   • Typing approve, accept, accept-all, yes, etc. does not trigger execution.

3. Workaround: Manually enable "accept-all" mode in WebUI or terminal first.

4. Bonus issue:
   /help replies “/help is executed.” but no menu is shown.

Expected Behavior

• Inline approval buttons should appear for actions like folder creation, file operations, bash commands, etc.
• Text fallback (approve / accept-all) should still work.
• /help should display the proper command menu.

Telegram and other messenger bridges are crucial for remote usage. Fixing the approval flow would make the tool much more practical and enjoyable.

Thanks again for all the work

[chauncygu]

Hi @edwardcodelab , Thanks for your precise and useful feedback. We have fixed it in the latest version of the code. Just updated, please see the code. If you have any further issues, we are happy to take them.