Skip to main content
Glama
vscode-copilot-telegram

vscode-copilot-telegram

by weslylaboy

Related Servers

Alternatives to vscode-copilot-telegram

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects VS Code Copilot to Telegram for mobile notifications, interactive approval workflows, and remote command input. Enables users to monitor AI agents, approve sensitive operations, and provide follow-up instructions from their smartphone.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Cursor agents to ask questions and send notifications to a user via Telegram, and to require Allow/Deny approval for dangerous shell commands through Cursor hooks.
      1
      MIT
    • A
      license
      A
      quality
      Not graded
      maintenance
      Enables bidirectional communication between AI coding assistants and Telegram, allowing interactive confirmations via inline buttons, media and screenshot ingestion, and on-demand message polling without a background daemon.
      6
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables remote control of AI coding assistants (Claude Code/Codex) via Telegram, allowing you to manage long-running tasks, send commands, and receive notifications from anywhere. Supports unattended mode with smart polling for up to 7 days and multi-session management.
      8
      30
      MIT

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: ask_user waits for a reply, notify sends one-way, and run_command executes with approval. There is no meaningful overlap between them.

    Naming Consistency4/5

    ask_user and run_command follow a clear verb_noun pattern, but notify is a bare verb. The deviation is minor and the names remain readable.

    Tool Count5/5

    Three tools is well-scoped for a narrow Telegram-mediated interaction layer. Each tool earns its place without redundancy.

    Completeness4/5

    The surface covers the core lifecycle: one-way notification, interactive questions, and approved command execution. Minor gaps exist, such as no way to send richer interactive messages or update prior messages, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues