Live data from Hacker News

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

github.com

91–100 of 148 posts

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

#91

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

Amazing, this is exactly what I've been looking for a while now, especially the remote dev box part. I'll give it a try, thank you!

Remote dev box is brand new in the last release so let me know if it works... happy to help you set it up (I personally run w/remote dev box) shoot me an email

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

#92
post #88
post #55

Why Mac only? Also - one issue I've seen with other tools doing worktree stuff is they don't deal with merge conflicts automatically. IMO the agents should just automatically resolve conflicts & rebase on their own, is that a thing here?

Surely that's something you just instruct the model to do in your CLAUDE.md / AGENTS.md right? Not really the domain of the IDE.

If you try to just instruct them they might get it wrong. If the surrounding software forces them to do it, it'll always work. E.g. it can check for merge conflict markers like Also you'll need a wrapper to actually detect when merge conflicts will occur and when rebasing is necessary.

Generally, the less you rely on the AI the better. Make the AI write the code, sure, but don't make the AI be the process.

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

#96
post #92
post #88

Earlier quoted context omitted.

Surely that's something you just instruct the model to do in your CLAUDE.md / AGENTS.md right? Not really the domain of the IDE.

If you try to just instruct them they might get it wrong. If the surrounding software forces them to do it, it'll always work. E.g. it can check for merge conflict markers like Also you'll need a wrapper to actually detect when merge conflicts will occur and when rebasing is necessary. Generally, the less you rely on the AI the better. Make the AI write the code, sure, but don't make the AI be the process.

I think that's being pretty uncharitable to the model... I use Opus and it has zero issue handling this
Post reply on HN