Superset

Run an army of Claude Code, Codex, etc. on your machine

Productivity

Developer Tools

Artificial Intelligence

GitHub

@flyakiet congrats on the launch, having the ability to run multiple agents is good and bad as well from my experience as of now. Good in sense of ability to execute multiple task all at once sounds good until all task are from one project but from different project its fine. Now here's the bad part : Assuming I'm building an app which has 10 different screen so at one point if all 10 screens are totally independent (very rare) this will work but if all 10 screens are dependent then those agents splits tons of errors (can be mostly solved through a orchestrator model) but the accuracy it brings vs using single agent workflow is less until speed is top most priority over the accuracy.

Here's what I faced in details (even I used openClaw) so earlier I was trying to run multi-agentic programming but it has lot of hidden bugs and issue so I shifted back to single agent -> verify the todo (move to next todo) -> pass on to next agent -> verify the work (move to next todo) -> keep on, instead of plan -> orchestrator -> multi agent triggers.

-> And from my perspective @Superset is cursor but with multiple open project windows into single one, So I highly doubt it'll sustain itself in longer run until its solving the problem of working on multiple project all at once, which is not a problem at all.

Because multi-context scaling inside one complex project is the biggest problem is what I faced.

Here's how you can make it more usable : maximum agents breaks as the task context increases -> creates more error and takes more resource.

For example : If I created a agent to finish one work, and I keep adding more to that feature so it'll hit the context limit, but what if you can use multi agent context window and give them some % of work with related context. -> this will not get triggered in the starting of any project but only when the context is about to end. (cursor is using summary feature (context is about to end -> summaries it -> then move it to next context window -> but still its inefficient and expensive for the larger tasks).

so what if -> at starting of the project 10 agents are there (each agent has 200k context length so total avail. length = (200 * 10) 2M) but it'll not use all at once instead -> start the task with first agent -> if agent is about to hit context -> orchestrator -> see the pending work -> send it to other agents -> gets the response -> verify the work -> send it to other agents -> keep it until the task accomplished or the combined limit exceeds. (kind of I opened up a factory and hiring worker based on the needs one by one instead of assigning all at once - which creates the issue if I'm working on complex task).

and Lets say 2M is also not enough so just add more agents and follow the same pattern.

so think of it like you're having the RAM of 128GB but you're not loading it all at once which is expensive instead using it as per the need.

Best wishes @flyakiet .
Waiting for your next major update .

Been using Claude Code for PostGod, and context switching between tasks is brutal. The sandbox isolation for each agent makes sense. Does it actually prevent them from messing with each other's code?

Congrats on the product!

Would've been amazing to have this before we started building CoreSight. I'll definitely share it with a couple of friends who are still early in the process. Congrats on the product, it's super impressive!

What's next on your priority list, growth-wise?

Im a power user of conductor, curious how it compares to conductor and what is unique or different with this? Conductor is really slow for longer sessions and hangs, is superset better at long sessions?

Worktree isolation per agent is the key design choice here. Without it, parallel agents would constantly step on each other's changes. The persistent daemon surviving crashes is a nice touch too. How are you handling merge conflicts when multiple agents edit overlapping files?

Another IDE, of which there are already many. How are you better than the others?

Been using superset since the beginning and it's great for managing multiple projects!

Congrats on the launch! As someone who often uses just a single aider session at a time and calls it a day, very excited to try this out!

Been using superset consistently for the last month and my usage on it is probably > cursor right now! Insanely helpful tool if you're trying to work parallel coding sessions (multi projects, worktrees, etc.)

Running multiple coding agents in parallel without context switching is exactly where dev workflows are heading. The sandbox isolation + centralized monitoring feels like a serious productivity unlock, especially for teams experimenting with Claude, Codex, and other agents simultaneously.

The built-in diff + review layer is a smart touch too. That’s usually where agent workflows get messy.

Curious:

• How does Superset handle long-running agent memory?

• Any benchmarks on productivity gains vs. single-agent workflows?

• Is there team collaboration support on the roadmap?

This solves a real pain point. I've been running Claude Code sessions sequentially and the context switching kills momentum. The sandbox isolation per task is smart — I've definitely had agents step on each other's changes when working on related files.

Question: how does the diff viewer handle conflicts when two agents modify overlapping files? Is there a merge flow or does it flag it for manual resolution?

Great launch, congrats to the team!

Great ease working with claude code etc using SuperSet!! No more headache and waste of time!

Does this handle git worktrees automatically? Do I need to reclone all my existing repos as bare repos in order to use this?

The waiting problem with Claude Code is real, but I'm curious how Superset handles the orchestration layer. When you have dozens of agents running in parallel, how do you decide which tasks are safe to run concurrently versus which ones need to be sequenced to avoid conflicts?

And with sandbox isolation per task, does each workspace get its own file system snapshot? Wondering how state gets reconciled if two agents end up touching related parts of the same codebase.

I use Claude Code daily for building my AI platform and parallel agent workflow conflicts are something I've been thinking hard about. Would love to understand more about how Superset handles those edge cases in practice. Congrats on the launch!

Congrats on reaching #1 today, Superset team! The ability to run multiple coding agents without context switching is a game-changer for speed. As a developer building a PropTech SaaS (ParkEase) with React Native and Python, I can see how this would have saved us tons of hours during our latest sprint. Question: Does it support custom sandboxes for private Python libraries? Good luck with the launch!

Finally an IDE for people who find waiting 30 seconds for Claude Code physically painful. Now I can be unproductive in 12 parallel threads instead of one 🙏

Really love that this works with existing Pro/Max plans, that’s a huge unlock for teams already deep into AI coding workflows. Such a smart move 🙌