PocketShell vs Happy
Happy is a genuinely good free, open-source remote for Claude Code and Codex - if that's all you need, use it.
PocketShell is for when you also want the terminal underneath: a real shell on any of your machines, files, git, monitoring, and P2P instead of a relay.
Happy's dedicated chat UI is arguably nicer for pure agent steering. PocketShell's agent story is intentionally different: browse Claude Code and Codex session history, resume a session into a live terminal, and get completion push notifications.
PocketShell combines a project file tree, code editor, git status and diffs, terminal tabs, and live dev-server preview in one mobile workspace connected to your own machine.
PocketShell pricing: Free includes 2 hosts, 5MB transfers, live stats only, 2 alerts, 2 project spaces, and the last 10 agent sessions. Pro is $4.99/mo or $39.99/yr for 10 hosts, unlimited alerts, history, spaces, stats history, and host-to-host transfer. Lifetime is $99.99 one-time and includes Pro.
We used publicly documented product features, pricing pages, docs, and comparison materials listed below, plus our own testing of PocketShell's host agent and mobile workflows.
Written and reviewed by Yash Agarwal, the developer of PocketShell. Competitor facts come from the primary sources linked on this page.
Methodology and correctionsSecurity wording here is scoped deliberately: authenticated P2P/TURN WebRTC traffic is end-to-end encrypted with DTLS. Terminal and agent traffic can use a server-readable WSS/TLS fallback while WebRTC is unavailable; file signaling has a documented key-exchange fallback. Read the security architecture for the exact paths.
Feature-by-feature
| Capability | PocketShell | Happy |
|---|---|---|
| Price | Free; Pro $4.99/mo or $39.99/yr; Lifetime $99.99 one-time. | Free. |
| Open source | The host agent is open source (Apache-2.0). | MIT open source client and relay; self-hostable. |
| Real terminal | Yes - arbitrary shell, tmux, any command on your machines. | No - agent-session scoped, not a general terminal. |
| Agent UI | Browse/resume into a live terminal; no in-app chat composer. | Dedicated chat UI with full CLI parity, voice, and parallel sessions. |
| Push notifications | Completion push notifications. | Push notifications. |
| Files/git | File tree, CodeMirror editor, git status/diffs, file transfer. | No file browser. |
| Monitoring/alerts | CPU/RAM/disk/network/temps, thresholds, widgets. | No host monitoring or alerts. |
| Preview | Expose a port with one command, then preview with hot reload on your phone over P2P. | No dev-server preview. |
| Transport | P2P WebRTC with TURN fallback; no vendor relay in steady-state data path. | E2E-encrypted relay; self-hostable; about 300ms relay latency disclosed. |
| Platforms | iOS and Android apps; host agent on macOS/Linux/Windows. | Claude Code and Codex controller from Happy docs. |
scroll the table horizontally
Choose honestly
Choose Happy if
- You only need a free Claude Code and Codex controller.
- A dedicated agent chat UI, voice coding, and parallel sessions matter more than a real terminal.
- You want MIT open source client plus relay and can accept the relay path or self-host it.
Choose PocketShell if
- You need arbitrary shell access under the agent session.
- You want files, git, monitoring, alerts, terminal tabs, and dev-server preview in the same app.
- You want P2P WebRTC to your own machines instead of a relay in the steady-state data path.
Questions people ask
Is Happy better for pure agent chat?
Can PocketShell send messages to agents in-app?
Does Happy replace a terminal?
Which is more private in the data path?
Put your hosts on your phone.
Install the host agent, scan the QR, and pair a machine you own. The host agent is open source under Apache-2.0.