/apply-worktree requires approval

[jeyj0-work]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When using /apply-worktree, I need to manually approve commands run by AI. Previously, the Apply button just instantly applied changes.

Update: often, the command run by the Agent doesn’t even actually manage to apply any changes.

Steps to Reproduce

1. create worktree using /new-worktree (real prompt here)
2. /apply-worktree

Expected Behavior

Changes are instantly applied to the main workdir.

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 (shouldn’t matter → Cursor 2 did this instantly, deterministically)

Additional Information

Going to downgrade to Cursor 2 after filing bug reports, only upgraded again to file them.

Does this stop you from using Cursor

Yes - Cursor is unusable

[mohitjain (Mohit)]

This is the same limitation covered in your other thread. The /apply-worktree slash command also routes through the agent’s shell, so it hits the same approval flow as /worktree.

I’ve responded there with the full details, and the team is actively working on moving worktree lifecycle back to the app side (native, no shell approval). Closing this one to keep discussion in one place.

One quick note: I noticed you filed several threads about related worktree issues. I’d recommend consolidating future reports into a single thread where possible, as separate threads for the same underlying issue don’t speed things up and can actually make it harder for the team to track. Your original thread is the best place to continue the conversation.