Hacker News new | ask | show | jobs
by ninininino 83 days ago
"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.
1 comments
babelfish 83 days ago
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/...

link
ninininino 76 days ago
Wow, it seems I'm the fool here.

I'm on Version: 2.6.19.

Per https://cursor.com/docs/configuration/worktrees#how-is-this-...

They apparently removed this in 3.0. - I couldn't begin to guess why.

"Automatic management of worktrees was removed in Cursor 3.0 and replaced with the new commands /worktree and /best-of-n. We also have added worktree support for the Cursor CLI.

Management of worktrees is now fully agentic. This makes it simpler to support use cases such as starting an agent, and only doing work in a worktree later on in the chat's lifecycle.

/best-of-n makes comparing the results of multiple models much easier. The parent agent will provide commentary on the different results and you can pick the best one. Additionally, you can even ask the parent agent to merge different parts of the different implementations into a single commit.

If you had agents that were previously running in a worktree, those chats will still work. However, you will need to use the new commands to start new agents in worktrees."

link