No "/apply-worktree" in new Agent Window

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

When creating a new worktree-based-agent in the new Agent Window, there’s no way to easily apply the changes to the main repo directory.

Steps to Reproduce

  1. create New Agent in Agent Window
  2. select “New Worktree”
  3. do some work
  4. can’t apply changes to main dir…

Operating System

Linux

Version Information

Version: 3.1.17
VSCode Version: 1.105.1
Commit: fce1e9ab7844f9ea35793da01e634aa7e50bce90
Date: 2026-04-19T19:33:58.189Z
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: Linux x64 6.19.7-200.fc43.x86_64

Additional Information

My workflow with Cursor 2 was usually:
While working on a feature myself, which AI isn’t able to complete (or only assist on), I kick off multiple agents in various worktrees in the background.
When I’m ready, I apply the changes from the worktrees to my “normal” working directory 1-by-1, to test them locally.
If everything’s satisfactory, I create a new branch in GitButler and create a PR from there. This allows me to easily work with the changes from the branch on all my future work.
If it’s not satisfactory, I unapply again, and tell the AI to make relevant changes (or just discard that work).

This workflow doesn’t work at all in Cursor 3, because the new worktree implementation in the agent sidepanel just doesn’t work (see other bugreports I filed), and the one in the new Agent Window doesn’t have the ability to apply the changes to the main working directory.

I can’t easily test the changes from the worktree easily, because the project I’m working on requires a complex setup to get running, which is not easy to change.
Even if I could test the changes in the worktree, it would be a lot more hassle for me to work around this while still benefiting from the parallel branches that GitButler offers (which are a killer feature that have made me a lot more efficient overall—for my usual workday, GitButler is much more important than Cursor, because I can replace Cursor much more easily with other tools).

Does this stop you from using Cursor

Yes - Cursor is unusable

7

Hey there! Thanks for the detailed report and the workflow context.

You’re right, the Agent Window doesn’t currently have an /apply-worktree equivalent. I also realize this creates a catch-22 with the suggestion I made on your other thread, apologies for that.

The team is actively rebuilding worktree support in the Agent Window to bring it closer to the Cursor 2 experience, including native apply and lifecycle management. This is in progress right now.

In the meantime, the agent does create a git branch in the worktree, so you could manually cherry-pick or merge those changes into your main branch via the terminal. Not as seamless as the old Apply button, especially with GitButler in the mix, but it’s the closest interim option.

8

Thanks for the suggestion.

Currently, the best workaround I’ve found is to use Cursor 2 instead of Cursor 3, where it’s all very seamless.

I hope the sidepanel also gets all the worktree fixes that the new Agent Window gets, because while I’m excited to use the new Agent Window, having an agent accessible via Sidepanel is in many cases very nice (it’s much easier sometimes to write the prompt while still seeing the code that caused me to want to write the prompt in the first place).

9

Just wanted to update here: the “Bring to Local” feature is great, but unfortunately incompatible with my GitButler workflow, because it changes the active git branch.

I’ve now resorted to building a custom script (+ cursor rule) for myself, so I can actually use the new Agent Window and Cursor 3. My productivity is still definitely worse than with Cursor 2, and I’m considering downgrading again if I can’t figure out the script properly, soon.

10

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

There’s no /apply-worktree command in the agents window.

Steps to Reproduce

Start typing /apply-worktree while in a /worktree.
Observe no auto-complete or apply-worktree listing for available commands.

Expected Behavior

/apply-worktree should be listed as a command while using the agents window.

Operating System

Windows 10/11

Version Information

IDE:

Version: 3.3.17 (user setup)
VSCode Version: 1.105.1
Commit: 7802cd697cf92bf53d0b4aa590925c696eb51720
Date: 2026-05-06T21:33:12.996Z
Layout: glass
Build Type: Stable
Release Track: Nightly
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

11

if you switch to the Editor layout (Cursor Settings > General > Window Layout > Editor), /apply-worktree is available in the sidebar Composer. That gives you the cherry-pick-as-unstaged-changes behavior without switching branches, which should be compatible with your GitButler workflow.

12

Right, but:

  1. I can’t reliably find the threads created from the Agent Window there. (even if I could, the UX to switch back-and-forth is still horrible for something that used to be a single button click)
  2. I can’t work with worktrees at all in the Sidebar since v3 (see other bug reports)
13

Fair points — you’re right that threads from the Agent Window don’t carry over to the sidebar, which makes that suggestion impractical. There isn’t a good interim path that covers your GitButler workflow right now. Native apply in the Agent Window (without branch switching) is part of what the team is actively rebuilding. I don’t have a timeline, but it’s in progress.