Your agent reaches out.
A release is ready. A report needs a look. Your agent sends a focused update, question or file.
MCP · REST · CLIYour AI does the heavy lifting. You make the decisions that matter. Bring approvals, updates and files into Telegram—and send your reply right back.
↳ release.readyMessage delivered. Human input requested.
A browser simulation. No real messages are sent.
YOUR STACK, NOW WITH A HUMAN CHANNEL
No more watching a terminal for the next question. Give your agent a way to reach you, wherever your day takes you.
A release is ready. A report needs a look. Your agent sends a focused update, question or file.
MCP · REST · CLIGet the context in a familiar Telegram chat. Review the details and reply in your own words.
TEXT · PHOTOS · DOCUMENTSRelay returns the response to the right agent. Your workflow picks up with your decision in context.
A COMPLETE TWO-WAY LOOPGive the green light before your agent deploys, publishes or takes the next important step.
All checks passed. Shall I ship it?
Let’s do it. ✓✓Screenshots, photos and reports travel with the conversation. Everything you need to make the call.
Three options found. Which one should I explore?
Let long-running agents check in with progress or ask a specific question when they need your direction.
One-use pairing links connect your Telegram identity. No numeric chat IDs to copy into prompts.
Source-scoped credentials and permissions keep inboxes, replies and files bound to the right agent.
Self-host with protected credentials and metadata-only audit records. Bot secrets stay out of agent prompts.
Explore the free sandbox first. Choose a plan when you’re ready.
For founders and small agent teams
For production AI workflows
For multi-team automation
No. The preview on this page and the free sandbox are simulations. You can explore the complete round trip without an account, a card or Telegram credentials. Live delivery requires a configured gateway and a paired Telegram account.
AgentRelay is provider-independent. Connect an MCP-capable client such as Claude, ChatGPT, Codex or Qwen, or integrate your own workflow through the HTTP API or included command-line client. Check the docs for your client’s authentication setup.
Every agent has its own authenticated source. Relay binds your Telegram conversation to that source, then makes the reply available through its authenticated inbox. Your workflow reads that reply and decides what to do next.
No. Telegram credentials stay on your gateway. A short-lived, one-use pairing link connects the authorized Telegram identity, so you do not need to paste numeric chat IDs into agent prompts.
Yes. The gateway supports self-hosting, binds to loopback by default and stores secrets in protected files. The setup guide covers the gateway, Telegram pairing and client authentication.
One gateway. Your agents. A conversation away.
Try your first round trip Free browser sandbox · No signup · No Telegram credentials