SideHub vs Paradev: which one to choose?
Paradev (formerly Superset) is an open source desktop app that runs dozens of agents in parallel, each in its own worktree, all the way to the pull request and the merge. SideHub puts your CLIs to work on your machines (Linux, macOS, Windows), is driven from a browser 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-11-07, facts checked in the official documentation
What Paradev does well
Paradev is one of the most complete agent orchestrators around, open source and free locally, with something new nearly every week.
One worktree per task
Each workspace has its own branch, git worktree and terminals, created from a branch, a pull request, an issue or a Linear task. The product is built to follow a hundred agents at once.
All the way to the pull request and the merge
A diff pane to stage, commit, push and open the pull request, then a PR page with CI checks, review threads and the merge (squash, merge commit or rebase), without leaving the app.
More than twenty agents
The docs list 22 (Claude Code, Codex, OpenCode, Cursor Agent, Copilot, Gemini, Amp, Antigravity, Kiro…), and any CLI can be added as a custom agent.
Plugins: MCP tools and skills
A plugin bundles MCP tools and skills, installed once from the app for the agents on the machine: tools and skills for Claude Code and Codex, skills only for Kimi, Vibe and Grok.
A remote machine in one command
superset hosts add user@box installs the CLI on a machine reachable over SSH (macOS or glibc Linux), signs it in and runs it as a user service, with nothing typed on it.
Open source and automations
MIT licensed since November 4, 2026. With Pro, automations started by a GitHub, Slack, Linear, Sentry or Notion event, a webhook or a schedule, and an iPhone and iPad app.
What differs
Paradev is a workstation to take many agents to the merge. SideHub is a control layer that puts your CLIs to work on your machines and reviews their work before it ships. Point by point:
| Paradev | SideHub | |
|---|---|---|
| Where you drive from | The desktop app, on the machine or on another device signed into the same organization, and the iPhone and iPad app (iOS 26 or later). No interface in a browser. | A browser, on any device: a web cockpit for all your machines, nothing to install to drive them. |
| Operating systems | macOS app (Apple Silicon or Intel). Linux as an experimental build (AppImage x64). "Windows is not yet available". Remote hosts are Macs or glibc Linux. | Agent on Linux, macOS and Windows, installed as a service that comes back with the machine (sidehub-agent service install). |
| CLI permissions | By default, Claude Code starts with claude --dangerously-skip-permissions and Codex with codex --dangerously-bypass-approvals-and-sandbox. You remove them in each agent's settings. | In a terminal, the CLI keeps its permission prompts. An unattended workflow step runs without asking (claude with an explicit tool list), and a tool policy can put a call (git push, sending an email) up for approval or forbid it. |
| Supported CLIs | 22 built-in agents, plus any CLI as a custom agent. | Claude Code, Codex, GitHub Copilot, Antigravity, Gemini (with an API key) and a plain shell, side by side, in their real terminal. |
| Parallel work | One workspace per task, each with its branch and worktree, more than a hundred at once. | Several terminals and several agents per machine, a task queue per agent. The real CLI keeps its options: claude -w or codex --worktree open a session in its own worktree. |
| Automations | One prompt, one agent and up to 25 triggers (GitHub, Slack, Linear, Sentry, Notion, webhook, schedule), with Pro. A run that finds the machine offline is missed and not retried. The docs describe no multi-step workflow. | Multi-step workflows, a different CLI per step, approval steps and interactive steps, started by hand, on a cron, from a webhook or an event (automatic triggers with Pro). No native GitHub, Linear or Sentry trigger: they go through the workflow's webhook. |
| Review before the push | A diff pane, then review comments on the pull request. Nothing is enforced between the agent's work and the push. | 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. No pull request or merge from SideHub. |
| Review by another CLI | Not covered in the docs. | 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 and plans | Spend estimated from the agents' local logs, at API list prices, and gauges of the quota left on each Claude Code and Codex login, read from the provider. | Tokens read in each run's transcript, turned into an estimated API equivalent, per run, per CLI and per repository. The plan limit is detected when the CLI hits it, with no gauge of what is left. |
| On the phone | iPhone and iPad app included in Pro: start agents, follow them, review the diff. The computer must stay awake, online and running Paradev. Android announced. | Web cockpit, no native app, from Starter: terminal, answers to the CLI's questions as cards, reviews to approve. |
| Price | Free at $0 (local workspaces, app, CLI). Pro at $20 per user a month (remote access, automations, mobile). Team at $60 (cloud workspaces), Ultra at $200. | Starter free for one agent, remote control and mobile included. Pro at €10 a month (5 agents, automatic triggers), Business at €15 per member a month. |
Which one to choose
Paradev fits better if
- you work on a Mac and want a desktop app to run many agents in parallel, one worktree each;
- your work goes through GitHub pull requests: CI checks, comments, merge from the app;
- you use agents that SideHub does not start (OpenCode, Cursor Agent, Amp, Kiro…);
- you want automations on GitHub, Linear or Sentry events without going through a webhook.
SideHub adds more if
- you want to drive from a browser, with no desktop app, Windows machines included;
- your CLIs must keep their permissions, and unattended steps follow a tool policy;
- a job must chain several steps and several CLIs, with a human approval in the middle;
- nothing should ship unreviewed: a review, a second CLI that reviews, a push of the approved HEAD only.
Both use your own CLI accounts and do not resell model access: nothing stops you from keeping Paradev on the Mac for parallel sessions, and SideHub on a server for workflows reviewed before the push.
Frequently asked questions
Paradev is free and open source: why pay for SideHub?
To take several agents to the merge on your Mac, Paradev Free does it very well. Its remote access, automations and mobile app need Pro, at $20 per user a month. SideHub Starter is free for one agent, remote control and mobile included, and Pro costs €10 a month. The SideHub agent is open source too (MIT).
Does Paradev run on Windows?
No: according to Paradev, Windows is not yet available, and Linux is experimental. Its remote hosts must be Macs or glibc Linux. The SideHub agent installs on Linux, macOS and Windows, and the cockpit opens in any browser.
Does Paradev start the CLIs without permissions?
By default, yes: its docs give claude --dangerously-skip-permissions for Claude Code and codex --dangerously-bypass-approvals-and-sandbox for Codex, and you remove these options in each agent's settings. In SideHub, a terminal starts the CLI with its usual permission prompts; only unattended workflow steps run without asking, within a tool list and, if you want, a tool policy that puts some calls up for approval or forbids them.
Are Paradev automations as good as SideHub workflows?
They cover another need. A Paradev automation runs one prompt on one agent when one of its triggers fires, with native GitHub, Slack, Linear, Sentry and Notion triggers that SideHub does not have. A SideHub workflow chains several steps with a different CLI per step, stops for an approval or an interactive step, and opens a review before any push.
Does SideHub open pull requests like Paradev?
No. SideHub pushes the agent's branch once the work is reviewed and approved, and the pull request is opened on GitHub afterwards. Paradev creates the PR, shows the CI checks and merges from the app.
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
- Paradev
- Paradev pricing
- Paradev download
- Paradev automations
- Paradev mobile
- Paradev blog: Superset is now Paradev
- Paradev blog: Paradev is now MIT
- Paradev docs: Install
- Paradev docs: Supported agents
- Paradev docs: Claude Code
- Paradev docs: Codex
- Paradev docs: Workspaces
- Paradev docs: Diff viewer
- Paradev docs: Pull requests
- Paradev docs: Automations
- Paradev docs: Remote access
- Paradev docs: Keep agents running
- Paradev docs: CLI reference
- Paradev docs: Mobile
- Paradev docs: Usage
- Paradev docs: Plugins
Other comparisons
Try SideHub on one machine
Install the agent on your VPS, your laptop or your Windows PC, open a terminal from the cockpit and start the CLI of your choice. Free for one agent.