Superset 2.0 represents a fundamental architectural shift from a local-first Electron application to a distributed client-host model, where the core engine runs as a host service on any server while the Electron app functions as a client, enabling horizontal scaling to support hundreds or thousands of coding agents across multiple machines in real-time.
Deep Dive
Prerequisite Knowledge
- No data available.
Where to go next
- No data available.
Deep Dive
What the heck is Superset 2.0?Added:
Hey guys, I am so excited to show you V2 of Superet. So, we've been kind of heads down for a couple weeks now building this V2, which is what you are seeing in front of you right now. And the reason we're calling it V2 is is because it's essentially a from scratch rewrite. And while you can see it a little bit in the cosmetics, looks a little different than what V1 is in V2. The whole root of it is different. So the reason that we rebuilt superset was because we had originally built superset to be an electron app local first and we had built it with the assumptions that you would be able to run hundreds of coding agents on your machine and because as engineers we wanted to use our product as if it's like right there like you want to control the code you want to control what's on the machine. Um so you got started with that assumption and it had worked uh up until 10 20 workspaces and uh eventually you start to hit the physical limit of what you can hold on a single machine. So um they got us on a journey to essentially take the core of what Superset is great at which is this kind of engine that drives the work tree management and the um like file tree and the divs and all this and essentially repackage it in a core that's we call a host service which is like a in game engine terms is like a host client uh type where you know if you play multiplayer games you can host a server and other clients can join that server.
We've taken it and rearchitected it such that the electron app is actually still an electron app. Uh but the shell UI here is a client and the core of the electron app is now a host and what we can do is take that host and essentially put it on any other server and your electron app as the the shell here can still connect to it and you can connect a client multiple clients to multiple hosts. So manual relationship and what you have is this. So if you're looking at this, this is a, you know, very regular superset shell. You can do all this, run cloud code, all of the good stuff that we know and love. Let's run cloud here. Make sure you skip permission. Sure. And continue. Um, all of the stuff except for this is running on a machine called Cottown. But my actual machine like if I do a who am I?
This is not my machine. This is a Mac that is actually sitting somewhere in SF in my co-founder's apartment and I'm able to use it the same way. And what we got here is also you know the file tree is here. Let me just like what if I just delete this file. Uh it show file was deleted on this. It's showing the deletion here. It's all in real time.
And I can even like edit all of this in real time as well. So you get all the superet nicities except for it's not on this machine. It's sitting somewhere else. And with this architecture, we can essentially let you drive superset from any app and it scales horizontally. So you can put this as on as many machines as you can and you can still talk to it through superset and use all the ID the same way in real time. Um and that will enable us to of course allow you to bring your own cloud, bring your own machine, you have a Mac Mini, you can put it on. Um, but it also allows us to provision a machine for you and kind of use the same architecture to give you a machine without much magic and say, "Hey, this is a cloud machine that is really beefy that has really good internet and you can run hundreds coding agents over there and if you're done with it, you can throw it away. You can scale it out. If you max that one out, you can keep adding machines on the cloud." Um, and we think that if you want to run 10 agents, sure, your your laptop would do, but at some point you will hit the physical limit of what a small laptop can do. um now you won't now you can run hundreds and thousands of coding agents and I think we'll get there over the next couple years you will run thousands of agents so this is an architecture that scales of course this was insanely difficult to do especially given a really short timeline we did this in weeks because all three of us are super technical and during YC where we had the pressure of launching so uh let me show you the rest of it that's a lot of rambling let me show you the rest of what makes V2 special so um of course the the core part of was working on core the app. We've also reimagined what this sidebar looks like and we'll actually do some extra work on it. But a very smooth uh like scrolling, very smooth moving things around the sections, all the things you like are still here. But we have rebuilt the file system, rebuilt how you view your changes, your committed changes, um and bring back all the stuff you love as well. Uh we've also so we don't have a pull request. Let me look at this one.
Uh, we've also made it even easier to review your changes. I can pull in like any any comments here and work at it from here. And I can also, you know, look at all the changes and you get infinite view to go down. I mean, these are all these are all not these are all PNG, so you probably want to see the actual image itself, but um, it's the full flash ID now. Um, with like syntax highlighting and all that good stuff.
Let me look at this. This is probably a little bit easier to see. And open files. Yeah. and the markdown editor, everything is still all the stuff you love is still here. And what we're able to do now is add this new thing called automations. So you can have superset run on a cron and be able to, you know, run like just a cron with a markdown and have it run at any point in time. So we have have an automation that is just checking open issues and when it runs it, it would just like open a workspace.
I already delete this um but it will just create a workspace. So you can go in and pull that workspace and see all the changes that it's made in that workspace and the session as well. And um all the other things are also back now. We have the task view that we're going to start investing a lot of time in that you can start um you start superet section sessions from your task and know like two-way sync with linear and we also have a CLI now. So let's check this one out. Hey go what does the superset CLI do?
So with the CLI which you will see let me just do a second view here super set we have fullfledged CLI that lets you do a lot of stuff now and you can manage your agents you can run automations you can check your host you can create workspaces and start stop task update all of that good stuff so you can see all the stuff it can do you can kind of get pretty crazy uh create a new workspace on my machine call it hello world me So you can of course use the CLI itself for yourself, but creating a workspace with the CLI is kind of the bigger thing that you can start enabling the agents to do. And of course the CLI will be baked into our chat. List my projects first. Um, sure. User branch name. Oh, I got to log in.
Log in there.
Authorize.
Try again.
Look at that. Okay. So, we can create the workspace through the CLI. Let's choose superset uh based on main and then submit. Okay. So, it has created a workspace called hello world v2. If we go into workspaces here, there it is. A hello world v2 workspace has been created. Uh so, let's spin up a cloud code session. Let's say hello world and look at me too in the new work space clause session launch in hello world v2.
Check it out. So we can load that in that's running. Hey hello world look at v2. So of course this is a hello world example but you can imagine the really crazy stuff you can do is like let's say hey spin up 10 agents in parallel exploring different part of the codebase. um report back to me. Yeah.
And that's it. A lot more to come. We talked about the CLI and the V2, but now that we've finished the rewrite, we can start doing really powerful stuff. Uh mobile is coming. We've had an internally working version already. Uh we want to make it like ready um and feel good. But now that we have the foundation of the client host connection, mobile had been pretty trivial to spin up. So we can start making a lot of progress now with V2 as a foundation. So excited. Uh, thank you for supporting us through this bakery ride, this journey. Um, and the early users of V2, I know you went through a lot of pain to get us here. So, appreciate y'all. And uh see you next
Related Videos
OpenHuman VS Hermes AI: Who Wins?
JulianGoldieSEO
285 views•2026-05-29
Long-Running Agents — Build an Agent That Never Forgets with Google ADK
suryakunju
142 views•2026-05-30
5 Mind Blowing Omni Uses Cases
PaulJLipsky
1K views•2026-06-02
This computer is made from real human brain cells. And you can buy it.
Talktmsmedia
3K views•2026-05-28
BREAKING: Microsoft’s New Image Generating Model Beat Out GPT 1.5 and Nano Banana 2
aimmediahouse
122 views•2026-06-03
I Made the Same Anime Fight Scene in Every AI Video Generator
NobleGooseAnime
295 views•2026-05-30
Nvidia Bets Big On AI PCs | New Chip To Power Windows Laptops | Technology | AI Updates | N18S
cnnnews18
3K views•2026-06-01
I Tested NEW Opus 4.8 on Four Projects (Updated LLM Leaderboard)
AICodingDaily
298 views•2026-05-29











