Agent changed workspace before executing /review-bugbot

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Bugbot / Security Review Agent

Describe the Bug

Hello, not sure if this is the correct place to report this.
I had an agent switch workspaces while being instructed to do /bugbot-review. When asked WHY they changed workspace, the agent said:

"over-read the Bugbot skill.
The skill says the review path should be “the active workspace or repository root.” I treated that as “make that repo the agent workspace via move_agent_to_root,” then launched Bugbot. “”

The relevant excerpt in the skill is
“The repository path should be the active workspace or repository root for the code the user wants reviewed.”

Steps to Reproduce

Context:
Large workspace with close to 100 repositories, with varying types infra/microservice/package

Not sure how it could be reproduced. I just asked the agent to do /bugbot-review and they changed the workspace. I have no rules instructing them to change workspaces.

Expected Behavior

The agent does not change workspace when not told to

Operating System

Windows 10/11

Version Information

Version: 3.12.10 (user setup)
VS Code Extension API: 1.128.0
Commit: 24a12dbd9cabf48956ce5bb3dbd234e41385b3d0
Date: 2026-07-16T03:15:48.538Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Auto

For AI issues: add Request ID with privacy disabled

95ca6c61-0e28-42a8-8705-a5e98f68c6e1

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey @tsaniprodanov!

Thanks for the report. We do have an open item in our backlog to require approval for move_agent_to_root.

That said, I’d like to understand the context a little more here! Were you trying to run /review-bugbot in a single folder of a large workspace, or were you working in a multi-root workspace?

7

Hey @Colin !

Thanks for the quick response. It is a single-folder, monolithic workspace - no multi root. All repos are flat checked out in a subfolder relative to root, i.e. root has /.cursor, and then /{repo-1}/.git , /{repo-2}/.git, etc.

My first prompt (and the one that caused the agent to switch root) was exactly: “run /review-bugbot on the local messaging changes”.

I believe two out of the many repos had changes at that point - the agent correctly executed the review on the correct repository - they just did not need to switch the root.

9

Thanks! That does seem wonky. I’ve shared it with the team.