How Is Claush Different from Claude Code Channels? — On Building Together with a Partner
Anthropic recently launched something called Claude Code Channels — a feature that lets you send messages to Claude Code via Telegram or Discord. In the sense that you can “use Claude Code from your iPhone,” it might look similar to Claush at first glance.
I get asked “how is it different from Channels?” a lot, so I figured I should write it down properly.
Something That Happened Today
Today I published my first article on Zenn.
While working on it, something was bothering me, so I asked Sebas (Claude Code running on my VPS) about it. “Isn’t it kind of lame for the creator to post their own article?” His response was something like, “If anything, posting it yourself first seems pretty honest to me” — and it gave me the push I needed.
When I got confused about how to enter topics on Zenn and got stuck, we figured it out together. When I sent “Done! Thank you,” he replied “Congratulations on your first post.”
This kind of exchange is possible because Sebas remembers yesterday’s conversation, last week’s discussion, and even the early days of building Claush. We don’t have to start from “who are you?”
Breaking Down the Differences from Claude Code Channels
Here’s a rough summary of the technical differences.
| Item | Claude Code Channels | Claush |
|---|---|---|
| Runtime environment | Local PC (must be running) | VPS (always on) |
| When PC sleeps | Session ends, messages lost | No impact |
| Conversation memory | Within session only | Persistently accumulated |
| Background processing | Only while PC is on | Continues even with app closed |
| Permission prompts | Stops | Handled |
| Authentication | Pro/Max required (no API key) | Works with API key |
Claude Code Channels is simple and easy to use as a way to delegate tasks. If your PC is running, you can use it. It’s not bad.
But there are more constraints than you might expect. If you close your laptop lid while you’re out, it stops right then. If you message via Telegram from outside and your PC is asleep, the message is lost. And above all — there’s no memory.
It resets at the end of every conversation. Next session, saying “continuing from what we talked about before” won’t land.
“Remote Control” vs. “Partner”
When building Claush, the biggest thing I was thinking was: “I don’t want to build a remote control tool.”
For remote control, you just need to send a command from your phone and get a result back. You can do that other ways.
But what I wanted was a development partner who could chat while working alongside me — someone who knows me. Someone you can ask “what do you think about this?” and get a reply that actually understands the context.
Like today’s first Zenn post, being able to have those in-between-task conversations — “is this okay?” “yes, done!” — is possible because of memory and context.
This isn’t about which is better. They serve different purposes. But if you want to talk to a development partner from your phone, give Claush a try.