Top
Best
New

Posted by kenrose 20 hours ago

Conductor is joining Meta(www.conductor.build)
193 points | 205 commentspage 3
habosa 11 hours ago|
The changelog is truly hilarious:

> Conductor Cloud goes read-only on November 13 and shuts down on November 20.

3 sentences later

> Add your own completion sounds in Settings → General. Pick a sound file, name it, and choose it like any other sound.

If you're shutting down in *9 days* I really don't care that you added custom sound effects.

mattmaroon 4 hours ago||
The number of comments in here saying “founder of xyz here, if you’re looking for a replacement we make a similar product” is illustrative.
pavlov 4 hours ago|
Most people who need this product probably should just vibe code their own.

At least that's what I did.

gosen 19 hours ago||
Glad for the team, sad for the product
Raed667 16 hours ago||
I'm not a Conductor user, but the shutdown timeline seems rather rushed no?
dgritsko 16 hours ago|
That's the consensus on the Discord server, people are not happy.
wolfi1 3 hours ago||
ok, as a fan of public transfer I just asked myself, how a conductor could be useful to Meta
mgw 16 hours ago||
Congrats to the team! It's great to see acquisitions in this space.

I personally never thought Conductor was that great, so I built my own with https://podium.do.

What I was missing was a built-in task system so more complex tasks can be split up by the agents. And running agents on my own machines of course.

jahala 16 hours ago|
Site looks great, congrats - will have a peek - but I feel task handling is better done in the repo itself? (repo-as-the-harness thinking) especially for teams.
mgw 5 hours ago||
Thank you!

Interesting idea, but we find task data is too high throughput to put into git. I assume with the new crop of DVCSs that can handle much more volume this might change.

leofree 19 hours ago||
Might be a dumb question but can you explain in a couple words the benefit VS a well organized claude code CLI that knows to spin sub agents?
6thbit 18 hours ago||
I had the same question. I think this is in the space of being like the 'trillian' or 'matrix' of ai agents, using multi provider coding agent from a single interface plus some bells and whistles.

But I think within claude code and codex subagent support has improved a lot lately and it doesn't seem this would improve that much over that native support if you only use one provider.

adam-eclse 18 hours ago||
The benefit is not spinning up sub-agents, but spinning up parallel workstreams. They basically took 90% of the friction out of working with and using worktrees. I was using Linear a lot (and enjoying it!) for my issue tracking, but at some point I realized it's more productive to just create a new worktree in Conductor for any bug/feature and cut out the middleman.
leofree 17 hours ago||
hmm so working on different features let's say on the same git, in parallel, without causing issues? Is the improvement of this parallelization worth it on solo projects or it becomes only relevant on big projects with lots of PRs and such?
adam-eclse 16 hours ago||
It's always useful to have even if you don't need 8 worktrees with agents all going at the same time (I rarely have more than 2-3 active at a time). Typically there a tension between the 'fast way' (a big ol' slop branch bag of assorted changes) and the 'correct way' (carefully isolated branches and PRs) - with a smart implementation of worktrees like Conductor, the correct way becomes just as fast. That's basically the heart of good UX in my mind.
BowBun 19 hours ago||
Gah this sucks! Conductor is my main development tool. Now I'm forced to look for alternatives. Why can't they open source it?
freedomben 19 hours ago||
Over the years I've gotten extremely conservative with adopting any new tooling into my workflow, for exactly reasons like this.
jerpint 3 hours ago|||
If you’re looking for an open-source alternative, I’m the creator of woltspace [0], which is a way of coordinating your wolts (coding agents) by letting them talk to each other and giving them a lodge on your machine.

I built it for myself as a dev who loves tmux and vim and who was very unsatisfied with the typical agent orchestration experience. You should check it out! The biggest advantage is you bring your coding agents to woltspace, not the other way around.

[0] https://github.com/jerpint/woltspace

paaloeye 19 hours ago||||
With labs spending their fundings left and right and vibe-coding, it's absolutely irresponsible to adopt anything less than 18 months old.
redanddead 16 hours ago|||
Trusts suck

They ruin innovation top down and bottom up at the same time

trcf23 19 hours ago|||
Not tried it yet but DeltaDB from ZED (and ZED editor more generally) could cover it for you and they are open source.
mfe7 19 hours ago|||
I switched to paseo.sh several months ago. It's just as good if not better.
techmunky 19 hours ago|||
respectfully, its a claude wrapper. with that said if you really can't live without it-- you have the binary, you know what to do.
Philip-J-Fry 19 hours ago||
Western AI giants have hundreds of billions of dollars to make back in a world where China is releasing open source tooling and open weights models. How else does they make their money back other than finding _something_ proprietary to sell.
ayayronf 19 hours ago|
Congrats to the conductor team! The timeline to migrate off Conductor Cloud feels very aggressive. What tooling are other folks moving to?
creativeembassy 17 hours ago||
I switched to Paseo a few months ago. Fully open-source, I've had no issues with it. But no cloud provider option, so to speak. (I run an instance of Paseo in a Hetzner box, agents working full-time, haven't really had to do any maintenance on it...)

https://paseo.sh/

askedrelic 19 hours ago|||
Orca is next for me to trial https://www.onorca.dev/

Herdr has been another YC favorite https://herdr.dev/

sbarre 18 hours ago|||
FWIW I used Orca for a week and then went back to Herdr..

Orca has a lot of UI bugs, buttons that don't work, menus that don't disappear, etc.. To be fair they push updates quite regularly, but I think I will check back in once it's a bit more stable.

nwparker 16 hours ago||
Hey, if you have issues please let us know!

We test our product like crazy, so I'm quite surprised to hear this. But feel free to drop me a message, open a GH issue or otherwise.

We are OSS MIT and always open to feedback

pbjerkeseth 17 hours ago|||
If you like taking bets on smaller oss & independent projects that have no interest in creating a vc backed business, I'm working (9 months+ now) on https://ouijit.com/

gh: https://github.com/ouijit/ouijit

It's a bit unique from a design standpoint, but the next release brings it a little more in line with the zeitgeist (but not too much).

ashiban 16 hours ago|||
We're building Datadog Studio[0], for both building things, but also following them through to prod

[0] https://www.projectcodename.dev/access

mksadoughi 13 hours ago|||
For what it's worth, I'm using plain Claude Code: one git worktree per session, the sessions messaging each other directly, and one coordinator session that assigns the work. To be honest, it fills the multi-agent gap pretty well. It's not as polished as Conductor, but given how much Claude Code itself has improved over the last few months, and where it's heading, I think it's a good alternative to just stick with.
fabianlindfors 18 hours ago|||
I moved to getbb.app. Been really happy with it for the past few months. The plugin functionality is really cool.
dgritsko 19 hours ago|||
T3 Code here, I've been a hardcore user of Conductor for a while but T3 is excellent.
hoakiet98 17 hours ago||
[dead]
More comments...