Soon we're going to need a meta-orchestrator for all these agent orchestrators

Did you build this out of pure interest in what's available or to be able to chime on threads like these on Reddit and HN when someone builds the same thing once again?

Nice, would https://vibepod.dev/ also be a fit for the list?

Nice site and I'm surprised (also not surprised) by how many there are. A few missing that you might consider adding:

- paperclip

- multica

- perplexity computer

This is nice and handy, thank you. Do you plan to add filters?

well done! but "compare" is a bit of a stretch... maybe you can get an inspiration from models.dev ?

reminds me days of coinmarketcap

openrig also seems to fit

hey, thanks

we are somewhat already heading in this direction to handle complex workflows like yours

And https://openrig.dev/

Add these to the list:

[3] https://orchestrator.inc/

[4] https://gitkraken.com/kepler

[5] https://emdash.com/

[6] https://superset.sh/

[7] https://www.conductor.build/

[8] https://nimbalyst.com/

[9] https://parallelcode.app/

[10] https://www.jetbrains.com/air/

There's also sometimes options that try to have a tighter integration with a single harness, which honestly seems to be better cause ACP is fairly bare:

[11] https://openchamber.dev/

Personally, I found Paseo to be very pleasant, except sometimes I had sub-agents kinda hang.

Kepler had a really nice issue tracking integration (GitLab/GitHub Issues, Trello, Linear, Jira) but their UI felt like vibe coded slop, like the core experience doesn't feel very good, but they keep adding shit that nobody needs like a graph visualization of what the agents are doing, instead of letting me drag the tasks around the Kanban board myself or tell the agents how to do that and how to transition the issue statuses. Hopefully it's gonna get better within a few years, still early on in development. Still, the idea of an issue tracker integration is brilliant and all harnesses should consider supporting that, e.g. pick which tickets you want to work on, they automatically create worktrees and agents do the planning/research step, presenting you with plans like /grill-me so you can decide what to work on, alongside having a step for merging all of those worktrees whenever you want when a wave of work is done.

I haven't tried most of them tbh cause my OS install doesn't need to be even more of a dumpster, but I'm surprised at how none of these really seem all that... rock solid?

