Highwind vs Paradev (formerly Superset)

Native Mac workspace vs Electron agent workspace on worktrees

Quick summary

Paradev, formerly called Superset, is a source-available desktop app for running many CLI agents in parallel, each on its own git worktree. It has 22 built-in agents, a background daemon that keeps terminals running when the app quits, a browser with DevTools, a kanban linked to Linear and GitHub, and a hosted MCP server.

Highwind overlaps a lot: CLI agents, a browser agents can use, a task board and an MCP server. Highwind is a native Swift app, restarts crashed dev servers, starts the services a server needs first, and has iOS and Android device panes. Paradev is Electron and centres on worktrees. It shipped a device pane on October 18 and paused it on October 25.

Choose Paradev for parallel agents on worktrees with Linear and GitHub tasks. Choose Highwind for a native app that runs each project’s servers, agents, browser and phone simulator together.

Who should choose Highwind, and who should choose Paradev (formerly Superset)?

Choose Highwind if

  • You want a native Mac app rather than Electron.
  • You want dev servers restarted on crash and started in the order they need.
  • You want servers running again after a reboot, not only while the daemon is alive.
  • You want an iOS simulator or Android device in a pane your agent can use.

Choose Paradev (formerly Superset) if

  • You want each agent on its own git worktree, with a diff viewer, commits and PRs in the app.
  • You want terminals to keep running while the app is closed.
  • You want tasks linked to Linear and GitHub.
  • You want a code editor in the app, or remote access and an iPhone or iPad app on a paid plan.
  • You use Linux.

Feature comparison

FeatureHighwindParadev (formerly Superset)
What it is
A Mac app for dev servers, CLI agents, browsers and phone simulators, grouped by project
A desktop app for running many coding agents on git worktrees
Runs your dev servers
Each service has a command, a folder and a port
Run button starts dev servers in their own pane
Restarts a server when it crashes
Per service, up to 3 attempts, 2 seconds apart
Agents resume after a crash; nothing documented for run commands
Starts the services a server needs first
Starts each required service and waits until its port accepts connections
Setup scripts run in sequence; no service dependencies documented
CLI agents from several vendors
Claude Code, Codex, Gemini, OpenCode, Copilot and pi, plus any CLI added with a JSON file
22 built in, plus any CLI as a custom agent
Agent conversations resume after a restart
Each agent pane resumes its own session at launch
Agents relaunch automatically with their resume command
Servers run again after you quit or reboot
Services that were running start again at the next launch, agents resume and browser tabs reopen. Launch at login is optional
Daemon keeps terminals running when the app quits; a reboot stops them
Built-in browser with DevTools
WebKit pane with the Chrome DevTools frontend beside the page
In-app browser with a DevTools pane
Agents can use the built-in browser
21 browser tools over MCP, with an approval policy per action
superset browser commands and a Chrome DevTools Protocol endpoint per pane
Phone simulator or emulator in a pane
iOS simulator, Android emulator or Android phone in a pane. No physical iPhones. Needs Xcode tools or the Android SDK installed
Simulator and emulator pane shipped October 18, paused October 25
Agents can use the simulator or emulator
13 device tools over MCP: tap, swipe, type, screenshot, UI tree, logs and crash reports
Not available now
MCP server that controls the app
More than 70 tools for services, logs, views, tasks, the browser and devices. Off until you turn it on
Hosted MCP server for tasks, workspaces, terminals and agents
Shell commands as buttons
Per project, run in their own pane
Terminal scripts as one-click buttons
Split panes
Views with split panes, layout presets and floating windows
Split panes
Task board
Kanban board per workspace that agents can read and update
Kanban board for Linear and GitHub issues
Git worktrees and diff review
No worktree management or diff view
Worktree per task, diff viewer, commit and PR
Code editor
Plain text editor and sidebar, no syntax highlighting
Built-in editor and file tree
Configuration as plain files
Plain files in a .highwind folder
.paradev/config.json; terminal scripts live in user settings
Built with
Native Swift
Electron, source-available (ELv2)
No account needed
No account
Not documented for the desktop app
Platforms
macOS 14 and later
macOS, Linux (experimental), iPhone and iPad app. Windows planned, no date
Price
Free during the public beta
Free, Pro $20, Team $60, Ultra $200 a month

“Not documented” means we found no mention of it in Paradev (formerly Superset)’s documentation.

Is Paradev the same app as Superset?

Yes. Superset now calls itself Paradev. Its site is paradev.com and its documentation is at docs.paradev.com. The CLI is still called superset, and the MCP server is still at api.superset.sh.

What keeps running after you quit or reboot?

Paradev’s terminals run in a background daemon, so their processes keep running when the app closes, which Highwind’s do not. Its documentation says choosing Quit Completely in the menu bar ends all terminal sessions, and that a restart or logout stops them.

Highwind’s processes stop when Highwind quits. At the next launch, including after a reboot, it starts the services that were running again. Both apps resume agent conversations. If you turn on launch at login, Highwind does this without you opening it.

Phone simulators in Paradev and Highwind

Paradev shipped a Mobile pane on October 18, 2026, and turned it off on October 25 while it works on letting agents build for and check the simulator themselves. Its changelog says the pane will come back. Highwind has an iOS simulator, Android emulator and Android phone pane now, with 13 tools for agents.

Where Paradev is ahead

Paradev gives each task its own git worktree with a diff viewer, commits and pull requests, has a code editor, links tasks to Linear and GitHub, runs on Linux, and offers remote access, automations and an iPhone and iPad app on its Pro plan. Its daemon keeps processes running through a quit, where Highwind has to start them again. Highwind has no worktree features and runs only on macOS.

Frequently asked questions

Is Highwind a Superset alternative?

Yes, for Mac users who want a native app, dev server supervision and device panes. If parallel agents on separate worktrees are the main thing you need, Paradev, the new name for Superset, covers that and Highwind doesn’t.

Where does each app keep its data?

Highwind keeps workspaces, projects and tasks as plain files in a .highwind folder on your Mac. Paradev uses a .paradev/config.json file and user settings, and its MCP server is hosted at api.superset.sh.

Try Highwind

A native Mac app for your dev servers, CLI agents and browser panes. Requires macOS 14 or later.

Get Highwind

Other comparisons

Last reviewed November 2, 2026. Product features and prices change; tell us on the contact page if something here is out of date.

Sources