Claude Code Channels, and where it stops

Released in March 2026, Channels connects a running Claude Code session to Telegram, Discord or iMessage. You start a session on your machine with the channels flag, link the chat, and from then on you can send it work from your phone and read the replies as messages.

If you already run Claude Code and you simply want to reach it from the sofa, this is the right tool and it costs nothing. Use it.

Channels is an interface, not a host. The session is still running on your computer, and the chat is a window onto it. Two consequences follow, and neither is a bug:

Your computer has to stay on. Close the lid and the session goes with it. The chat stays there looking perfectly healthy, which is the confusing part — you send a message from the train and nothing answers, because the thing you are messaging is asleep in your bag.

It stops when it needs permission. When the agent reaches something it wants approval for, it waits. If you are away from the desk, it waits until you get back — so a job you started before dinner can be exactly where you left it at bedtime, having done nothing for four hours.

Both are the same limitation wearing different clothes: the work is tied to a machine that is tied to you.

The usual next step is a VPS: rent a small server, install Claude Code, keep a session alive in tmux, reach it over SSH. It genuinely fixes the sleeping-laptop problem, and we have written up that path and the others in more detail.

What it does not fix is the second half. A session in tmux still stops and waits, and now it waits somewhere you have to SSH into to find out. You have moved the machine without changing the arrangement.

The alternative is to stop treating the agent as a program you left running and start treating it as someone who works somewhere.

That is what we do. Each agent gets its own cloud computer and its own Telegram bot — a name, a chat where nothing else happens, and a machine that is still there tomorrow with its repositories and half-finished work intact. Claude Code is installed and signed in already, so there is no API key to supply and no second subscription to hold. It has standing permission to get on with the job, so it does not stall waiting for you; it messages you when there is something to see.

The honest comparison: Channels is free and gives you your own machine with a chat interface. This costs money and gives you a machine that is not yours to touch, with a chat interface. If you like having a shell on the box, that difference will matter to you and Channels or a VPS is the better answer.

Stay on Channels if your work happens while you are at the machine anyway, and you just want a nicer way to reach it.

Move to a machine of its own if you keep starting things you cannot wait around for — the long migration, the scraper that should run hourly, the build you would like finished by morning.