Comparison

Superset vs super.engineering (2026): Agent Workspace vs Native Rust Control Plane

Compare Superset and super.engineering (formerly Superconductor) for running parallel AI coding agents in Git worktrees. Native Rust performance vs a full agent workspace with automations, MCP, and remote access.

Last updated·

Superset and super.engineering (formerly Superconductor) are direct competitors: both are desktop apps that orchestrate Claude Code, Codex, and other CLI agents in isolated Git worktrees with diff review built in. The split is architectural and philosophical. super.engineering, which now calls itself "the native agent control plane," is a closed-source, keyboard-driven native macOS app written entirely in Rust with a GPU-rendered terminal, still in alpha with nightly-only releases. Superset is a shipping product with automations, a CLI and SDK, an MCP server, remote access across your own machines, and a team and enterprise track.


At a Glance

Supersetsuper.engineering
What it doesRuns 100+ AI agents in parallel with Git worktree isolation, chat, review, and browserRuns unlimited parallel CLI agents in worktrees from one keyboard-driven native interface
CategoryLocal-first agent workspace with remote hostsNative macOS agent control plane (alpha)
ArchitectureDesktop app100% Rust, Metal GPU-rendered terminal, no Electron (WebKit for browser tabs)
Agent supportAny CLI agent (Claude Code, Codex, Cursor Agent, OpenCode, Gemini CLI, Copilot, Grok, Kimi Code, Mistral Vibe, Amp, and more)15 listed providers (7 stable, incl. Claude Code, Codex, Cursor, OpenCode, Pi, Grok), plus any CLI agent
IsolationAutomatic Git worktree per taskWorktree per task (workspace → project → worktree → tab)
ForgesGitHub, plus Linear integrationGitHub, GitHub Enterprise, GitLab, self-managed GitLab
Remote / cloudRemote access: add any machine as a host and keep workspaces running when your laptop sleepsExperimental SSH remote workspaces (Linux or macOS hosts); app stays macOS-only
AutomationAutomations: scheduled agent sessions, CLI, TypeScript SDK, MCP server, Slack botsc CLI, experimental 1-8 agent teams, experimental sc browser automation; no scheduling
License / statusSource-available (ELv2), shipping productClosed source, alpha, nightly releases only

What Is Superset?

Superset is a local-first desktop workspace for AI coding agents. It launches Claude Code, Codex, Cursor Agent, OpenCode, Gemini CLI, GitHub Copilot, Grok, Kimi Code, Mistral Vibe, Amp, and other agent workflows inside isolated Git worktrees with persistent terminal sessions, and switching agents mid-session keeps your workflow intact. Around that core, it adds a built-in diff/file editor with commit, push, and PR creation from the Changes pane, a Pull Requests view, a chat panel, an in-app browser with port detection and Design Mode, and an MCP server so agents and tools can drive Superset. Remote Access lets you add any machine as a host so workspaces keep running when your laptop sleeps, and scheduled automations, a CLI, a TypeScript SDK, and a Slack bot cover unattended and recurring work. You can review inside Superset or jump into VS Code, Cursor, Xcode, or JetBrains. Source-available under Elastic License 2.0 (ELv2).

What Is super.engineering?

super.engineering, formerly Superconductor, is a native macOS app for running parallel AI coding agents, built entirely in Rust with a Metal GPU-rendered terminal and a sub-half-second cold start claim. Its pitch: web-technology tools cap you at a handful of parallel agents, while a native app runs unlimited agents, scaling with your hardware. Each task gets its own worktree with tabs for chat, terminal, files, diffs, and browser; a review panel supports line-anchored comment threads that can be dispatched back to an agent, plus triage of AI review findings; and an adaptive Git button walks each branch through commit, PR, CI fixes, and merge on both GitHub and GitLab. A bundled sc CLI exposes the app to scripts and agents, and an experimental orchestration layer runs teams of up to eight labelled roles, a lead plus specialists, with coordination state and agent-to-agent messaging. It is keyboard-driven and deeply customizable (saved layouts, per-workspace themes, picture-in-picture windows, sidebar sections), runs agents as local subprocesses on your own subscriptions with no accounts and no proxying, and is currently a closed-source alpha distributed as a free nightly download for Apple Silicon Macs.

Key Differences

Native Performance vs Product Surface

super.engineering's identity is the native build: 100% Rust, GPU terminal, no Electron, unlimited parallel agents, and a September 2026 performance release pitching 120Hz motion and instant startup. If raw UI speed and terminal fidelity are your top criteria, it is the most aggressive engineering effort in this category. Superset spends its effort on surface area instead: an in-app browser with Design Mode, port detection, chat, a Pull Requests view, an MCP server, automations, and Remote Access are all part of the product today. Fast chrome versus more product -- that is the core trade.

