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.