Compare

Bernato vs Claude Code Remote Control

Akshay Sarode
Quick verdict

CC Remote Control: zero install, official, free with Pro plan, one session at a time, tied to your terminal staying open.
Bernato: download a daemon, supervises every process on every machine, survives terminal close, works with non-Claude tools, and can sandbox macOS spawns with Seatbelt. Linux supports opt-in bwrap when available; Windows has limited Job Object containment without filesystem/network isolation.

Feature matrix

CC Remote ControlBernato
Continue session from phone
Spawn agents from phone
Survives terminal close
Multiple machines simultaneously
Restart-on-crash
30-day agent history
Works with Codex, Aider, custom processes✗ (Claude Code only)
Sandbox capabilities (Seatbelt)Permission prompts only✓ Per-agent, declarative
LAN-direct routingn/a (cloud relay)✓ local-first on LAN
Self-hostablen/a✓ Daemon yours, tunnel relay configurable
CostPro/Max/Team planFree 3 nodes · paid checkout hidden this cycle

Pick CC Remote Control if

Pick Bernato if

Use both

They don't conflict. CC Remote Control for daily-driver coding sessions. Bernato for the runs that need to outlive your terminal or run on a different machine. Detailed walkthrough: Claude Code Remote Control vs Bernato.

FAQ

Does Bernato need a Claude subscription?

Bernato runs whatever process you tell it to. If that process is Claude Code, you bring your Anthropic plan. If it's Codex, you bring your OpenAI key. If it's a Python script, you bring nothing extra.

Is Bernato a replacement for Claude Code?

No — Bernato runs Claude Code (or anything else). It's the supervisor, not the agent.