Skip to content

saplq/chatmate

v0.12.0MIT

Connects your AI to your Telegram through your personal ChatMate bot: read the chats you connected, give tasks in the bot, and get answers, drafts and results back in Telegram.

GitHubOpen Website

ChatMate plugin

Connect the Telegram chats you choose to your own AI. ChatMate supplies the messages and tools; your AI handles the work and can return answers to your personal ChatMate bot.

Start in your bot

  1. Open @chatmate_aibot, create your personal bot and connect your chats.
  2. Choose ChatGPT or Claude in that bot. For ChatGPT Work, install ChatMate and run its Setup step. Setup guides Telegram sign-in, access and the owner-message subscription in the same conversation. Use the copyable setup prompt only if your client has no Setup step.
  3. For a Claude cloud Routine, follow the protected setup form. It supplies the saved Routine instructions and guides the API trigger generated in Claude’s web UI. Ordinary Claude and local Claude Code retain their guided setup prompts.
  4. Complete Telegram sign-in and Allow yourself. Never paste credentials or tokens into an AI conversation. Send one short task to your personal bot and check the automatic reply before relying on the connection.

Full prompts and manual connection instructions are also available at getchatmate.com/connect.

Choose an execution surface

  • ChatGPT Work: web Work or desktop Work with Cloud uses native Setup after installation to configure MCP Events when the surface supports them. Monitoring starts only after subscription succeeds. Ordinary chats and clients without Events support manual requests.
  • Claude web, desktop or mobile: connect the account connector to read chats and make manual requests. OAuth alone does not start tasks when a Telegram message arrives.
  • Local Claude Code: install this plugin and authenticate its MCP connection. This connection is separate from your Claude web account and a cloud Routine environment.
  • Claude cloud Routine: choose a repository, environment and required account connectors, then create an API trigger in Claude’s web UI. Save its fire URL and token in the protected setup form. ChatMate triggers the Routine with the canonical owner message UUID; the Routine claims the task, starts Thinking, updates its progress and accumulated answer, then returns one final reply. Cloud token-by-token streaming remains unverified.

Use one active executor for Telegram tasks. Connecting two AIs does not configure automatic fallback.

Claude Code installation

In Claude Code 2.1.275 or later:

/plugin install chatmate --marketplace saplq/chatmate-plugin

Confirm the source and installation scope, then reload plugins or start a new session. Open /mcp and authenticate ChatMate; complete the Telegram login yourself.

For Codex, install this repository through its plugin marketplace and authenticate the ChatMate MCP connection. The repository retains its Codex compatibility manifest and marketplace.

Manual connector fallback

Add an OAuth MCP connector named ChatMate with this server URL:

https://www.getchatmate.com/api/connector/mcp

Complete Telegram sign-in and Allow. The connector provides tools; use the setup prompt to configure the execution surface separately.

Answer updates and optional hooks

Use explicit update_answer calls by default. The packaged Claude Code display-hook example is disabled. Enable it only after explicitly choosing a dedicated Telegram-only project/environment; never install it globally or in a general AI-chat environment. It forwards every assistant display delta from that environment, including unbound text.

Telegram actions in 0.10.0

A specific owner request authorizes the requested action and recipient. No additional ChatMate send switch or mandatory confirmation card is required; your AI client's write permissions and Telegram rights still apply. ChatMate supports 18 typed actions: text/replies/quotes, stored photos/documents/video/audio/voice/video notes/animations/stickers, reactions, edits and deletion of its own registered sends, copy/forward, locations/venues/contacts/dice, polls/quizzes and closing them, Business checklists and editing them, and pin/unpin.

Native checklists require a Business private chat. Reactions and native copy/forward are available in ordinary bot chats/groups, not on behalf of a Business user. Business replies and edits require an active connection with reply rights and a recent incoming message. Media reuse is limited to currently accessible attachments for the same child bot; new arbitrary uploads are not supported. Static sticker previews are readable on demand.

The complete feature map and implementation references include prior capabilities and known limits. The live test register keeps real Telegram/provider checks separate from code and deployment verification.

Your data

History starts when a chat is connected; ChatMate keeps its latest 60 days. Earlier messages, Secret Chats and channels are unavailable. Manage connected chats, AI access, export and deletion at My data. Read the privacy policy.