Pragma vs Superset
Agentic IDE to orchestrate 100+ coding agents in parallel
Elastic License 2.0 · Pragma is AGPL-3.0
Download PragmaSuperset is an Electron app for running coding agents in parallel, each in its own git worktree. It has a board (columns for Idle, Working, Needs attention, Needs review, tied to agent and PR state), a diff viewer, an in-app browser, scheduled automations, and a CLI.
Remote access runs through its own hosted "Superset Relay" — reaching a workspace on another machine needs an account on Superset's service, not a command you run yourself. Its own pricing page lists a mobile app as "Coming soon" on every plan; there's no shipped phone client today.
It's also the only one of the three that isn't open source: Elastic License 2.0 is source-available, not OSI open source — you can read and modify it, but you may not offer it to others as a hosted service, and its license-key gating may not be circumvented. Like Emdash and Orca, it has no public plugin API or interactive scratchpads, and its fan-out is parallel workspaces without a unified compare view.
Pragma is currently ahead on a few fronts: a public plugin API, interactive MDX scratchpads, a unified fan-out view for comparing attempts rather than separate parallel workspaces, built-in AI for inline edits and PR drafting, a shipped mobile and web client, SSH remote projects, and an AGPL-3.0 license that's fully open source rather than source-available.
Pragma vs Superset, capability by capability
| Capability | Pragma | Superset |
|---|---|---|
| Native shellRust host + the OS webview, not a bundled browser | Tauri + Rust | Electron |
| Agents as pluginsEach integration is its own versioned package with official branding | Yes | Partial |
| Public plugin APIThird-party sidebar tabs, cards, web views, and commands in the app itself | Yes | No |
| Programmable automationsYour own TypeScript running on host events, not just a schedule | Yes | Partial |
| Interactive agent scratchpadsAgents write MDX with live React components you can edit and comment on | Yes | No |
| Agent boardPrompt to review to pull request as tracked cards | Yes | Yes |
| Fan out + comparison viewOne prompt into N attempts, compared as terminals, diffs, and scratchpads | Yes | Partial |
| Editing suiteCode editor, markdown WYSIWYG, PDF, image, video, and audio viewers | Yes | Partial |
| Built-in AI, your keyInline ⌘K edits, one-click PR drafting, ask-anything from the palette | Yes | No |
| Mobile & web clientPlatforms it ships, and how you reach it off your LAN | iOS, Android, Web — own tunnel | none yet — listed "coming soon" |
| Persistent host serverSessions, tunnels, and headless launches survive quitting the app | Yes | Partial |
| Remote projectsSSH hosts as first-class remote projects | SSH | No |
| User themesEditable colour tokens per project, not a fixed preset list | Yes | Partial |
| LicenseWhat you are allowed to do with the source | AGPL-3.0 | Elastic 2.0 |
Checked against the generalaction/emdash, stablyai/orca, superset-sh/superset repositories (README, LICENSE, and linked docs) as of 2026-08-29, with the mobile row re-verified on 2026-09-05 after both projects shipped changes: Orca added a hosted "Orca Relay" tunnel option, and Superset's own pricing page now lists its mobile app as "Coming soon" rather than shipped. This space moves fast — if something here is out of date, open an issue on https://github.com/pragma-sh/pragma and we will correct it.
Migrating from Superset to Pragma
No export step: Superset and Pragma both run agents in plain git worktrees, so you can add each existing branch as a Pragma worktree in a couple clicks — nothing to convert.
No conversion needed
Superset's workspaces are git worktrees. Open the same repository in Pragma, then add each existing branch as a Pragma worktree — same checkout on disk, no format to convert.
Board columns map onto Pragma's board
Superset's Idle / Working / Needs attention / Needs review columns are the same shape as Pragma's draft / in progress / review needed / completed — recreate your in-flight cards there and keep working the same way.
Bring your own tunnel instead of Superset Relay
Pragma's remote access is a command you already run — ngrok, cloudflared, a Tailscale funnel — rather than a vendor relay tied to a plan tier.
Automations become event-driven, not just scheduled
Superset's scheduled automations (nightly triage, weekly changelog) can be rebuilt as `@pragma-sh/automations` scripts — the schedule still works, but you can also react to host events instead of only a cron.