Cursor 3 agent ui does not allow me to use branches on WSL repo

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I try to select a branch or create a new one / or a worktree while in Cursor 3, and there is no option. It appears to not list any branches available.

Steps to Reproduce

Use cursor on windows with a repository under WSL, then add the WSL repository as a workspace in cursor, and try and start a new chat that is on another branch of worktree.

Expected Behavior

For it to work properly.

Operating System

Windows 10/11

Version Information

Version: 3.3.30 (system setup)
VSCode Version: 1.105.1
Commit: 3dc559280adc5f931ade8e25c7b85393842acf30
Date: 2026-05-09T18:28:42.332Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

Thanks for reporting this, and sorry for the friction here. We’ve raised a bug report for the WSL branch/worktree picker issue in the Cursor 3 Agent UI, and we’ll follow up here once we have a fix or more concrete update. As a temporary workaround, you can switch or create the branch manually from your WSL terminal with git switch / git checkout, then start the agent from that workspace state.

Yeah I also don’t have that new worktree thing either (dropdown to the right of the branch one), but I could have sworn it did work at one point when I was trying out Cursor 3.

It DOES work for a repo thats on windows, but not for anything within WSL. I assume both of these being missing is related (can’t have a worktree if git isn’t working).

It’s for sure some sort of issue with the application/wsl integration though. The actual agent/harness stuff works fine, if you tell it to make a worktree it can, etc.

I also repeatedly see “setting up WSL” pop up. I’ve tried wiping cursor-server folder in WSL, didn’t help.

Editor window w/ WSL works mostly fine, sometimes get issues with failing to save files in worktrees (not actually though, its just some application state issue), but thats been a thing for months.

Any update on this git + wsl issue?

We have eyes on it and it’s getting looked by the engineers on the correct teams! however, I don’t have an estimate. We’ll let you know any updates.