At first glance, it looks similar to Conductor (https://www.conductor.build/). It seems like a lot of these tools are converging on the same general ideas.
Could you share a comparison with the other tools out there?
Note that Anthropic specifically called out that usage through Conductor will be metered as "programmatic usage" in their June 15th pricing change: https://news.ycombinator.com/item?id=48126438
My colleagues are planning to get around this by using Conductor's big terminal mode. At which point I think it's basically just a git worktree manager?
yeah there is a lot of overlap, we are more terminal first than conductor so you can do can use any cli agent you want. We have a lot more quality of life features around the terminal like notifications, and some things similar to tmux where if you kill the app or update your sessions stay alive and running. We also recently released remote workspaces so you can setup cloud workspaces for your agents. Id say if you like the chat experience conductor is still a bit more polished, we'll get to that level of polish soon, but if you care more about the terminal and cloud and more new integrations we are shipping superset is better.
Very excited about the remote workspaces! Perfect for me as I've set up a remote Mac as a Claude terminal. I know it's only just released but the typing is quite laggy... have you considered something like mosh? I've been using this from the terminal and it makes it feel as fast as running locally.
I've been using this for the past few months, and I love it! It's built exactly around my workflow with many worktrees in various repos open at the same time, sometimes with different agents working side-by-side. Before Superset I just used terminal tabs but simply couldn't manage more than like 20 terminal tabs without losing track, so i coudn't scale further. Now i'm running probably 40-50 agent sessions over several repos simultaneously without any issues and losing track!
Keep up the good work guys!
Could you elaborate a little on what you are doing with 40-50 agents? I use Claude, I've employed sub-agents, but I still can't wrap my head around how people are using them to that extent.
ha, I didn't mean they are all running at the same time. sorry if it sounded like this.
I open a new worktree/agent session for each new feature or bugfix. Usually I start with ideation and brainstorming before doing the actual implementation. However my priorities shift daily, so I could be starting a feature on monday, but then stop during the ideation already, pick up another task on tuesday and won't go back to the initial one until a week or a month later. Since I got it in a neat worktree in superset, I still see my open branches easily, have access to its claude code session and can resume the work much easier than before having terminal tabs.
Because of this setup I currently have 17 backend sessions, 25 frontend sessions, plus several other repos open and ready, when i need to.
one issue i'm having, maybe you know what's causing this, in long running terminal sessions I'm getting rendering issues. Like some characters show as something else. I have to resize the window to fix it, usually opening and closing the code sidebar fixes it for some time, but it never fully goes away.
I think i also have it more on the big screen (4k) than on the laptop screen.
And headless server support! I have gotten a lot of request to let people run the agent on a separate dev box (in the cloud or some pc gathering dust in the corner). The frontend/backend are decoupled so you can run the agents on a totally separate machine than the GUI is running.
If you have any other problems/concerns/issues/suggestions/etc, reach out!
Nice. In the right track. I made something similar, but focused on local agents, but we both have issue tracking for managing multiple project and agents in parallel. It works, I think people will be surprised when they start using systems like this.
It is very different from current editors and the direction they are going in. In a way, it undermines the direction they are going. Current editors aim to make engineers 10x or 100x. These editors aim at a different target than the engineers. I will leave it to the imagination on who.
Sorry if I'm missing something but is there a way to create a new Claude workspace that has dangerously-skip-permissions but starts in Plan mode? There's no mode selector in the new workspace modal
Yeah I have --dangerously-skip-permissions configured as a preset for Claude in Superset, but you can add more commands too. Just go to Settings > Terminal
That overrides plan mode though, eg it seems claude --dangerously-skip-permissions and --permission-mode plan can't be used together. So I can't kick off a workspace from Superset with a prompt that starts in Plan mode but can switch to dangerous
That still is not it for me, for now iTerm2 tabs / tmux is plenty. This, or tools like Warp, feel so heavy for me and I get overwhelmed.
The Codex/Antigravity desktop app alternate route feels more like the direction I can buy into it, but I still feel like there's room for another novel UX not yet done.
Perhaps the biggest thing I feel like I wish existed is a "Scratchpad" mode inside a session, Claude recently came up with `/btw` and it's been really useful. Same with `!` for terminal commands within session.
Nested thinking spaces within a chat window UX is a very tricky thing to reason about.
Sadly there are so few solutions, if even one, that is trying to offer a real remote agent interaction.
That's why I've build my own. No IDE per se rather than a discord bridge, with all interaction possibilities that makes sense and a way for my agent to quickly send me files or host mockups. My usecase is to build tools, reports, do research, mock up ideas and build prototypes. That's why I don't need to see the code that was written.
I was looking exactly for something like that. I tried installing the Linux version and it runs but:
1. it's behind a login wall | 2. tries to download its own OpenCode instead of using the one installed on my machine
I also tried to create a new workspace. It asked what I want to do. I tried with "create user accounts", and it proceeded to create the git worktree (without asking for its name) and sent that prompt straight to OpenCode without allowing me to choose the LLM model.
I plaud the effort - I really do - but it doesn't really seems a great experience for now.
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.
Kitty with oh-my-zsh, lazyvim and an agent. The entire thing is an ide. If I need to refactor, query data and interact with the system I just use native tools like rg+fastmod, bash, awk, jq... Either writing myself of asking an agent to do the heavy lifting.
Linux in the agent era is a breeze to operate and reason about, so the whole thing becomes a single development environment that's really light on resources and effective.
What I've started to do is to use Zulip. You can have different agents in different chats. You can upload files and you update from your mobile phone. At first I thought it was crazy but it's nice not to have 3 different AI agents running in tmux
That's an interesting take! Basically Linux / a computer is everything you need to ship code.
If I could provide one gentle pushback - the same way there's utility in OMZ, lazyvim etc., there may be utility in us shipping our CLI etc. - there must exist some software we can build that'll be useful to you as well :)
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?
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?
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 :)
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.
I switched over to Superset from Conductor a few months ago and haven't looked back - it's really nice to be able to use the native Codex/Claude Code TUIs without any of the bloat
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.
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.
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 :)
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.
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
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
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.
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.
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 :)
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.
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
That's fair! We do have more paid features (a slack integration, remote workspaces etc.) but yeah we haven't found the best balance for which tier to put each in for sure.
The FAQ says "Superset has a free tier. The source code is available on GitHub under Elastic License 2.0 (ELv2), so you can inspect and self-host it subject to the license terms." - what is self hosting in this context, isn't it a desktop app? Is this why it wants me to sign into something? What exactly am I signing in to?
So we also ship a cloud service along with Superset, which enables our Linear integration, Slack integration, and our multiplayer capabilities / remote workspaces.
When you sign in, you're signing into our cloud service!
Actually Cursor is starting to converge with us as we speak! You can look at their new agents mode (which is now their default for new users) as an example.
For what happens, in our heads the end goal is building a software factory where dozens to hundreds of agents are always running - something that nobody has nailed the experience for yet. Until that's a solved problem I hope we have room to grow and build!
yes, bad choice on my part. the origin was i was planning for it to be a superset of all your dev tools, not thinking about apache superset at all since it was a different domain
Fair pushback! The space will settle down eventually, it's just clear to a lot of people that there's a lot of value to be created in this space that hasn't been created yet :)
"Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting."
Could you share a comparison with the other tools out there?
GUIs slow you down, in my opinion. But having the nice visual diff is something we can't really do well in TUIs, so very welcome.
So, superset, for me (been using for quite some time now) is basically to organize my agent and terminal sessions per task and project.
I can switch context much easier and can also resume working on something days later, with all my tabs nicely available and separated.
This was consuming me before, a dozen or more tabs and windows in my computer that I don't really remember to which task each belongs to.
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
If you have any other problems/concerns/issues/suggestions/etc, reach out!
It is very different from current editors and the direction they are going in. In a way, it undermines the direction they are going. Current editors aim to make engineers 10x or 100x. These editors aim at a different target than the engineers. I will leave it to the imagination on who.
The Codex/Antigravity desktop app alternate route feels more like the direction I can buy into it, but I still feel like there's room for another novel UX not yet done.
Perhaps the biggest thing I feel like I wish existed is a "Scratchpad" mode inside a session, Claude recently came up with `/btw` and it's been really useful. Same with `!` for terminal commands within session.
Nested thinking spaces within a chat window UX is a very tricky thing to reason about.
1. it's behind a login wall | 2. tries to download its own OpenCode instead of using the one installed on my machine
I also tried to create a new workspace. It asked what I want to do. I tried with "create user accounts", and it proceeded to create the git worktree (without asking for its name) and sent that prompt straight to OpenCode without allowing me to choose the LLM model.
I plaud the effort - I really do - but it doesn't really seems a great experience for now.
So far so good with Superset - even as a non-engineer builder.
Kitty with oh-my-zsh, lazyvim and an agent. The entire thing is an ide. If I need to refactor, query data and interact with the system I just use native tools like rg+fastmod, bash, awk, jq... Either writing myself of asking an agent to do the heavy lifting.
Linux in the agent era is a breeze to operate and reason about, so the whole thing becomes a single development environment that's really light on resources and effective.
If I could provide one gentle pushback - the same way there's utility in OMZ, lazyvim etc., there may be utility in us shipping our CLI etc. - there must exist some software we can build that'll be useful to you as well :)
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?
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 :)
Can't wait to see what else you guys cook up!
Definitely some exciting stuff coming with better automations, mobile and remote workspaces
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?
Ours are a bit complex but here's an example: https://github.com/superset-sh/superset/tree/main/.superset
As we're investing more into integration test and self-validating for the agents we're able to increase the number without sacrificing quality.
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.
will continue working bugs and hope you'll give it a try later in the future when the product's more stable :)
they all look incredibly / increasingly the same?
When you sign in, you're signing into our cloud service!
What happens if Cursor makes the exact same features as your product?
For what happens, in our heads the end goal is building a software factory where dozens to hundreds of agents are always running - something that nobody has nailed the experience for yet. Until that's a solved problem I hope we have room to grow and build!
https://superset.apache.org/
https://github.com/apache/superset
https://news.ycombinator.com/newsguidelines.html