Get started free
Compare Local agent orchestrators · same instinct, wider scope

The closest feature list on this page. The difference sits a layer below all of it.

Superset has almost every surface here: parallel worktrees, a diff viewer, terminals, an in-app browser, automations, a CLI and an MCP server. What it does not hand an agent is a machine of its own.

“Run 10+ parallel coding agents on your machine”: a macOS app that runs any CLI agent in its own git worktree, with terminals, a diff viewer and an in-app browser around it.
Superset · superset.sh
The short answer

Feature for feature this is the nearest neighbour intentic has, and the overlap is real rather than superficial. If you are on a Mac and your agents need only the toolchain that Mac already carries, Superset does the job and does it well.

Underneath, the two make opposite bets. Superset's agents run in your local environment, tuned by per-workspace setup scripts. Each intentic agent gets a container built from an image you approve, with credentials for your systems kept inside it.

The second split is what “remote” means. Superset reaches another machine through Superset Relay, on a paid plan and inside an organisation. An intentic sandbox dials its own tunnel out to your browser, and the platform never holds more than identity, a URL and grants.

Where we agree

Agents run in parallel on hardware you own, each in its own git worktree, on the subscription you already pay for — neither product proxies a model call or marks one up. Both put a diff between the agent and your tree, both keep a terminal next to it, and both can start a session with nobody watching.

Where they differ

A container, not the Mac as you left it

Superset shapes a workspace with setup, teardown and run scripts, but the tools those scripts reach for are whatever is installed on your machine. In intentic the machine is the artefact: an overlay Dockerfile you read and approve, so the agent that needs psql and a headless browser has them and your laptop does not.

Credentials the agent operates, not credentials in your shell

Capabilities wire a sandbox to GitHub, PostgreSQL, Sentry, Stripe, Discord, SSH or any MCP server. Each installs a real client and writes its secret inside the sandbox, injected per turn, with no path from the platform to it.

Remote, without a relay in the middle

Superset Relay is a service that routes traffic between your devices, and remote hosts sit on a paid plan with an organisation around them. An intentic sandbox opens nothing inbound and dials out; your browser holds the token that commands it, and the platform sits off that path entirely.

Where the machine doing the work can be

Superset ships for macOS today, with Windows and Linux still to come. A sandbox is Docker, so the work can happen on a workstation, a VPS, a Mac or WSL2 — and that machine need not be the one you are looking at.

Scheduled, or woken by what happened

Superset's automations run agent sessions on a schedule. intentic's also start on a push, an alert, a payment, an email or a chat message, each a fresh session with its own transcript and an optional guard command.

Head to head

4 of these 11 rows go to Superset. Those are the marked ones.
Dimension intentic Superset
Where the agent runs a Docker sandbox on hardware you own your Mac, in your local environment
Host operating system macOS, Linux, Windows via WSL2 macOS; Windows and Linux not yet shipped
Which agents it runs 5 native harnesses, plus any ACP agent as a capability any CLI agent at all, a dozen of them with presets
What you can change about the environment the image, the capabilities, the context loaded each turn per-workspace setup, teardown and run scripts
Where credentials live inside the sandbox, injected per turn your local shell
Reaching another machine a private tunnel the sandbox dials out; nothing inbound is opened Superset Relay, on a paid plan and an organisation
Starts on an event automations: cron, webhook, push, alert, email, chat automations on a schedule
Driving it from other software the MIT CLI a CLI, a TypeScript SDK and an MCP server
Previewing what the agent built the sandbox's ports mirrored into your browser an in-app browser with per-workspace port detection
Native desktop app browser workspace, plus two-way desktop sync a real macOS app
Licence MIT sandbox and CLI; the hosted platform is closed source available under the Elastic License 2.0

Pick Superset when

You work on a Mac, the tools your agents need are already installed on it, and you want the most finished native surface for running ten at once — with an SDK and an MCP server so your other agents can drive it. Superset is further along at exactly that, and one person working locally is inside its free tier.

Every claim above is checkable on superset.sh and in this repo. Where we have it wrong, open an issue and it gets fixed in the next build.