chatwithdev vs Claude Code Channels: your door vs the customer door
Claude Code Channels (Anthropic's research preview) pushes messages from your Telegram, Discord, or iMessage into a Claude Code session you already have running — official, free, and good at what it does. What it deliberately isn't: a way for your customers to reach you. chatwithdev is that customer door, and it turns what walks through it into tickets your agent can act on. Here's the split.
chatwithdev vs Claude Code Channels at a glance
| Feature | chatwithdev | Claude Code Channels |
|---|---|---|
| Job it does | Website chat → your Telegram → tickets → dispatch (runner or GitHub) → PR you review. | Bridges your chat apps into a running local session; two-way, with permission prompts relayed. |
| Who can reach it | Your website visitors, no account needed — plus you. | A sender allowlist you control — in practice, you. Not a customer channel. |
| Needs a live session? | No — tickets queue durably; the runner polls, or GitHub dispatch needs no infrastructure at all. | Yes — events only arrive while a session is open (persistent terminal for always-on). |
| What the agent receives | A ticket in your words (AI-drafted from the transcript, you confirm); customer text is marked as data, never the prompt. | Whatever the allowlisted sender types. |
| Audit trail | Ticket states: open → queued → running → PR open → done, mirrored in Telegram and the dashboard. | The session transcript. |
| Pricing model | Flat $15–50/mo per account — unlimited messages, no per-seat math. Free plan included. | Free Claude Code feature (research preview, as of mid-2026). |
Comparison reflects publicly listed plans and features as of mid-2026 — shapes, not exact prices. Always check current pricing on both sites.
When Claude Code Channels is the better choice
- You want to message your own running session from Telegram or Discord — the official, zero-cost way.
- You want to pipe CI results or webhooks into a live session where Claude already has context.
- You want permission approvals on your phone while a long task runs at your desk.
When chatwithdev is the better choice
- You need a channel customers can use — a widget on your site, no accounts, answered from your Telegram.
- You want reports to become durable tickets that survive sessions, restarts, and your weekend.
- You want dispatch with a hard gate: your ticket wording, branch-only pushes, PR review before anything lands.
Adding chatwithdev alongside Claude Code Channels
Use both — they meet in the middle. Channels is how you talk to your agent; chatwithdev is how your customers' problems reach it, as tickets you approve. Add the widget below, connect your bot in setup, and see the full picture of how the two layers fit together.
<script src="https://www.chatwithdev.com/widget.js" data-chatrelay-project="your-project" data-chatrelay-convex="https://impressive-quail-820.convex.cloud" data-chatrelay-title="Chat with us" defer></script>
FAQ
Does Claude Code Channels replace chatwithdev's runner?
Different shapes. Channels pushes events into a live interactive session — great while you're driving it. The chatrelay-runner is an unattended queue worker: tickets wait durably, jobs run one-shot on a branch, and status survives restarts. If your VPS session isn't open, Channels events don't arrive; a queued ticket just waits.
Can customers message my Claude Code bot directly via Channels?
Channels is allowlist-gated by design — anyone who can message it can also approve tool use in your session, so you should never put customers on it. chatwithdev keeps customers on the website widget, and only your confirmed ticket ever reaches the agent.
Both use a Telegram bot from @BotFather — same bot?
Use separate bots: your Channels bot is a private line to your session; your chatwithdev bot is the relay for customer chats and ticket cards. Both are bots you own and can revoke any time.
Do I need Claude Code Channels to use chatwithdev?
No. chatwithdev's dispatch tiers work without it — the GitHub tier needs no infrastructure at all, and the runner tier is a small daemon on your VPS. Channels is a nice addition for steering interactive work, not a dependency.