[ENHANCEMENT] Native Telegram Bot Integration for Remote Control

[redgoarhao]

Problem (one or two sentences)

Users cannot interact with Roo Code remotely. When away from the computer, there is no way to receive Roo's messages, approve/reject tool operations, or send new instructions.

Context (who is affected and when)

Heavy Roo Code users who need mobility. I often work on long-running tasks and need to monitor Roo's progress or respond to approval requests while away from my desk.

Desired behavior (conceptual, not technical)

Roo Code should have built-in Telegram bot integration that forwards messages to Telegram in real-time, allows approving/rejecting tool operations via Telegram buttons, enables sending new instructions from Telegram, and optionally supports TTS for message readout.

Constraints / preferences (optional)

I've already built a working Python implementation (~1600 lines) that monitors Roo Code's task files, uses python-telegram-bot to send messages and receive commands, provides interactive approve/reject buttons for tool operations, supports TTS via edge-tts, and works with both local and remote (SSH) VS Code instances.

This works but requires maintaining separate Python code. Having this natively in Roo Code would be much better for the community.

telegram_roo_bridge.py

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote]

I would like to help with this issue, but I need some clarification to ensure I propose the right solution. This is a substantial feature request, and I have several questions:

Architecture Questions:

1. Would the maintainers prefer this as a core built-in feature or as an MCP server? An MCP server approach would allow for better separation of concerns and could be maintained independently, while a core feature would be more tightly integrated.

2. Looking at the user's Python implementation, it monitors task files directly. Would you prefer an approach that:

   • Hooks into the extension's internal messaging system directly, or
   • Uses a file-watching approach similar to the existing Python implementation, or
   • Creates a new API/event system that external tools can subscribe to?

Security Considerations:
3. Remote control of code execution raises security concerns. What security model would be acceptable?

• Token-based authentication for the Telegram bot?
• Per-action confirmation codes?
• IP/device whitelisting?
• Or should this be considered outside the scope of an initial implementation?

Scope Questions:
4. Should the initial implementation include TTS support, or should that be a follow-up feature?

5. The user mentions it works with both local and remote (SSH) VS Code instances. Is cross-instance support a requirement for the initial implementation?

Priority:
6. Is this feature aligned with the project's current roadmap and priorities?

Please tag @roomote in your response with answers to these questions, and I'll be happy to propose a detailed implementation plan.

[redgoarhao]

Thank you for your detailed questions!

I'd prefer to leave the architectural and technical decisions to the Roo Code core maintainers (@roomote) - they know the codebase best and can make the right call on:

• Core feature vs MCP server approach
• Internal API vs file-watching implementation
• Security model design

What matters most to me as a user:
The ability to interact with Roo Code via Telegram while mobile - receiving messages, approving/rejecting operations, and sending new instructions.

Regarding your specific questions:

• TTS: I would like TTS support for both local AND remote instances
• Cross-instance support: Yes, both local and SSH remote support would be valuable

Bounty Offer:
To support the development of this feature, I'm willing to donate 1000 USDT (on TRON network) once a working implementation is merged. This demonstrates how important this feature is for my workflow.

I've already built a working Python proof-of-concept (~1600 lines) that I'm happy to share as reference. It shows the core functionality is feasible and useful.

Looking forward to hearing from the maintainers on how they'd like to approach this!

[roomote]

I've seen your comment and appreciate the detailed feedback! I'll explore implementing this as an MCP server, which would provide a clean separation of concerns while enabling the Telegram bot integration you're looking for.

I'll start by:

1. Studying the existing MCP server patterns in the codebase
2. Understanding the task file structure your Python PoC monitors
3. Designing an approach that supports the core requirements (message forwarding, approve/reject buttons, sending instructions)

I'll open a draft PR to share my progress. Feedback and guidance are welcome!

[roomote]

I've opened a draft PR with my attempt at addressing this request: #11147

What's implemented:

• Added ApproveAsk and DenyAsk IPC commands for remote approval/denial
• Created @roo-code/telegram-bridge MCP server package
• Telegram bot with:
  • Real-time message forwarding from Roo Code
  • Approve/Deny inline buttons for tool operations
  • Message forwarding from Telegram to Roo Code
  • Basic commands (/help, /status, /cancel)

Architecture:
The implementation uses an MCP server approach for clean separation of concerns. The bridge connects to Roo Code via IPC and manages a Telegram bot for remote interaction.

Next steps (for future PRs):

• TTS support
• Cross-instance support for SSH remote
• Integration tests

Feedback and guidance from maintainers are welcome!