MAO vs Paradev (formerly Superset): which should you use to run coding agents in parallel?

Paradev, formerly Superset, is a desktop app for macOS, with an experimental Linux AppImage, that runs Claude Code, Codex, OpenCode or any other CLI coding agent in a terminal, gives each task its own Git worktree and branch, and adds review, pull requests, an in-app browser and automations around them. Its source is public under the Elastic License 2.0, and it has a free tier with paid seats. MAO is a desktop canvas for macOS, Windows and Linux where each agent is a real terminal node, and agents you wire together hand each other tasks and drive a browser, an Android device or an iOS Simulator. Choose Paradev if you work on a Mac and want a free, source-available tool with event-driven automations and cloud workspaces; choose MAO if you need Windows, want agents and their connections laid out on a canvas, or want phone testing and remote workspaces in a one-time purchase.

What is Paradev (formerly Superset)?#

Paradev is the new name of Superset: a desktop workspace that runs coding agents in parallel, each task in its own Git worktree.

The rename is recent. superset.sh now answers with a permanent (308) redirect to paradev.com, whose home page carries the banner "Superset is now Paradev", and the GitHub repository moved to ParadevAI/Paradev. Some names stay: the CLI command is still superset. Paradev's site also notes it is unrelated to Apache Superset, the business-intelligence tool.

Paradev's docs describe it as a desktop app with a full interface, not a terminal app. Agents run in terminals, backed by a background daemon so running processes survive app restarts, and next to them sit a Changes pane, a pull request pane with checks and review threads, a file editor and an in-app browser. It has built-in support for over twenty agents, from Claude Code, Codex and OpenCode to Cursor Agent, Copilot, Gemini and Amp, and runs any other CLI agent as a custom agent. It never proxies model calls: agents use your own subscriptions and API keys.

Each project workspace is a Git worktree on its own branch, with its own terminals and ports. Paradev's FAQ is direct about the limit: a worktree is not a sandbox, so agents still share the machine's processes, network and files outside the worktree, and worktrees do not prevent merge conflicts.

How do MAO and Paradev differ?#

Both run CLI agents in terminals and give each task a Git worktree; they differ on platforms, licence, price model and how agents and devices are laid out.

When does Paradev fit better?#

When you work on a Mac, want the source, and want agents started by events or kept running in the cloud.

• It has a free tier. Free covers one user with local workspaces, the desktop app and the CLI, with no time limit. MAO's trial lasts 7 days and covers one workspace and one project.
• The source is public. Paradev's code is on GitHub under the Elastic License 2.0, so you can read it and self-host within that licence's terms. MAO is closed source.
• Automations start agents on events. On Pro, agent sessions start on a schedule or when a GitHub pull request, a Slack message, a Linear or Sentry issue or a webhook arrives, with a run history and retry.
• More agents are built in. Its supported-agents table lists over twenty agents, including Cursor Agent, Copilot, Amp and Devin, with status, resume and usage tracking where each agent allows.
• Review and merge stay in the app. The pull request pane shows checks and review threads and merges, and Design Mode sends a clicked page element, its styles and a screenshot to an agent.
• Cloud and mobile. Team and Ultra add cloud workspaces that run without your computer, and the iPhone and iPad app (Pro) lets you answer agents and review diffs away from your desk.
• A CLI, SDK and MCP server. Scripts and other agents can create workspaces, launch agents and read their terminals.

When does MAO fit better?#

When you need Windows, want the whole team of agents on one canvas, or want phone testing and remote work in a one-time purchase.

• Windows and a supported Linux build. MAO runs on Windows, Linux (Wayland and X11) and macOS. Paradev's Linux AppImage is experimental and Windows is not yet available.
• A canvas you can see. Agents, notes, files, browsers and devices sit side by side, and the wires between them show who works with whom.
• Wires decide what an agent can reach. An agent finds only the peers, notes and portals it is connected to, and a task sent with mao ask comes back to the sender by task ID.
• Phones and simulators. A wired agent taps, types and reads logcat on an Android emulator or phone, or drives an iOS Simulator on a Mac. Paradev's docs do not describe device testing.
• Your own server, no subscription. Remote workspaces over SSH, and WSL workspaces on Windows, come with the one-time MAO licence; Paradev's remote access is a Pro feature.

How do I compare them on a real task?#

Give both the same task with two independent parts and watch how the work moves.

1. 1Pick a change with two parts that touch different files, such as an API endpoint and its tests.
2. 2In Paradev, create one workspace per part, start an agent in each, then review the changes and open a pull request from the app.
3. 3In MAO, create one layer per part, start an agent on each, wire them so one reviews the other's work, then land each layer into Ground.
4. 4Compare how you followed both agents, how work and feedback moved between them, and what was left for you to do by hand.

Frequently asked questions#

Sources#

• superset.sh: answers with a 308 permanent redirect to paradev.com.
• Paradev home page: the "Superset is now Paradev" banner, "formerly Superset", and the note that it is unrelated to Apache Superset.
• Paradev llms.txt: source-available under the Elastic License 2.0, platforms, the plan summary, and no proxying of model calls.
• Paradev on GitHub: the README's downloads and supported agents, and the LICENSE (Elastic License 2.0).
• Paradev docs: Install and FAQ: macOS, the experimental Linux AppImage, no Windows yet, the CLI on Linux, the iPhone and iPad app, worktrees that are not sandboxes, and terminals that survive restarts.
• Paradev docs: Supported Agents and Chat UI: the built-in agents, custom agents, and the upcoming chat over the Agent Client Protocol.
• Paradev docs: Workspaces: a Git worktree, branch, terminals and ports per workspace, and separate clones for cloud workspaces.
• Paradev docs: Agent Sessions & Forking and Agent Orchestration: Continue with another agent, fork, and the superset:orchestrate skill.
• Paradev docs: In-App Browser and Computer Control: the browser pane, Design Mode, superset browser, the CDP endpoint, and the computer skill.
• Paradev docs: Remote Access: hosts through the Paradev relay, set up over SSH or with superset start --daemon.
• Paradev docs: Automations: agent sessions on a schedule or an event.
• Paradev pricing: Free, Pro, Team, Ultra and Enterprise.
• MAO product facts: platforms, supported agents, price and free trial.
• Run a shell or agent and Switch an agent node to chat mode: terminal nodes and chat mode.
• Create a worktree layer and Land a layer into Ground: layers as Git worktrees and landing them.
• Connect agents, notes, and portals and Send a task and collect its result: wires that grant access, and mao ask, mao send and mao result.
• Browser and device portals and Remote workspaces: browser, Android and iOS Simulator portals, SSH and WSL workspaces.

Checked on 2026-10-28.