No per-agent auto-worktree? This is the killer feature of Conductor, having to type `/worktree` into every new chat isn't really a resolution. Not even sure what selecting 'Worktree' for a new chat does

▲

ninininino 4 days ago | parent | next [-]

"having to type `/worktree` into every new chat isn't really a resolution"

I don't know what you're talking about. My experience with Cursor (before this new v3) is that new Cursor agent tabs / cloud agents already intelligently manage worktrees to prevent conflicts.

	▲	babelfish 4 days ago \| parent [-]
		Wow, maybe something is wrong with my setup. In Cursor 3, I am clicking "New Agent" at the top left. My root repository is correctly listed on top of the composer, and I clicked the icon to the right of it and selected 'Worktree'. Then, I instruct the model to run `pwd` and tell me it's git status. It's always just on `main` in my root repository. I dug through the settings and couldn't find anything, and after finding this comment[0] on their forums gave up. Would you mind sharing a bit more about your setup/how it works? [0] https://forum.cursor.com/t/working-with-worktrees-in-cursor/...

▲

jeffnv 4 days ago | parent | prev [-]

i would expect it before the end of the month, why not?