Launching today
Superset
Run an army of Claude Code, Codex, etc. on your machine
789 followers
Run an army of Claude Code, Codex, etc. on your machine
789 followers
Superset is a turbocharged IDE that allows you to run any coding agents to 10x your development workflow. - Run multiple agents simultaneously without context switching overhead - Isolate each task in its own sandbox so agents don't interfere with each other - Monitor all your agents from one place and get notified when they need attention - Review changes quickly with built-in diff viewer and editor Wait less, ship more.
Superset
Hey all,
I'm Kiet, one of the creators of Superset. We created Superset to reduce the time you spend waiting around for agents like Claude Code to run. Superset lets you kick off dozens of coding agent sessions in parallel. It works with any coding agents like Claude Code, Codex, OpenCode, etc. while allowing you to use your Pro/Max plans. It's a full featured IDE optimized for parallel agents workflows.
The last few months have seen incredible adoption from the most cutting edge teams from all over the world. I'm excited to see what you will build with Superset!
@flyakiet Are there any plans to integrate with issue trackers, CI/CD, or cloud IDEs?
Superset
@flyakiet @kimberly_ross We definitely plan to do these things!
Our Linear integration is live already, it needs some love but once the bones are in it won't be hard to add in support for other issue trackers. For CI/CD, we plan on having pipelines where agents can get notified and deployed based on CI events. For cloud, we actually plan to build our own cloud infrastructure - you can imagine our existing workspaces working pretty much the same regardless of them being cloud or local
The sandbox isolation is the right architectural call to prevent interference, but it creates the inverse challenge: when two agents are working on related tasks — say, a frontend and a backend agent that both need to agree on an API shape — how does Superset handle cross-agent context sharing? Full isolation is clean but can lead to agents making conflicting assumptions in silence. Is there a shared workspace layer agents can read from, or is isolation by design absolute?
Superset
@giammbo We are working on that, we are building in a memory layer where in your prompts to one agent you could '@' the context of another workspace to bring it into the chat or make it available for the agent in your current session to grab. We have yet to ship it but we are pretty excited about it
@avi_peltz The '@' workspace syntax is a really elegant solution — it keeps isolation intact while making context sharing explicit and intentional, which is exactly the right tradeoff. Curious about the granularity: when you '@' another workspace, is it the full agent context you're pulling in, or can you reference a specific artifact (like a schema file or an API spec) so the receiving agent gets exactly what it needs without the noise?
Superset
@giammbo I imagine the goal will be conversations can be searchable! agents probably will be able to pull down a conversation and then run grep / list messages / tetc.
There may be fun things we can do like maintaining llm-accessible indicies on long conversations or something but an agent with tools can go surprisingly far :D
Let's gooo massive fan of Superset product + team! One of the fastest executing teams I've seen!
Question for you guys: Do you think the future will see more local or cloud development? Right now I'm using my mac mini and ssh'ing into it, and it's great in many ways but can get messy with enough things running in parallel. Cloud is easier to manage but problem becomes continuing working from the CLI and all that. Where do you think things are heading?
Superset
@eliasstravik Thanks for the support as always Elias!
Doing the 10+ worktrees has been frying my machine, definitely see remote/cloud as the only way forward to get to 100+ agents in parallel
Superset
Now that chat is launched, focus will be Cloud+SSH
This looks really solid love the idea of running multiple agents in parallel
Quick question — with all these isolated environments, how are you handling security between them?
Like making sure one agent can’t access another or any API-related risks?
Superset
@shrujal_mandawkar1 thanks Shrujal! So in my head the tricky thing is it's a huge risk if any sandbox gets hacked, as they will have instances of users' entire sandboxes within them. One rogue agent is probably equally destructive with access to one vs 100 agents.
As a result our goal will be focused on buliding this out with security in mind first and foremost! We definitely need to consider the ways our sandboxes will be vulnerable as we scale out
@thesaddlepaddle That makes a lot of sense and yeah, even a single compromised sandbox can be pretty impactful
From what I’ve seen, issues usually come from sandbox escapes, misconfigured permissions, or unintended access between environments
Are you guys planning to isolate at infra level as well (like containers/VMs), or more at application level for now?
@thesaddlepaddle @shrujal_mandawkar1 at the infra level as well for sure!
Pally - AI Relationship Management
love this, it’s my daily driver now. replaced cursor, claude code, and conductor!
Superset
@hazhubble thanks Haz!! If you run into anything we're always happy to help :)
The waiting problem with Claude Code is real, but I'm curious how Superset handles the orchestration layer. When you have dozens of agents running in parallel, how do you decide which tasks are safe to run concurrently versus which ones need to be sequenced to avoid conflicts?
And with sandbox isolation per task, does each workspace get its own file system snapshot? Wondering how state gets reconciled if two agents end up touching related parts of the same codebase.
I use Claude Code daily for building my AI platform and parallel agent workflow conflicts are something I've been thinking hard about. Would love to understand more about how Superset handles those edge cases in practice. Congrats on the launch!
Superset
@joao_seabra great question. Each workspace gets a clone of the repo using git worktrees. We try to split them at task level but conflicts can occasionally happen. This happens in large engineering team working on codebases as well. Usually the agents are very good at merge conflicts, especially if we start including the trace and intent in the PRs.
Conflict has been less common than i expected. They mostly happen when multiple human team members are working on the same feature.
@flyakiet very cool, thanks for sharing a bit on this. Best of luck for this launch, looks super promising! Will be on my list to try.
Congrats on the launch. This is super cool! Are agents aware of how much ram they are using on the host machine to prevent slowness?
Superset
@valentin_po honestly that's a great idea for a feature! We do already have the breakdown for memory usage, so we could add it to the MCP to help us debug :)