Comparisons

SideHub vs Claude Code Remote Control: which one to choose?

Remote Control drives Claude Code on your machine from your phone, included in your Claude plan. SideHub puts several CLIs to work on your machines and keeps a review between their work and your repository. What sets them apart, and when to prefer one or the other.

Connect your first machine

Last updated 2026-10-15, facts checked in the official documentation

What Remote Control does well

It is the official way to follow and start Claude Code sessions from another device, and it covers that need very well.

New sessions from your phone

In server mode, claude remote-control waits in a directory and creates a session each time you ask from claude.ai/code or the Claude app: up to 32 at once by default (--capacity).

One worktree per session

With --spawn worktree, each on-demand session gets its own git worktree: several tasks in parallel without stepping on each other.

Included in Claude plans

Available on Pro, Max, Team and Enterprise, with nothing to install beyond Claude Code. On Team and Enterprise, an Owner turns it on first in the admin settings.

A real mobile app

Native Claude app on iOS and Android, a QR code to open the session, push notifications when a long task finishes or a decision is waiting, a diff pane of the changes.

Everything stays on your machine

Files, MCP servers, tools and project settings stay local. The session only makes outbound HTTPS requests and opens no inbound port.

Back after a drop

In an interactive session, Claude Code reconnects on its own after sleep or a network drop. In server mode, a crashed session comes back as soon as you send it a message.

What differs

Remote Control is a window on Claude Code. SideHub is a control layer above several CLIs. Point by point:

Claude Code Remote ControlSideHub
Getting startedA claude remote-control server to start in each directory and keep alive (tmux or screen on a remote machine). Once stopped, its sessions can be resumed for about four hours; after some ten minutes without network, it exits.One agent per repository, installed once as a service that comes back with the machine (sidehub-agent service install). Terminals and sessions then open from the cockpit.
Supported CLIsClaude Code only.Claude Code, Codex, GitHub Copilot, Antigravity, Gemini (with an API key) and a plain shell, side by side.
Account and billingA claude.ai sign-in is required. No API keys, no Bedrock, Google Cloud Agent Platform, Foundry or LLM gateway (ANTHROPIC_BASE_URL).Each CLI runs as you set it up: subscription or API key. SideHub starts the real binary and does not resell access to the models.
WorkflowsOne conversation per session. Scheduling goes through other Claude Code features (scheduled tasks, routines).Multi-step workflows, a different CLI per step, approval steps, started by hand, on a cron, from a webhook or an event (automatic triggers on the Pro plan).
Review before the pushThe diff pane shows the changes. Commit and push happen in the session, under Claude Code's permissions, without a dedicated review.Every run that changes the repository opens a "To review" card: diff, approve or request a fix. SideHub only pushes the HEAD you approved, never forced.
Review by another CLINot built in.A second CLI (Codex reviewing Claude, for instance) reads the round in read-only mode and ranks its remarks before you decide.
Cost/usage shows your plan usage, with no cost per session.Tokens read in each run's transcript, turned into an estimated API equivalent, per run, per CLI and per repository.
Several machinesEach machine's sessions show up in the claude.ai/code list, only where a server is already running.One cockpit for all your machines (VPS, laptop, Windows): online or not, CLIs installed and signed in, one-click agent update, a task queue per agent.
On the phoneNative app, push notifications.Web cockpit, no native app: terminal, answers to the CLI's questions as cards, reviews to approve.
PriceIncluded in Pro, Max, Team and Enterprise.Starter free for one agent, Pro at €10 a month (5 agents, automatic triggers), Business at €15 per member a month.

Which one to choose

Remote Control is enough if

SideHub adds more if

They do not exclude each other: SideHub starts the real claude CLI with your account, and Remote Control remains a Claude Code feature.

Frequently asked questions

Does SideHub replace Remote Control?

Not if you only use Claude Code and mostly want to follow it from your phone: Remote Control does that very well, at no extra cost. SideHub helps when several CLIs work on your machines and their work must be reviewed before it ships.

Can Remote Control drive Codex or Copilot?

No, it only serves Claude Code. Each vendor offers its own remote access for its CLI; SideHub brings Claude Code, Codex, Copilot and Antigravity into one cockpit.

Do I need an API key to use SideHub?

No. The CLIs use your subscriptions as you signed them in on the machine. An API key works too, where Remote Control requires a claude.ai sign-in.

Does my code go through SideHub?

No. It stays on your machine. SideHub receives orders, run statuses, token counts and terminal output, relayed live to the cockpit and not stored (except the last lines of a failed run).

What happens when the machine restarts?

With Remote Control, you start claude remote-control again in each directory. The SideHub agent, installed as a service, comes back on its own and shows online in the cockpit.

Sources

Other comparisons

Try SideHub on one machine

Install the agent on your VPS or laptop, open a terminal from the cockpit and start the CLI of your choice. Free for one agent.

Connect your first machine