Automation and Scheduling

super.engineering has a genuinely good local CLI (sc) with JSON output, experimental orchestrated agent teams, and experimental agent-driven browser automation. But it has no scheduling, no webhooks, no HTTP API, no SDK, and no MCP server -- recurring work means scripting sc yourself. Superset ships automations that run agent sessions on a cron-style schedule on a device you choose, a CLI and TypeScript SDK to compose them, an MCP server so agents and tools can create workspaces and launch agents, and a Slack bot for dispatching and receiving runs. For unattended or recurring agent work, Superset has the built-in story.

Maturity, License, and Team

super.engineering is in alpha: nightly is the only release channel, the product is closed source with no public repo or changelog page, there is no pricing page, and its Teams and Enterprise page is "email us." Superset is source-available under ELv2, has published free and Pro pricing, and carries team features (unlimited users on Pro, Linear and Slack integrations) and an enterprise tier with SAML SSO and SCIM, audit logs, and a SOC 2 Type II report. Individual early adopters may not care; teams standardizing a workflow will.

Forges and Review

Credit where due: super.engineering supports GitLab (including self-managed) alongside GitHub, and its review panel -- line-anchored comment threads that dispatch to agents, AI-finding triage, and the adaptive Git action button -- is a thoughtful flow. Superset's review is its built-in diff/file editor with commit, push, and PR creation, a Pull Requests view with CI checks and line comments you can send to agents, and one-click handoff to VS Code, Cursor, Xcode, or JetBrains, with GitHub and Linear integration. If GitLab is your forge, super.engineering covers it natively today.

Remote and Mobile

super.engineering's remote workspaces are experimental and SSH-based: the app stays on your Mac and drives worktrees on a Linux or macOS host. It has teased an iPhone companion but has not shipped one, and its mobile session continuation relies on a third-party tool. Superset's Remote Access adds any machine as a host through a relay, with the full workspace GUI, and is in beta on the Pro plan; a Superset mobile app is listed as coming soon.


Pricing

Superset offers a free tier and Pro at $20 per user per month, or $15 per user per month billed yearly. super.engineering has no pricing page as of September 2026: the alpha is a free download with no account required, and its terms anticipate paid licensing that has not been announced. Both are bring-your-own-agent -- you pay Anthropic, OpenAI, and other providers directly.


Which Should You Choose?

Choose Superset if you:

  • Want scheduled automations, a CLI and TypeScript SDK, an MCP server, and a Slack bot around your agents
  • Need Remote Access across your own machines, team plans, or enterprise features
  • Prefer a shipping product with published pricing over an alpha
  • Want an in-app browser with Design Mode and port detection in the loop

Choose super.engineering if you:

  • Prioritize native performance: Rust, GPU-rendered terminal, no Electron
  • Are keyboard-driven and want deep layout, theme, and keybinding customization
  • Use GitLab (including self-managed) as your forge
  • Are happy riding an alpha on nightly builds

Verdict: super.engineering is the performance purist's take on this category, and the native engineering is real. But it is an alpha: closed source, nightly-only, no pricing, no scheduling or API surfaces, and macOS-only. Superset delivers the same worktree-orchestration core as a complete product -- automations, CLI, SDK, MCP, browser, Remote Access, and team features included. Try super.engineering if the native feel excites you; standardize on Superset if you need the workflow to be dependable today.


Frequently Asked Questions

Is super.engineering the same as Superconductor?

Yes. Superconductor rebranded to super.engineering; developer-facing names like the sc command, .superconductor/config.json, and SUPERCONDUCTOR_* environment variables remain during the transition.

Do both use Git worktrees?

Yes. Both create an isolated worktree per task. super.engineering organizes them as workspace → project → worktree → tab, with experimental cross-repo "shared context" branch groups; Superset attaches persistent terminals, diffs, and review to each worktree-backed workspace.

Is super.engineering open source?

No. It is closed-source proprietary software, currently free during its alpha, with no published pricing. Superset is source-available under the Elastic License 2.0 with free and paid tiers.

Which platforms do they run on?

Both are macOS-first. super.engineering requires macOS 14 or newer on a Metal-capable Mac and serves an Apple Silicon build, with Windows and Linux planned. Superset supports macOS on Apple Silicon and Intel, ships an experimental Linux build, has Windows planned, and also offers a CLI, an MCP server, and Remote Access to Linux or macOS hosts.