SideHub vs Paseo: which one to choose?
Paseo is a free, open source app to drive your coding agents from the desktop, the web or your phone. SideHub puts several CLIs to work on your machines, in their real terminal, and keeps a review between their work and your repository. What sets them apart, and when to prefer one or the other.
Last updated 2026-10-15, facts checked in the official documentation
What Paseo does well
Paseo is the most complete independent project for driving coding agents remotely, and it costs nothing.
Free and open source
Apache 2.0 license, no forced sign-in, no telemetry. You only bring your CLIs' credentials, which Paseo does not store.
Real native apps
Native iOS and Android client (not a web view), a desktop app that bundles its daemon with no setup, a web client and a CLI. Voice runs on the device by default.
Some forty agents
Claude Code, Codex, OpenCode, Pi and a few more natively, plus over 30 others through ACP (GitHub Copilot among them), each a one-click install.
Worktrees and delegation
One git worktree per task, tied to a pull request through gh when needed. An agent can hand part of the work to another provider or model.
End-to-end encrypted connection
QR code pairing and a relay that cannot read the traffic, or a direct connection over the local network, Tailscale or a tunnel. The code never leaves the machine.
Schedules and Hub
Cron schedules that start an agent, heartbeats that prompt the same conversation again. Paseo Hub adds GitHub, Slack and Discord triggers and multi-step YAML workflows, with structured outputs and conditions.
What differs
Paseo is a rich interface above your agents. SideHub is a control layer between their work and your repository. Point by point:
| Paseo | SideHub | |
|---|---|---|
| How the agent runs | An adapter per provider (native or ACP) starts the agent and translates its output into Paseo's interface: messages, diffs, permissions. | The real CLI binary in a terminal (PTY), as if you had typed it: same screens, same slash commands, and a plain shell next to it. |
| Getting started | The desktop app starts its daemon on its own. On a server, a headless daemon through the paseo CLI or the Docker image, paired with a QR code. | One agent per repository, installed once as a service that comes back with the machine (sidehub-agent service install), linked to your hosted workspace. |
| Supported CLIs | Some forty: Claude Code, Codex, OpenCode, Copilot through ACP and many more. | Claude Code, Codex, GitHub Copilot, Antigravity, Gemini (with an API key) and a plain shell, side by side. |
| Workflows | With Hub: YAML files in .paseo/workflows/, started by a GitHub, Slack or Discord mention or by hand, steps with structured outputs and if conditions. The documented format has no human approval step. | Multi-step workflows, a different CLI per step, approval steps and interactive steps where you work with the CLI before you validate, started by hand, on a cron, from a webhook or an event. |
| Review before the push | Diffs to review in the desktop app. The docs describe no approval the push would depend on. | 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 CLI | Possible by asking an agent to review another one's work in a fresh conversation. | Built into the review: a second CLI (Codex reviewing Claude, for instance) reads the round in read-only mode and ranks its remarks before you decide. |
| Cost | The docs do not mention a cost per run or per repository. | Tokens read in each run's transcript, turned into an estimated API equivalent, per run, per CLI and per repository. |
| Deliverables and team | Hub shares projects, workflows and activity between its members. Sharing settings and skills is announced. | Hosted team workspace with roles: shared agents, workflows and reviews, and Memory, where runs leave reports and documents everyone can read. |
| On the phone | Native iOS and Android app, voice. | Web cockpit, no native app: terminal, answers to the CLI's questions as cards, reviews to approve. |
| Price | Paseo is free. Hub: free self-hosted, Free at $0 (50 runs a month, 1 seat), Pro at $15 per seat a month. | 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
Paseo is enough if
- you want a free, open source tool that you can host entirely yourself;
- the native phone app, voice and the desktop app matter to you;
- you use agents SideHub does not start (OpenCode, Pi and others through ACP);
- starting an agent from a Slack or GitHub mention is enough, with no human approval between steps.
SideHub adds more if
- you want the real CLI in its terminal, with its screens and commands, and a shell next to it;
- nothing should ship unreviewed: a "To review" card, a second CLI that reviews, a push of the approved HEAD only;
- your workflows need an approval or a step where you work with the CLI;
- you want to know what each run and each repository costs, and keep deliverables in a hosted team workspace.
Both start the CLIs installed on your machine, with your own accounts: nothing stops you from keeping Paseo for the phone and SideHub for reviewed workflows.
Frequently asked questions
Paseo is free: why pay for SideHub?
To drive your agents from your phone or desktop, Paseo does it very well and for free. SideHub is paid for the control chain: approval steps, a review before the push, a second CLI that reviews, the cost of each run, Memory and a hosted team workspace. Starter stays free for one agent.
What is the difference between Paseo's interface and SideHub's terminal?
Paseo translates each agent's output into its own interface (messages, diffs, permissions). SideHub shows the CLI's terminal as is: what you would see by starting it by hand, menus, slash commands and new features included, with no adapter in between.
Paseo Hub has workflows: what does SideHub add?
Hub chains agent steps from a mention or a manual start. SideHub adds the human: approval steps, interactive steps, a review of every run that changes the repository, then a push of the approved HEAD, with the cost of each step.
Does SideHub have a native mobile app?
No. The cockpit is a web app built for the phone: terminal, cards to answer the CLI, reviews to approve. Paseo has the edge here, with native iOS and Android apps.
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).
Sources
- Paseo
- Paseo Hub (plans and pricing)
- Paseo docs: Hub workflows
- Paseo docs: Schedules
- Paseo docs: Supported providers
- Paseo docs: Security
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.