April 12, 2026
Hack it or lock it?
Show HN: Claudraband – Claude Code for the Power User
A DIY Claude remote fans love—critics say it feeds the walled garden
TLDR: Claudraband lets people keep and remotely control Claude Code sessions without bypassing login. The crowd split fast: power users cheer the control, while skeptics worry about Anthropic’s terms, single‑vendor lock‑in, and a missing license—plus a running joke that “Claude Code power user” is an oxymoron.
Claudraband just hit Show HN, pitching itself as a command-line sidekick that keeps Claude Code chat sessions alive, lets you pick them up later, and even run them from a tiny home server. The maker insists it’s not a hack—no login bypasses, you still sign into the official Claude Code—and it rides the real interface. Translation: it’s a remote control for Claude’s coding helper that power users can script and automate.
Then the comments arrived. First storm cloud: “How does this play with Anthropic’s” ToS “for paid accounts?” asked one user, sparking legal jitters and a chorus of “read the terms” replies. Next up, the lock‑in brawl: critics argue building tools that only work with Claude props up a walled garden and want support for rivals like Google’s Gemini and open projects. Practical jab: “License? Anyone?”—because shipping code without one makes lawyers twitch.
The jokes were flying too. The quip “Claude Code power user is an” oxymoron turned into a mini-meme, while veterans countered they’ve already wired this into editors and love the speed. One pro tip said Claude’s “Channels” can inject prompts cleanly, but admitted some features still require the clunky terminal slash commands. Verdict from Hacker News: builders adore the control; skeptics smell lock‑in, terms trouble, and paperwork. Cool tool—if the rules and rival support catch up.
Key Points
- •Claudraband wraps the official Claude Code TUI to enable persistent, resumable, and remotely controllable sessions.
- •It provides a CLI (cband), an HTTP daemon, an ACP server for editor integration, and a TypeScript library.
- •The tool is not a Claude SDK replacement and requires authentication through a real Claude Code session; all interactions pass through Claude Code.
- •Setup requires Node.js or Bun, an authenticated Claude Code, and tmux; an experimental xterm backend is available for headless fallback.
- •Examples and docs cover local/daemon workflows, ACP-driven editor integration (e.g., Zed/Toad), session tracking, and runnable TypeScript samples.