How to Use Claude Code in Telegram with Chatcode
Set up Claude Code in Telegram with Chatcode: run the agent on a server you own, drive it from a browser terminal, and follow the session from Telegram.
The native Claude Code Telegram channel is a great quick bridge, but it only works while a session is open on your machine, it’s Claude-only, and you can’t approve permission prompts from your phone. Chatcode takes a different approach: it runs the agent on a server you own and gives you one synced session across a browser terminal and Telegram — always on, and not limited to Claude. Here’s the full setup.
What you’ll have when you’re done
- Claude Code (or Codex/Gemini/OpenCode) running on your own server.
- A full terminal in the browser at app.chatcode.dev.
- The same session followed from Telegram, with notifications when long jobs finish.
- Nothing to babysit — sessions stay alive between visits.
Step 1 — Sign in
Go to app.chatcode.dev and sign in with magic-link auth — no password to remember, no extra account to manage.
Step 2 — Hook up a server
Chatcode runs your agent on a server you control:
- Easy mode: connect DigitalOcean and Chatcode spins up a droplet for you.
- Bring your own: install the Chatcode connection on your existing VPS and attach it to your account.
Either way, the agent runs on your hardware — the browser and Telegram are just windows into it.
Step 3 — Open a session and pick your agent
Choose a workspace folder under ~/workspace, pick an agent — Claude Code, Codex, Gemini, or OpenCode — and you land in a real shell. Sign into the agent once, exactly the way you would on your laptop. Each agent runs in its own sandbox, and you can flip the per-session sandbox toggle to set how locked-down it should be.
Step 4 — Link Telegram
Link Telegram to your account to follow the same session from the Chatcode Mini App and linked chats. From Telegram you get:
- The same session you see in the browser, in sync.
- Notifications for session activity and long-running work.
- Mini-app pages for picking a server and resuming a session.
The browser stays the full terminal; Telegram is the continuity and notification layer you carry in your pocket.
Step 5 — Work from anywhere
Start a task at your desk in the browser, then step away. When Claude Code finishes that long refactor or needs you, you get a Telegram update and can pick the session back up — from your phone, or from any browser later. Sessions stay alive between visits, so there’s no “did my laptop sleep?” moment and no lost messages.
How this compares to the native channel
| Native Channels | Chatcode | |
|---|---|---|
| Runs on | Your local machine (session must stay open) | A server you own (always on) |
| Surfaces | Telegram chat only | Browser terminal + Telegram |
| Agents | Claude only | Claude Code, Codex, Gemini, OpenCode |
| Messages while “off” | Lost (no queue) | Session persists |
| Safety control | Terminal prompts / skip permissions | Per-session sandbox toggle |
For the native setup and its trade-offs in full, see How to Connect Claude Code to Telegram.
Ready to try it? Start with Chatcode — it’s free to begin, on your own machine and subscription.
Frequently asked questions
Do I need to keep my laptop on to use Claude Code in Telegram with Chatcode?
No. Chatcode runs the agent on a server you own — a DigitalOcean droplet it provisions for you, or your own VPS. The session lives on that server and stays alive between visits, so you don’t keep a terminal open on your laptop.
Is Telegram a full terminal in Chatcode?
The browser at app.chatcode.dev is the full terminal view. Telegram is the continuity layer: a Mini App and linked chats that follow the same session, send notifications when long jobs finish, and let you resume from your phone.
Does Chatcode work with agents other than Claude Code?
Yes. The same setup runs Claude Code, Codex, Gemini, and OpenCode. You pick the agent when you open a session, each in its own sandbox.
Whose subscription and machine does it use?
Yours. Chatcode uses your own Claude (or ChatGPT) subscription and runs on your own server — it acts as a trusted relay between your browser/Telegram and the agent session, not a cloud that copies your repo elsewhere.