Top
Best
New

Posted by avipeltz 5 hours ago

Launch HN: Superset (YC P26) – IDE for the agents era(github.com)
Hey HN, we’re Avi, Kiet, and Satya. We’re building Superset (https://github.com/superset-sh/superset), an open-source agentic IDE for running coding agents like Claude Code, Codex, OpenCode etc in parallel.

Demo: https://www.youtube.com/watch?v=YWDHn7gUwfg

Try it: https://superset.sh/

We’re three engineers who’ve built and maintained large codebases, and we kept wanting to work on more than one thing at a time. Once CLI coding agents got good enough we found ourselves running several of them in parallel: triaging Github issues, adding a few ui features, reviewing PRs, researching a refactor, etc.

The funny part was that we and a lot of our friends had all hacked together similar scripts around git worktrees. Worktrees are a nice primitive for this because each agent can get an isolated copy of the repo, but the workflows around them can feel pretty messy, setting up/tearing down environments and managing dev servers.

We first posted here a few months ago when Superset was mostly an open-source terminal for managing git worktrees (https://news.ycombinator.com/item?id=46368739). Since then, it has changed a lot based on feedback from people using it on real codebases, plus contributions from our open-source community. The product has grown into something closer to an IDE for managing agent work across many worktrees, repos, and machines.

The biggest thing we learned is that the hard part is not just “run more agents.” It is managing all the state around them: worktrees, ports, terminal sessions, environment setup, diffs, tasks, and PRs. Once you have five or ten agents running, the bottleneck often becomes remembering what each one is doing and actual human review. We added task / issue tracking so work can move from issue → agent → diff → PR → review without losing the context all in Superset. But there's a lot more work to improve this experience over time.

We also launched Remote Workspaces, currently in beta. The idea is that you can run coding agents on remote machines instead of using all the memory and CPU on your laptop, while still managing the work from the Superset desktop app.To support Remote workspaces, we isolated the core functionality of our Electron app into a headless Hono server such that it can be deployed into any workspaces and talk to any client (such as our desktop app, mobile, web, etc) and still provide the same interface that our desktop app has.

A lot of our next work is around making agent work easier to manage when you are not sitting at your main dev machine. We’re building more functionality into the Superset CLI, improving remote workspace flows, and working on Superset Mobile (coming soon) so you can check on agents, review progress, and steer work from your phone.

We’d love more feedback on Superset, especially if you are daily driving coding agents!

51 points | 65 commentspage 2
ssalka 4 hours ago|
How do you guys plan to sustain the business, given that your product here is open source & already has many competitors doing similar things?
saddlepaddle 4 hours ago||
So far we've been growing pretty healthily all things considered!

I think one thing to remember is that the other side of us having dozens of competitors is that if the space couldn't sustain more than 1-2 parallel agent companies, a lot fewer of us would exist. We also will have a lot of time to continue creating value for our customers in the future in new ways :)

hoakiet98 4 hours ago||
we monetize on teams and, in the future, cloud. the bet is that teams will want to centralize their set up for this type of work, especially shared Linear, GitHub, skills, etc.
jerrygenser 3 hours ago||
This uses separate git worktrees. If we have a local dev setup involving multiple docker services, is there a recommended solution for managing those envs? I didn't see.
saddlepaddle 3 hours ago|
We have a concept of setup and teardown scripts if you're interested in checking them out! Together with worktrees, you can make it pretty automatic to making copies of your repo: https://docs.superset.sh/setup-teardown-scripts

Ours are a bit complex but here's an example: https://github.com/superset-sh/superset/tree/main/.superset

ddxv 5 hours ago||
I'd love a comparison to what's already out there. Don't vscode, antigravity, cursor etc all have agents too?
xnx 5 hours ago|
Yes. Antigravity switched to primarily be an agent management tool (the previous version of the product became Antigravity IDE). Additionally, most advanced tools automatically spawn subagents.
hoakiet98 4 hours ago||
biggest difference is it's terminal first, and optimized for CLI agents. we don't prescribe a specific harness and instead try to work with any CLI harness you bring.
pplonski86 4 hours ago||
is it terminal on steroids some kind of? so you can manage mutiple coding agents? how many coding agents you can manage in parallel that it is still comfortable to work and code changes are meaningful
hoakiet98 4 hours ago|
yes, we surface agent states automatically so you can see what's running or needs attention across the different workspaces. there's a set of tasks where having 5-6 running in parallel is still productive for me such as running spikes and fixing small issue.

As we're investing more into integration test and self-validating for the agents we're able to increase the number without sacrificing quality.

toddmorey 5 hours ago||
I agree with the hard part being managing state, especially environments and ports. I've never used lsof so much in my life.

Question on Remote Workspace: Can the remote machine port forward so I can use a browser to see / test current state of the app on the remote machine?

saddlepaddle 4 hours ago|
On the docket! Right now the main thing we have enabled is the file system + terminals + ai agents through remote workspaces, but yes dev environments is definitely on the agenda :)
FailMore 1 hour ago||
It's nice to see people building things, but honestly I found the demo video a bit disappointing. A bit too slow, a bit too choppy, a bit hand wavy. It didn't make me grasp why I needed this in my life.
dested 1 hour ago||
Windddddddoooowwwwwssssss
brod_ie 5 hours ago||
Binding the shell <-> local git clone automatically feels like the future. Great work.
avipeltz 4 hours ago|
thanks! give it a try :) https://github.com/superset-sh/superset
desireco42 4 hours ago||
I used Superset for quite a while until a month ago. There were some annoying issues, with freezing and terminal not being rendered how it should be. And they did repeated fixes that didn't really solve it. Since I had work to do I moved on.

I installed Zellij on my server where most of work is happening and local machine and this works well for me. There are other issues I have now, but overall flow is fairly natural to what I am doing.

I liked that they did integrate a lot of agent workflow in Superset but my experience was that it would just take too many resources and especially with glitches, it wasn't worth it continuing. I had a period where i enjoyed working in it. It is vibe coded electron app, 2GB! is too much for this kind of app.

I just updated to their new version... it supposedly imported my projects but I can't find anything... so... I guess this is it.

hoakiet98 3 hours ago|
sorry to hear about the issue. we really messed up on the performance and balancing that with more features. looking into the imported projects did no projects show up on the sidebar for you?

will continue working bugs and hope you'll give it a try later in the future when the product's more stable :)

jimmydoe 4 hours ago|
zed , orca , /.+mux.*/ , ...

they all look incredibly / increasingly the same?

avipeltz 4 hours ago|
yeah i think theres a lot of ux conventions that are starting to get figured out, but we do want to be different. At least right now most dont well support remote workspace, issue tracking, or review. I bet most of the current ux patterns will look very different in a year
More comments...