Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Launch HN: Superset (YC P26) – IDE for the agents era

github.com

Post reply on HN
Print view View original

121–130 of 148 posts

Re: Launch HN: Superset (YC P26) – IDE for the agents era

#121

Post by frenchie4111 »

hoakiet98 wrote: post #104
frenchie4111 wrote: post #60

Wow - this looks like a fork of my project https://github.com/frenchie4111/harness It's crazy to see how we have independently landed in the same place Good luck to your project! Excited to see how our projects differ in the future

looks awesome! very interesting how similar these tools all look. i do think we're at an intermediate state here with the current UI where it doesn't scale as well for the future where triggering agents and review becomes much more important than the writing code part.

Agreed - On Harness I am already working on triggering/review. Those are the two next projects on the list

We will definitely continue to iterate / try to keep up with whatever everyone thinks is the best UX

Re: Launch HN: Superset (YC P26) – IDE for the agents era

#123

Post by avipeltz »

collin128 wrote: post #67

Just switched from Conductor to Superset and I'm a big fan. I really didn't like the extra stuff conductor added to the UX (the text rendering always drove me nuts). So far so good with Superset - even as a non-engineer builder.

Glad to hear it! :) we'll keep shipping and making improvements

Re: Launch HN: Superset (YC P26) – IDE for the agents era

#124

Post by nullbio »

One thing I don't understand with all of these, is how they're handling different worktree infrastructure spin-up?

For example, if I have a webapp, I want each of the worktrees to spin up its own infrastructure, and be accessible on its own unique local url, so that I can see the changes locally for each worktree, or I can have agents automate visual checks using something like agent-browser.

Currently I use docker for my infrastructure, each service running in its own container. I have a script that has a ./app worktree create worktreename. That creates a worktree as "worktreename" and spins up all of my docker infrastructure with prefixes for things like "WORKTREENAME", and I can access all my urls at worktreename.myapp.test (or just myapp.test for the main worktree).

This is working fine for now, but it'd be cool if one of these apps was compatible with this concept so I could move over to that.

Re: Launch HN: Superset (YC P26) – IDE for the agents era

#126

Post by tsvillain »

Tooster wrote: post #62
vmsp wrote: post #51

Is anyone actually using agent swarms for anything real?

Yeah, how many agents can you people even run at once and how much does it cost you? In company we used the monthly token quota and nowadays it's basically unusable with claude opus 4.6 on high reasoning. You can basically burn through 100% usage through a single day. How does it even scale for you with N agents and which magical plans or models do you use, where tools like this are even viable?

[flagged]

Re: Launch HN: Superset (YC P26) – IDE for the agents era

#127

Post by ChicagoDave »

avipeltz wrote: post #118
ChicagoDave wrote: post #95

Still misses entirely the way software is constructed. These whack-a-mole tools are pointless.

definitely understand the perspective. I feel like theres some dev work that completely requires me to be single threaded and just think hard, but there other modes where i can jump into whack-a-mole mode and try to work on a bunch of github issues in parallel, or sentry issues, or little ui bugs and the thinking goes more into reviewing plans and prs and i dont have to be as attentive to each individual session

There are individual tasks that can be “swarmed”.

Constructing software requires supervision and a continuous feedback loop from a discerning human.

Re: Launch HN: Superset (YC P26) – IDE for the agents era

#128

Post by dbbk »

ChicagoDave wrote: post #117
dbbk wrote: post #100

Earlier quoted context omitted.

Care to elaborate

Even with the strongest guardrails, no llm can be left unsupervised. And believing an llm can supervise itself is madness. For every agent you deploy as a “team” you will have multiplied diminishing returns. I’ve iterated the process hundreds of times and even with a strong specification and tests, an llm can meet the spec and pass all the tests and still build the wrong thing. This multi-agent workflow idea is worse…

I also don't believe in this multi-agent swarm thing. I just use Claude Code "manually" and this is still useful for that.

Re: Launch HN: Superset (YC P26) – IDE for the agents era

#129

Post by whinvik »

I always feel like I want to use something like this, but then realize my NeoVim setup + tmux + Ghostty is good enough and I am not ready to learn a whole another system for modest gains.

The friction I have currently is obviously things like port forwarding, in app browser etc.

I keep thinking to try out cmux but haven't gotten around to it.

Post reply on HN