upvote

points

by jamie_ca19 hours ago |
comments
upvoteby Charlieholtz13 hours ago|
next
[-]
Love to hear it! (Conductor founder here).

This is helpful to know - we're working on adding more agents, Copilot and OpenCode harnesses are among the most popular requests.

We also recently built an escape hatch. If you turn on Settings → Experimental → Big Terminal Mode you can create new terminals in the center panel (with ⌘⇧T) and use any agent you'd like (Copilot, OpenCode, etc). It isn't the best experience because you don't get notifications etc (yet), but at least it lets you use the harness you'd like until we build out the first-class UI for it.

Send me feedback anytime, I'm charlie@conductor.build.

reply
upvoteby edf137 hours ago|
parent|
next
[-]
Anyone know of a similar tool to conductor for Linux?
reply
upvoteby dcardamo26 minutes ago|
parent|
[-]
[dead]
reply
upvoteby Atotalnoob11 hours ago|
parent|
prev|
next
[-]
I’m interested in these types of tools, but the biggest issue I am currently having in my workflow is manually verifying everything is working. Tests and stuff are nice, but typically if there is a bug, the AI agents enshrine it in th tests.

However with worktrees I am not really able to easily copy secrets, etc to run my app, ports conflict, I end up with a bunch of separate dbs and services, etc.

Does conductor help with this? Have you all found any useful ways of making this easier or more automated?

reply
upvoteby shmoogy3 hours ago|
parent|
[-]
Conductor has a feature that lets you define a script to copy .env and other things as needed from main repo into new worktrees on creation.

I don't use it much anymore, but last I did I would run into port conflicts with docker projects.

reply
upvoteby atonse13 hours ago|
parent|
prev|
next
[-]
I was an early user of conductor and used it a lot (like from maybe oct to Jan). But then there was some bug where maybe it wouldn’t release file descriptors or something where my laptop needed to be rebooted twice a day. So I stopped using it months ago.

But I’ve tried to reinstall it since and it just gets stuck in a weird infinite loop.

I liked conductor though. Hope you are able to fix those bugs and I can try again in a few weeks.

reply
upvoteby BowBun11 hours ago|
parent|
prev|
[-]
Howdy, love your product. My coworker and I have literally been begging our coworkers to give it a try. To me, it was the key tool to 'get it' (coming from Cursor) when going from single threaded agentic dev to parallel agentic dev. Please keep up the great work.
reply
upvoteby sheremetyev1 hours ago|
prev|
next
[-]
I've built multi-agent workflow on JJ workspaces - independent from specific agent. You can run Codex, Claude or anything else - https://www.visualjj.com/learn/parallel-ai-agents
reply
upvoteby Klaster_110 hours ago|
prev|
next
[-]
In VSCode, I use https://github.com/jackiotyu/git-worktree-manager for the same purpose - the extension has before create/before destroy WT hooks which you can run anything from. Mine symlinks workspace file from main checkout, installs packages and copies over some files. Very handy.
reply
upvoteby sbysb14 hours ago|
prev|
next
[-]
You should check out Ouijit [1] - I use it regularly for work and it's nice because it focuses on the environment that you want, and just gives you a shell that you can use any tooling in, as well as VM isolation per worktree if needed.

[1]: https://github.com/ouijit/ouijit

reply
upvoteby jdkoeck14 hours ago|
prev|
next
[-]
No need for any AI-specific tool, this is exactly what devcontainer is for! Just tell your agent to use devcontainer up (and docker compose down the other way).
reply
upvoteby donmcronald14 hours ago|
parent|
[-]
Devcontainers always disappointed me. The sales pitch is that everyone uses the same container, but that's not accurate. Everyone builds a container from the same config and it'll be similar, but it takes a ton of effort to make sure it's identical.

The idea that a devcontainer gets built on-demand instead of checked out like 'docker pull ..." has always felt weird to me. It's so close to being awesome, but ends up being barely useful.

Or maybe I'm wrong. Is there a way to checkout an immutable devcontainer?

reply
upvoteby rtfeldman19 hours ago|
prev|
next
[-]
> The best at that that I've found is Conductor, but I can't use it at work because we only have Copilot and they're locked to a Claude/Codex backend.

FYI, you can use Copilot directly in Zed!

reply
upvoteby anthony-eid18 hours ago|
prev|
next
[-]
We support create git worktree hooks too
reply
upvoteby saturn_vk17 hours ago|
parent|
[-]
Is there an example of this?
reply
upvoteby jamie_ca17 hours ago|
parent|
[-]
The worktree create hook is documented https://zed.dev/docs/tasks?highlight=hook#hooks

And then I guess setting up tasks for the cleanup part, but it'd be great to see that get automated too so I don't need to remember it.

reply
upvoteby maximilianroos14 hours ago|
prev|
next
[-]
self-promotion, but check out worktrunk.dev

by far the most popular worktree manager

reply
upvoteby kippinsula14 hours ago|
prev|
next
[-]
tried parallel agents for a sprint and bounced off it. the worktree dance is fine, real blocker for us was test data isolation. scoped postgres schemas per branch worked, but reasoning about which agent broke teh shared migration when three of them touch it got old fast. we just run one agent at a time now and go for a walk.
reply
upvoteby danelliot17 hours ago|
prev|
[-]
[dead]
reply