Don't see the worktree option in Agent Window

Support Help
, ,
1

Hi this is my current Cursor version:

Version: 3.2.16
VSCode Version: 1.105.1
Commit: 3e548838cf824b70851dd3ef27d0c6aae371b3f0
Date: 2026-04-28T21:07:47.682Z
Layout: glass
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: Darwin arm64 24.5.0

Worktrees in Agent window should be possible when creating a new agent, per docs, but i dont see it, is it available??

Screenshot 2026-04-29 at 12.25.06 PM
Screenshot 2026-04-29 at 12.25.06 PM1642Ă—616 20.7 KB

4

Hi @alechko03 !

Can you double check that dev is a git directory? If you ls .git inside that directory, does anything come up?

Worktrees are only available in directories which are git repos.

5

I have the exact same problem:

image
image904Ă—307 12.7 KB

In my case, the “pruebaworktrees” folder has its perfectly valid .git folder and I’m able to use the /worktree command from the Edit window to create new working worktrees

7

Do you also have a remote configured? Please make sure you do.
Another troubleshooting step is to disconnect and reconnect Github via cursor.com/dashboard → Integrations → GitHub → connect/configure.

Normally you shouldn’t have to do this but it might help Cursor to resolve/populate the repo metadata that the Agents Window uses to decide whether to display Worktree info.

9

The remotes were actually the problem. Having a remote makes the new worktree option appear… but I wonder why does this feature require remotes at all? git worktree doesn’t seem to require does it?

Anyway, thanks for your help!

10

Awesome! Glad it worked. We are planning to resolve this so that the remote is no longer required to bring it in line with the expected git worktree behavior. But it’s a good workaround for now :smiley:

11

Ok thanks @kevinn!
Ill try the GitHub reconnection, but my repo is local not published to GitHub yet, does that matter?

How do i configure remote? and what is it?

12

Hey Alex! A “remote” is the link between your local git repo and a hosted version (on GitHub, GitLab, etc.). You can have a local repo without one — it just means nothing’s been pushed up yet.

Here’s the full flow:

  1. Create a new empty repo on GitHub (don’t initialize it with a README) and copy the URL. You can set it to Private during creation if you don’t want it publicly visible.

  2. In your project, check if a remote is already configured: git remote -v

  3. If nothing comes back, add it: git remote add origin <your-repo-url>

  4. (Optional, good practice but not required for the workaround to work) Push your code up: git push -u origin main

Once that’s done, the GitHub reconnection in Cursor should work as expected. Let me know how it goes :slight_smile: