Remote Control vs Happy Coder vs Shuriken

We make Shuriken. We tried to be fair; corrections welcome at office@shuriken.sh.

Quick answer#

Remote Control is Anthropic's own way to drive a local Claude Code session from the Claude app or claude.ai/code. It's official and included with your plan, but it's Claude Code only. Happy (Happy Coder) is free and open source, adds Codex, and encrypts end to end. Shuriken follows every chat of every agent on all your computers and servers, through its web app today, with native apps planned for November 2026.

All three keep your code on your own machine and let you steer from the sofa. Which one fits depends on how many agents you run, how many machines they run on, and how much you care about the extras.

At a glance#

Read on 22 October 2026 from Anthropic's docs, Happy's README, site and App Store listing.

What Remote Control does well#

It's official. No extra app, no wrapper, no third party in the path. Run claude --remote-control (or /remote-control in a running session), scan the QR code, and the session appears in the Claude app and at claude.ai/code. Auto-connect can turn it on for every session.

It's the full session. Your files, MCP servers, tools and project configuration stay available. Subagents and workflows stay in sync across every connected device. You can send photos and files from your phone, and type from the terminal and the phone interchangeably.

Pushes are thoughtful. Claude sends a push when a long task finishes or it needs a decision, and you can ask for one in the prompt ("notify me when the tests finish"). It skips pushes while you're typing at the terminal.

It survives a nap. If the laptop sleeps or the network drops, Claude Code reconnects when the machine is back. It only makes outbound HTTPS requests and opens no inbound ports. Trusted Devices (in beta) can require each phone or browser to be verified before it can steer a session.

The limits to know: one remote session per interactive process (server mode runs several), the local process must keep running, API keys aren't supported, and on Team and Enterprise an Owner must switch it on. It is, by design, Claude Code only.

What Happy does well#

Free and open source. MIT licensed, with the CLI, mobile app, desktop app and relay server all in the open. You can read it, fork it and ship your own build.

End-to-end encryption. Its App Store listing says sessions are end-to-end encrypted and its servers can't read prompts, responses or code.

More than Claude. happy claude and happy codex wrap each agent's own harness in your terminal, and its desktop app is the project's route for multi-model sessions.

Real native apps. iOS and Android apps are in the stores today, with pushes when an agent needs input or finishes. Its 1.8.0 notes add a voice assistant (one hour free, then a subscription).

The limits to know: it covers a handful of agents (Claude Code, Codex, Grok and, from 1.8.0, OpenClaw) rather than a long list, and the paid "Plus" tier is an in-app purchase.

Where Shuriken is different#

Every agent, every machine, one list#

Shuriken isn't a remote control for one session. It's a harness that runs your agents: Claude Code, Codex, Gemini CLI and 64 more, on every computer and server you've linked. Your phone shows all of it, across every project: a chat that's running shows it, and one that's waiting on you is easy to spot. See your agents on your phone.

The queue and voice, from the phone#

Type the next three messages while the agent is still working; they wait their turn. Or talk: Shuriken's voice is turned into text on your own computer by NVIDIA Parakeet by default, with a live transcript. Look at the chat's Changes before you say "carry on".

Accounts that move by themselves#

When an account reaches your switch point (99% by default) or the provider reports a limit, your chats move to another of your own accounts and keep going. That matters more on a phone than anywhere: you can't fix a "limit reached" from the sofa if fixing it means logging in on the laptop. See source switching. Use only accounts you own and are entitled to use.

The machines keep working#

Agents run in a background service, so closing the app window doesn't stop them. On a Mac, Cocaine mode keeps it running with the lid closed (yes, really). Or put a headless Shuriken on an always-on box and run chats there.

Honest gaps#

Our phone option today is a web app, not a store app. It installs to the home screen, and browsers never count as linked devices. Installed, it pushes account alerts, such as a device going offline or a source signing out, but not "a chat needs you": that push comes with the native apps. The native iOS and Android apps, built from scratch to feel like iOS and like Android, are planned for November 2026: here's the plan. Remote Control and Happy both have store apps with pushes today.

Which should you choose?#

• Only Claude Code, one machine, want official and free with your plan: Remote Control.
• Claude Code and Codex, want open source and a native app today: Happy.
• Many agents or many machines, several accounts, a queue and voice: Shuriken.

They don't exclude each other, either. Remote Control and Happy each attach to a session you start in your terminal; Shuriken runs its own chats on your machines. Plenty of people will keep Remote Control for a quick check on one terminal session and use Shuriken for everything else.

Codex, GitHub Copilot CLI and OpenCode have remote features of their own, set side by side in remote control for coding agents compared. For a step-by-step guide covering all the options, see how to run Claude Code from your phone, or the phone feature page. To try Shuriken, download it and open app.shuriken.sh on your phone.