Paradev alternatives: what changed with the rename, and when to switch

Paradev, the app that was called Superset, is an MIT-licensed desktop app that gives each coding agent task its own Git worktree and branch, with a Free plan for one person working locally. Look elsewhere if you need Windows, if you would rather keep a terminal and manage worktrees yourself (cmux is free and GPL-licensed), or if you want each project open on one canvas with its own agents, browser and notes. Armadai, a paid Mac app, is built for that last case. Conductor, the closest match, stopped taking new users on 4 November 2026 after announcing it is joining Meta.

What changed when Superset became Paradev

superset.sh now redirects to paradev.com, and the documentation lives at docs.paradev.com. If you already used Superset, these are the changes you will notice:

• The data folder. The first time an updated app, CLI or host starts, Paradev moves ~/.superset to ~/.paradev, including worktrees, sessions and settings, and leaves ~/.superset as a link so old paths keep working. New workspaces go under ~/.paradev/worktrees/.
• Repository config. Paradev still reads an existing .superset/ folder in your repository. You do not need to change it. New repositories get .paradev/, and the FAQ says to move an old folder, if you want to, only once everyone on the team runs a current version.
• The CLI. The command is still superset: to keep a host reachable after you quit the app, the docs have you install the standalone CLI and run superset auth login and superset start --daemon, and environment variables keep names such as SUPERSET_ROOT_PATH.
• The licence. On 21 October 2026, superset.sh described the code as source-available under the Elastic License 2.0. Paradev's homepage and the repository's licence file now say MIT License, a standard open source licence.

Two other names share search results. Paradev says it is unrelated to Apache Superset, the business-intelligence tool, and that the Paradev hiring platform at joinsuperset.com is a different company.

What Paradev does, and what it costs

A Paradev workspace is a Git worktree on its own branch, with its own directory and terminal sessions. You create one per task, run any command-line agent in it (Claude Code, Codex, OpenCode, Cursor Agent and others), review the diff in the app and open a pull request. Agents run in terminals owned by a background daemon, so closing the window, quitting with ⌘Q or installing an update leaves them running; choosing Quit Paradev Completely, restarting or logging out ends them, and they pause while your Mac sleeps. Around that core it adds an in-app browser, Linear and Slack integrations, Remote Access to agents on other machines, Automations that start agents on a schedule or an event, a CLI, a TypeScript SDK and an MCP server.

Every plan uses your own Claude Code, Codex or other agent accounts; Paradev says it never proxies model calls.

When another tool fits better

• You need Windows. Paradev supports macOS on Apple Silicon and Intel, ships an experimental Linux x64 AppImage, and says Windows is planned with no date. Every app on this page is Mac-first; Conductor alternatives includes tools that run on Windows.
• You want isolation, not just separate files. Paradev's FAQ is clear that a worktree is not a sandbox: agents still share your machine's processes, network and files outside the worktree. Its cloud workspaces run agents in a cloud sandbox, but they are in early access, not yet available to every account, and the pricing page includes cloud hours from the Team plan up. cmux's paid plans offer Cloud VMs instead.
• You would rather keep a terminal. cmux is a free, GPL-licensed macOS terminal built on Ghostty, with vertical tabs, split panes, notification rings when an agent needs attention, an in-app browser and a socket API.
• You want projects, not branches, as the unit. Every Paradev project must be a Git repository and each workspace is a branch; for work outside a repository it offers sessions in a scratch folder. If what you juggle is several separate projects, each with its own agents, browser, notes and tasks, an app organised around the project fits that better.

Paradev and Conductor, now that Conductor is winding down

Conductor and Paradev use the same model, one worktree and one branch per task. For new users the comparison has ended, because Conductor no longer takes sign-ups. Conductor's announcement sets out the timeline:

1. 4 November 2026: no new sign-ups or downloads. Existing free users cannot upgrade, and Pro users keep Pro features for free.
2. 13 November: Conductor Cloud goes read-only. You can read old chats and export data, but not send messages, and active subscribers get a refund.
3. 20 November: Conductor Cloud shuts down and deletion of Cloud data begins.
4. Early 2027: local Conductor, which gets new models and critical bug fixes until then, starts winding down, and Conductor deletes user data when the app shuts down.

To keep your work, right-click a cloud workspace and choose Transfer to local, or export everything from Settings → Account → Export data.

Paradev publishes a migration guide for Conductor users. Because a Conductor workspace is an ordinary Git worktree, you add the same repository folder Conductor used, then right-click the project and choose Import untracked worktrees, leaving Run setup script off because those worktrees are already set up; nothing is copied or moved. Scripts move from conductor.json to .paradev/config.json, where each command set is an array. The guide's example turns this:

{
  "scripts": {
    "setup": "bun install && cp \"$CONDUCTOR_ROOT_PATH/.env\" .env",
    "run": "bun dev --port $CONDUCTOR_PORT",
    "archive": "docker compose down"
  }
}

into this:

{
  "setup": ["bun install", "cp \"$SUPERSET_ROOT_PATH/.env\" .env"],
  "run": ["bun dev"],
  "teardown": ["docker compose down"]
}

The archive script becomes teardown, which runs when you delete a workspace. CONDUCTOR_PORT has no equivalent, because Paradev detects the ports a workspace listens on instead of assigning them, so remove --port unless your app needs a fixed one. One warning from the guide matters more than the rest: do not archive an imported workspace in Conductor, because archiving deletes the directory that is now your Paradev workspace. Quit Conductor instead.

The options side by side

For more apps, including Anthropic's own desktop app, see apps for running multiple Claude Code agents on a Mac.

Armadai, if you work across several projects

Armadai is a native macOS app that lays work out on an infinite canvas. Each project folder becomes a workspace with tiles for Claude Code, Codex, terminals, a code editor, a multi-tab browser, notes and a task board, and several workspaces sit side by side. You zoom out to see every project and zoom in to work on one, or switch to Tab View for a workspace per tab.

The differences from Paradev that matter in practice:

• What a workspace is. In Paradev a workspace is one task on one branch. In Armadai it is one project, with as many agents as you add. When you hand a task off from the board to Claude Code or Codex, Armadai gives that run its own Git worktree and brings successful work back as a draft pull request. If one worktree per task is the whole workflow you want, Paradev is the more direct fit.
• Who needs you. Armadai's sidebar lists sessions across every project as working, idle or waiting, and for requests it supports you can approve from the sidebar without leaving the project in view.
• A lead agent. The master agent runs Claude Code, Codex, Grok or Cursor and can open workspaces, launch and message agents and arrange the canvas from one conversation.
• Agents in conversation. Coordinate connects Claude Code and Codex inside one project to exchange plans and reviews, with a message budget you set and a transcript that stays on your Mac.

Where Paradev is ahead:

• Price and licence. Paradev is free for one person working locally and MIT-licensed. Armadai costs $20 a month or $120 a year, the 7-day free trial needs no card, and there is no free plan.
• Phone, remote hosts and cloud. Paradev's iPhone and iPad app is on the App Store for Pro users, and Remote Access and cloud workspaces keep agents reachable away from your Mac. Armadai Remote for iPhone is a beta on TestFlight; Remote describes it.
• Keeping agents alive. Paradev keeps terminals running after you quit by default. Armadai does it once you enable the background session helper and choose Keep Running and Quit; Codex Agent and IDE tiles still close with the app.
• Event-driven runs. Paradev's Automations start agents on a schedule or when an event comes in. Armadai's plans list scheduled tasks, and its homepage describes no event triggers.

Plans and what each includes are under pricing.