Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Using the new /worktree in Cursor 3.x (started at first upgrade, still present in 3.1.17) causes worktree creation to require approving (at least one) step(s).
Steps to Reproduce
- Open Agent sidepanel in Cursor IDE.
- Start a new agent with
/worktree do some work
Expected Behavior
Creates a worktree quickly, then starts the work there. Like Cursor 2, basically.
(I downgraded after the first upgrade due to this, and will again downgrade after creating bug reports)
Screenshots / Screen Recordings
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
For AI issues: which model did you use?
Composer 2 (but shouldn’t matter)
Does this stop you from using Cursor
Yes - Cursor is unusable
Hey there! Thanks for reporting this.
This is a known limitation with how /worktree works in the editor sidepanel right now. The slash command delegates worktree creation to the agent’s shell, which means the bash script goes through the normal sandbox approval flow. Since the script writes to ~/.cursor/worktrees/ (outside your workspace) and generates a unique worktree ID each time, it can’t be pattern-matched for your allowlist.
@deanrie addressed this in a related thread — the team is actively working on moving the worktree lifecycle to the app side (like the old Cursor 2 UI worked), which would eliminate these prompts entirely.
In the meantime, the new Agent Window already handles worktree creation natively without going through the agent shell, so if you haven’t tried it yet, that’s worth a shot — you’d get the prompt-free experience there. You can also upvote this feature request for visibility.
1 Like
I’ve tried out the new Agent Window, but this is blocking me from using it effectively: No "/apply-worktree" in new Agent Window .
I’m sure that once Cursor 3 back at feature parity with Cursor 2 in both the sidepanel and the new Agent Window, it’ll be amazing (was very much looking forward to using the new Agent Window). Until then, it’s fully incompatible with my workflow sadly, and the Agent Window doesn’t fulfill what I think is its main promise (easy multitasking).
(Cursor 3 feels like an alpha/early-adopters release that was pushed to production accidentally. Maybe something to keep in mind for the future. Luckily I’m on Linux where downgrading to v2 is easy…)