Like if I open a JetBrains IDE like IntelliJ IDEA / Rider I know that despite the crappy resource usage and whatnot, they have the needs of writing, refactoring, debugging and building code covered. Most of the current harnesses seem to get some baseline of telling agents what to do, but still somehow end up being buggy (e.g. can't peek into OpenCode sub-agents and give THEM instructions last I checked, or pause or alter the prompt, despite Claude Code allowing message exchanges with sub-agents and such), and many others are just clones of what already exists.

At the same time the desktop / web apps shipped with harnesses like OpenCode (if there's one at all) are very clearly insufficient and a step below Claude Code Desktop and Codex (ChatGPT app) in usability (like that move to horizontal tabs like browsers have, come on how am I supposed to navigate when there's like 30 of those? or what about an auto mode switch within the UI), so obviously we do need something as an ADE.

Personally I wonder if half of these projects will die off in like 5 years, or whether they'll get more polish or differentiate themselves more, and which will try to push more for cloud-only stuff, like how RooCode essentially dumped their VSC plugins and went all in on the cloud.

The fundamental difference is in the design philosophy - other meta harnesses focus on agent-in-the-loop, and we focus on the other half, i.e human-in-the-loop. We will be feature-complete in the next 2 months - launching the cloud and offrun mobile app soon.

Why not keep building yours? It will quite literally be the same or better than 99% of these tools.

I also don't care much about individual conversations with agents as the main way of managing work, my personal dashboard shows projects (and subdivided by work trees underneath) but I have an orchestrator agent who is the one I talk to 90% of the time and who is responsible for summarizing information from various project manager agents and only update tiles in the dashboard when I actually need to do something, in the form of questions I can answer directly.

Over time as I add more preferences for how to work, the orchestrator sends fewer and fewer requests to me that it can handle itself.

thats a great point - we will keep that in mind while building offrun.dev

I totally keep my agents away from git writes.

I tried a few of those and they are shiny but each eventually has their own bugs and quirks and limitations and I always felt like I was trying too much of my active workflow into a tool that could crash and lose all me sessions.

Whenever I need to change or fix ccwt I just spawn an agent with a fix and then I merge and rebuild the tool and it automatically autoupdates and restarts in the herdr tabs. This way I don't have to replace the "outer shell" of my agents for every change I make. Only when herdr itself gets reinstalled (often herdr can reattach to the same sessions but sometimes you just need to stop everything and restart all the agents. Losing progress notification state in the process)

I found a more modular approach that works for me:

1. Herdr terminal multiplexer 2. My custom orchestrator, which I grew out organically based on what I actually need and I feel I can easily change. It started like a minimal reimplementation of wt (worktrunk) but grew out into an integrated constellation of TUIs that leverage herdr API to drive herdr and help me navigate in herdr

Just sharing as an example of the pattern. It's not meant to be an useable tool by anybody else I think.

https://github.com/mkmik/acmik

great point! we have released only for Mac for now (both silicon and Intel) and will be launching Windows and Linux versions soon.

We are going to integrate Herdr, Pi, Opencode and provision to add custom harness soon - already working in that direction.

Yes, one can always build this on their own. We are just building based on our observations on what is missing while using claude, codex, Pi, Opencode etc.

You are right. You can build your own, or you can pick one you like and tweak it as you please.

I think different products cover different needs. I think there's lots of options nowadays and I'm most of the options shine one way or the other, it just depends on the mental model of the user and their goal.

I started my own tool less than amonth ago [1]. I did my first Show HN a week after, I was really proud, I added lots of features that first week just to accomodate my own needs and I was not even focused on this project but I could already see how it really helped me remove a lot of fatigue on managing multiple projects and be capable of manage them all at my own pace. My tool, in particular, was created with a focus on iterating over projects, not agents, and in the human (you) having full control on what you do. Anyway, the thing is that the very same day I posted the Show HN, there was this other project that was also submitted some hours before [3]. This project had more traction and comments already and was the one that appeared on the first page of HN. I haven't tried it, but I'm sure it would be great as well.

Yesterday I had a call with another dev at my organization, and he was also doing his own thing (unaware of the one I did, and unaware of other options available already) and I could already see the overlap with different tools and I even pointed out other projects for him to gather for ideas. I think is fantastic that so many people are exploring this space.

The reality I'm observing, with the latest state-of-the-art models, is that they are amazingly capable models and that less and less I need to even review what they produce. I trust on them more and more. This has deep implications moving forward.

I think we'll see two trends moving forward:

- Devs will build their own tools their own way (not all, but some will)

- Devs will clone an open-source project, and then, instead of forking and pusing upstream, they will just adjust to their own needs and detour from the original project more often than before

Sure enough, some people will just take the convenience of a ready-made project, and not even bother to iterate over your own thing, but when you are one prompt away from fixing this big issue or this subtle detail that annoys you, you don't need a config param anymore, and you don't need to wait days or weeks for somebody to fix, if you can compile the project in your machine, you can just create your own version of the software that works the way you want. You are just one prompt (or 10 or 50) of creating or adjusting to your own preferences.

Industry-wise I think this feels sometimes scary, but I think it is amazing.

[1] https://github.com/pausan/agenttik

[2] My Show HN 2 weeks ago: https://news.ycombinator.com/item?id=49720222

[3] Another, more successful, Show HN same day as mine: https://news.ycombinator.com/item?id=49713894

edit: formatting issues and minor tweaks on wording

The whole point of Offrun is that we want the users to stay in a flow state. Users will never be stuck because of session/account limits because they can simply switch to any other account in 1-click and resume the work seamlessly.

I read somewhere that a common thing in text written by LLMs is, in their sentences, putting inanimate objects in the active position.

Because every bit of this webpage was written by Claude.

because it was written by an LLM - using the direction given by a fellow human :)

thats the future we are heading to, right?

It occupies the same space in my brain as the clickbait-type "This is the key" and "what you're missing" LLM-isms

haha really appreciate your comment - I have taken your feedback and will definitely add the thought process to our roadmap.

haha thanks for the positive comment - we are working on the right design to get users! Our early users are appreciating the intuitive design of the tool - our focus is to manage multiple coding agents without getting human attention in the way.

Herdr lets you run agents anywhere, and Offrun helps you to manage the agents. We are going to launch Herdr integration inside Offrun soon.

I don’t really get Herdr it’s terminal with integrated tmux ?