Worktrees are temporarily unavailable right now. The team is aware and actively tracking this.
I understand this is frustrating, especially since the worktrees docs page describes the feature. We don’t have an ETA for re-enabling it yet, but it’s being actively worked on.
In the meantime, Cloud mode supports running prompts across multiple models and doesn’t require worktrees, so it can serve as an alternative for parallel execution.
I removed the Glass early access option from Cursor settings to restore worktree support. After doing so, Cursor downgraded to the previous version. After Cursor restarted my entire agent chat history is GONE across all projects. How can I restore it?
Hi there! The worktree experience has been updated on recent builds. Instead of the dropdown option, you can now use the /worktree command directly in the agent chat - just type /worktree followed by your prompt, and the agent will create and work in a worktree for you.
There’s also /best-of-n if you want to compare results from multiple models in parallel.
The docs haven’t been updated yet to reflect this change (which is still only on nightly builds). Let us know if you have any questions or run into any issues with the new flow!
Also ideally for QOL in glass if I am in a worktree I would hope the scm pane on the right could pick this up and detect the chat we are on is on this worktree so show the branch/changes that is on
it always assumes youre in the main worktree root, but if you use worktrees to work on three different features, each their own chat for the same repo you’d ideally like to see the changes unique to the chat you are on’s worktree and branch
Updating my earlier reply – as @Colin explained above, the worktree experience has been updated on recent nightly builds. The old dropdown selector has been replaced with slash commands in the editor agent chat:
/worktree [branch=<name>] <task> – creates a worktree and runs the agent in it
/apply-worktree – merges worktree changes back into your main working tree
/delete-worktree – removes a worktree
/best-of-n <model1,model2,...> <task> – runs the same prompt across multiple models in parallel
These are available in the editor only for now. Glass support is still being worked on.
Cloud mode also remains an option for parallel execution without worktrees.
@philkuz - you’re on a recent enough nightly build to have these. Give /worktree a try in the editor and let us know how it goes.
@blummis - your lost chat history after removing Glass early access sounds like a separate issue. I’d recommend filing a new thread so the team can look into recovery options for you.
I initialize a new agent task in a worktree, but the task begins locally instead.
Steps to Reproduce
New Agent
Choose “Worktree”
Submit prompt
It’s not in a worktree
Expected Behavior
It should be in a worktree.
Is worktree creation now up to agents? This is a problem because:
That’s not what the UI implies.
Now all benign terminal commands require approval instead of auto-running.
Apparently, one of my agents failed to create a work tree, or moved changes to main without asking, I didn’t realize it AND I PERMANENTLY DELETED UNTRACKED FILES IN THE DIFF VIEW, THINKING THEY WERE MISTAKENLY COPIED TO THE WORKTREE. But in fact, it was not the worktree because I guess the agent didn’t create a worktree like asked?! Those untracked files are now gone.
I have so far found Cursor 3 to be a major usability AND FILE INTEGRITY regression.
The dropdown under the Agent chat window shows “Local” but the option for “Worktree” and “Cloud” are both greyed out. No way to fix it. Even ran it on a fresh GitHub repo. Reverting to 2.6 fixed it.
Steps to Reproduce
Run Cursor 3 on Ubuntu 22.04 using cursor . in a Git repo. Go to the dropdown under the agent window that defaults to “Local”
Expected Behavior
Worktrees and cloud should be an option. And multiple agents should also work.
worktrees ergonomics was not the best in previous version, but since 3 I think it just degraded even further. Why can’t I just create a worktree, do stuff there and merge it back to the original branch? I would literally like to see this flow, I’m doing it manually now and it’s pain since I have to switch editor windows
