That message shows up when the agent tries to switch the chat’s workspace root (for example after creating a git worktree) while the chat is open in a workspace that contains several folders or repos. Cursor currently treats that switch as a multi-repo move and rejects it, which interrupts the agent’s turn. This is a known issue we’re already tracking, and I’ve added your report to it.
Two things I would suggest to try working around it:
Run the chat from a window with just the single repo you’re working in (File → Open Folder on that repo), rather than a multi-folder workspace.
Or add a rule (Cursor Settings → Rules) telling the agent not to call move_agent_to_root and to run its commands from the target folder or worktree directory instead. The worktree itself works fine without the root switch.
Could you confirm whether the chat was open in a workspace with more than one folder or repo? That helps us make sure it’s the same case.
I’m having the exact same problem. I’ve had the same setup for months without any problems. Today I updated to the latest Cursor and now I can’t get any work done because this error keeps popping up.
