Claude Code Remote Control

Original Article ↗ Hacker News Discussion ↗

Comparison to SSH/tmux and Existing Workflows

  • Many say this duplicates long‑standing setups: SSH/mosh + tmux/screen + Tailscale/Termux/Termius, which already give persistent remote terminals from phones.
  • Critics argue Claude’s polling via Anthropic servers is a “most inefficient” re‑implementation of GNU screen; proponents reply that it avoids inbound connections and is easier for non‑experts.
  • Several emphasize that terminal UX on phones is poor (thumb typing, key chords, tmux shortcuts), so a purpose‑built mobile interface and voice input could be a real improvement.
  • Others insist tmux/screen are simpler than this remote control, and that abstractions here are “triangular wheels” for people unwilling to learn basic tools.

Security, Lock‑in, and Sandboxing

  • Some recommend running Claude Code inside containers/VMs or tools like bubblewrap‑tui; others highlight that Claude already has powerful local access once you grant commands, so this is not a new risk class.
  • Debate over “vendor lock‑in”: one side says tying your workflow to Claude’s client is a form of lock‑in, another says lock‑in refers to depending on proprietary services you can’t replace.
  • The mobile apps’ demand for GitHub access to list sessions alarms some; workarounds include throwaway accounts or repo‑scoped sandboxes.
  • A few worry about a future where codebases are only modifiable via proprietary agents, creating a captive ecosystem.

Bugs, Limitations, and UX Issues

  • Many report the feature as extremely buggy:
    • Remote sessions not enabled on some Max accounts; logout/login only sometimes fixes it.
    • Can’t reliably interrupt runs, sessions get stuck in “plan mode,” UI disconnects, doesn’t resume cleanly, and sometimes shows raw XML (e.g., for /clear).
    • One remote connection per session and flaky mobile handoff make multitasking hard.
  • General sentiment that Claude Code (web/desktop) is powerful but unstable, with frequent regressions and outages; some describe the codebase as “vibe‑coded” with weak testing.
  • Requests include API key support, logout‑all‑sessions, auto‑caffeinate, QR on first run, better context management, richer multi‑session views, and first‑class Slack/Telegram control.

Productivity, Lifestyle, and Ethics

  • Enthusiasts love being able to nudge agents, approve tools, review code, or iterate on ideas while walking, in bed, on commutes, or at the gym.
  • Others find “coding from the toilet/forest/bed” dystopian, seeing this as further erosion of boundaries and a driver of overwork and burnout.
  • There’s a broader debate about tools that push “do first, think later”: some fear more “vibeslop,” others say rapid prototyping plus human judgment can improve design, not replace it.

Ecosystem and Competition

  • Many alternative “remote Claude/Codex” setups exist: happy.engineering, Omnara, OpenClaw‑style harnesses, Telegram/Slack bridges, opencode web, HAPI, Crabigator, yoloAI, codecast, and DIY tmux/Tailscale workflows.
  • Some see this as Sherlocking smaller tools, but argue there’s still room for universal control planes, mission‑control dashboards for multiple agents, and richer mobile/voice‑first interfaces.