RemoteAgent.CHAT vs Claude Code Channels
Both bring Telegram to your AI coding agent. The difference is how much you have to set up — and whether your agent works while you're away.
What is Claude Code Channels?
Claude Code Channels is an official Anthropic feature (currently in research preview) that lets you push messages into a running Claude Code session via Telegram, Discord, or iMessage. It works as an MCP plugin: you install it inside Claude Code, create a Telegram bot via BotFather, configure the token, restart Claude Code with a special flag, and then pair your account with a code exchange. The key constraint: the channel only delivers messages while the Claude Code session is open and running on your machine. There is no always-on daemon — if your terminal session closes, messages are dropped.
What RemoteAgent.CHAT adds to Claude Code Channels
RemoteAgent.CHAT doesn't replace Claude Code Channels — it wraps it. The AI engine stays exactly as you configured it. RemoteAgent.CHAT adds the control plane: a Telegram bot, an always-on daemon, async notifications, and a web dashboard.
- ✓Zero configuration — one curl command installs the agent. No BotFather, no bot token, no plugin install, no Bun dependency, no session flags.
- ✓Always-on daemon — RemoteAgent.CHAT runs as a persistent background process. Messages arrive and tasks execute even when your terminal is closed.
- ✓Works with any AI runner — Claude SDK, Claude Code CLI, Gemini CLI, Aider, OpenCode, OpenClaw, or any custom binary. Not locked to Claude Code.
- ✓No Claude.ai subscription required — works with your own Anthropic API key, or with a completely different AI provider.
- ✓Async by design — send a command, lock your phone, get a Telegram notification when the task completes.
- ✓Agent offline alerts — instant notification if your machine or agent process goes down.
- ✓Multi-project switching — manage multiple codebases from a single bot. Claude Code Channels is scoped to a single open session.
- ✓Session history dashboard — every command and its status in a web UI. No equivalent in Channels.
- ✓Voice input — Telegram voice messages are transcribed and forwarded to the agent. Channels does not support voice.
- ✓Production-ready from day one — Channels is in research preview; the API and protocol may change.
Claude Code Channels alone vs Claude Code Channels + RemoteAgent.CHAT
| Feature | Claude Code Channels alone | + RemoteAgent.CHAT |
|---|---|---|
| Setup complexity | BotFather + plugin install + Bun + session flag + pairing | One curl command |
| Always-on (works when terminal is closed) | ✗ Session must be open | ✓ Persistent daemon |
| Requires Claude.ai login | ✓ Required | ✗ Uses your own API key |
| Requires Bun runtime | ✓ Required | ✗ Self-contained binary |
| AI runner flexibility | Claude Code only | Claude SDK, Gemini, Aider, OpenCode, OpenClaw, custom |
| Push notifications when task completes | ✗ No notification system | ✓ Telegram push on done or error |
| Agent offline monitoring | ✗ Not available | ✓ Instant Telegram alert |
| Multi-project switching | ✗ One session per terminal | ✓ /projects command |
| Voice message input | ✗ Not supported | ✓ Transcribed automatically |
| Image / screenshot input | ✓ Saved to inbox folder | ✓ Forwarded to the agent |
| Session history & audit log | ✗ Not available | ✓ Full dashboard |
| Production stability | Research preview — API may change | ✓ Stable, in production |
Real-world use cases
Claude Code Channels only works while your Claude Code session is running. If you close the terminal, messages are silently dropped. RemoteAgent.CHAT runs as a daemon — you send a task from Telegram, close your laptop, and get notified when it's done. No open terminal required.
Channels is exclusive to Claude Code. If your stack uses any other runner, it's simply not an option. RemoteAgent.CHAT wraps any AI tool and gives it the same Telegram interface — runner choice is yours.
Setting up Channels for Telegram requires: creating a bot via BotFather, copying a token, installing Bun, installing the plugin, restarting Claude Code with a special flag, and pairing your account. RemoteAgent.CHAT handles the bot for you — one curl command and you're done.
Channels is in research preview — Anthropic explicitly states the protocol may change. RemoteAgent.CHAT is in production and has been running for paying users. If stability matters, the choice is clear.
When Claude Code Channels alone is enough
RemoteAgent.CHAT isn't for everyone. If any of these describe you, you probably don't need it:
- –You're already deeply invested in the Claude Code ecosystem and don't want to add another tool.
- –You only need occasional mobile access and are fine keeping a terminal session open.
- –You want Discord or iMessage support — Channels supports both, RemoteAgent.CHAT is Telegram-only.
- –You want to react to external events (CI webhooks, monitoring alerts) pushed into your session — that's the core use case Channels is designed for.
Try RemoteAgent.CHAT free for 14 days
Full Pro access. No credit card. Connect Claude Code Channels in under 5 minutes.
curl -fsSL https://remoteagent.chat/install | bash