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.
This is the 2nd launch from Superset. View more
Superset 2.0
Launching today
Run 100s parallel coding agents, offload them to different machines. Rewritten from scratch to support remote workspaces. Share and collaborate with teammates in realtime. Works for any CLI agent.
Free Options
Launch Team
Superset
Hey everyone!
The pace of shipping softer keeps getting faster and it's been so much fun building at the bleeding edge, and trying to help as many people ship products people love as possible. We've had quite the grind to get this one out so we're hoping you all enjoy :)
New Features:
Remote workspaces - ship code across across devices / team members, continue working from anywhere
Automations - schedule agents to pick up tasks for you later (think of Openclaw's heartbeat feature)
Superset CLI - gives agents superpowers, and unlocks powerful new workflows
MCP refresh - works with v2 and backed by an expanded toolset
A general app refresh - the same Superset you know and love, just a bit more elevated
I'd call this a push to get out the building blocks for everyone's code factories, there's crazy new workflows that are possible now that even we're still discovering.
Excited to see what you all build, and if you have any feedback, we're here to help!
Product Hunt
Superset
@curiouskitty so we currently have it airtight at the following levels:
Your desktop by default is not accessible for remote access (it doesn't even load the module that has the ability to make the connection until you restart the desktop server). We actually recommend not turning it on and investing in remote workspaces with least-priviledge instead to improve security.
Permission must be granted to access a remote workspace - by default nobody has access to your remote workspace, owners instead need to grant it to users in settings (and they have to be a part of your org).
Hope that makes sense!
The interesting part here is not more agents. It is whether teams can trust the orchestration once those agents are spread across machines and repos.
How are you handling permission boundaries, failure recovery and audit history when one agent changes code that another agent depends on?
Superset
@pratikraj that's actually a class of issues we plan to invest in, but the main way to avoid these issues as always is to make sure agents are sufficiently isolated in sandboxes with least-privilege (one of the first steps is sandboxing which we now support). Agent audit history / failure recovery etc. is definitely a hot-button issue, we'll do our best to discover what the best practices are for it :)
Out of curiosity, who is running 100 parallel agents on real production codebases and what is the workflow that earns its keep? What is the most surprising one you have seen?
Superset
@michael_vavilov Ah we aren't running 100 yet to be honest - we can hover at 5-10 pretty consistently IMO!
One of our more useful flows is issues triage, in which we ask claude to use the Superset MCP to grab issues -> investigate -> pass a prompt to a new workspace and agent to work on the groomed ticket.
The automations are surprisingly useful too once you get a few running, because they also can spawn a bunch of agents themselves. I use it for sales stuff / email triage pretty frequently
BlogBowl
Congrats on the launch! Looks interesting!
I suppose 100 agents run in different branches? How do you handle merge conflicts after or is it something a human should do?
Superset
@danshipit thanks, agents are surprisingly good at merge conflicts these days! I recommend making sure you merge not rebase though as I've seen agents mess up rebases pretty badly (and it's harder to recover from).
Different branches is definitely our recommendation, as that way you can coordinate tasks so that you have fewer conflicts!
BlogBowl
@thesaddlepaddle Interesting, yeah different branches is a must-have, otherwise claude will do a lot of errors ;)
Superset
@lakshminath_dondeti right now we support 2 review paths
All GitHub reviews and comments are pulled into the sidebar and can be brought into the agents
All CLI agents for review will work out of the box since we work with any CLI agents like Claude Code, Codex, OpenCode, etc.
I was using Cursor, then Claude Code, then CC inside Cursor, and finally switched to Superset and haven’t looked back.
Awesome that I no longer need to worry about disk space limits killing my flow
Superset
@dave_yen1 thanks! We plan to keep it that way :)
Superset
@dave_yen1 we need to get you your remote Mac Mini setup!
Superset
@dave_yen1 thanks Dave!! 🙏