chatwithdev vs Happy Coder: the session and the queue
Happy Coder is a free, open-source, end-to-end-encrypted way to take your Claude Code session with you — same session, phone or desktop. chatwithdev doesn't compete with that: it supplies what the session works on. Customer reports from your website become tickets in your Telegram; one tap sends a ticket to your agent and the PR comes back for review. Here's where each fits.
chatwithdev vs Happy Coder at a glance
| Feature | chatwithdev | Happy Coder |
|---|---|---|
| Job it does | Customer chat → your Telegram → ticket → dispatch to your agent (self-hosted runner or GitHub), PR reviewed by you. | A mobile client for your running Claude Code session — continue it from iOS, Android, or web. |
| Who can reach it | Your website visitors — no account or app — plus you. | Only you (end-to-end encrypted between your devices and your machine). |
| Where tasks come from | Customer reports, frozen into tickets that survive after the chat is gone. | You type the prompt in the session. |
| Needs a live session? | No — the ticket queue is durable; your runner polls and works jobs one-shot. | Yes — it mirrors a session that's running on your hardware. |
| Pricing model | Flat $15–50/mo per account — unlimited messages, no per-seat math. Free plan included. | Free and open-source; you bring your Claude subscription. |
| Ownership | You create the Telegram bot yourself at @BotFather and can revoke its token any time — your bot, your audience. | Strong — open-source, runs on your hardware, E2E-encrypted relay. |
Comparison reflects publicly listed plans and features as of mid-2026 — shapes, not exact prices. Always check current pricing on both sites.
When Happy Coder is the better choice
- You want to continue your exact session from your phone — free, private, no vendor in the middle.
- You value open source and E2E encryption for anything touching your code.
- You're happy typing prompts yourself and just want mobility.
When chatwithdev is the better choice
- You want the work to come to you: a visitor reports a bug, you tap ➕ Ticket, tap dispatch, review the PR.
- You want live chat on your site answered from Telegram regardless of the agent story.
- You want dispatch to run unattended on your VPS — no session to babysit, jobs are one-shot with progress streamed to Telegram.
Adding chatwithdev alongside Happy Coder
Keep Happy — it's free and does a different job. chatwithdev adds the customer side: the widget below goes on your site, chats land in your Telegram, and tickets dispatch to the same machine Happy mirrors. The runner guide shows the unattended path; setup takes a couple of minutes.
<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
Is chatwithdev a Happy Coder alternative?
No — Happy mirrors your own Claude Code session to your phone; chatwithdev turns customer reports into tickets and dispatches them to your agent with you as the gate. They operate on different ends of the same loop and combine well.
Happy is free — what does chatwithdev charge for?
chatwithdev is a hosted product: the website widget, the Telegram relay, tickets, and dispatch. There's a free plan; paid plans are flat per account ($15–50/mo as of mid-2026), never per seat. The chatrelay-runner CLI itself is MIT-licensed and free.
Can both run on the same VPS?
Yes. Happy wraps the interactive session you drive; chatrelay-runner is a separate small daemon that polls for dispatched tickets and runs one-shot jobs on a branch. They don't conflict — the runner refuses to start work in a dirty working tree.