This is the same limitation covered in your other thread. The setup commands from worktrees.json also run through the agent’s shell tool, so they hit the same approval flow.
I’ve responded there with the details and workaround (the Agent Window bypasses this). Closing this one to keep discussion in one place.