Hi, there is a new bug: if you select a workspace for cursor agent and start working, sometimes it switches to another workspace randomly.
In this case you need to stop working and restart in the correct workspace, rly annoying.
Hey, thanks for the report. This looks like something we’re already tracking, but I want to make sure I understand which exact case you’re seeing so I can route it to the right place.
A couple questions:
Does the wrong workspace show up right when the agent starts, like after New Agent or Split, or does it switch in the middle of a run while the agent is doing something?
Do you usually have multiple projects or agents open at the same time?
Are you launching these agents from the desktop Agents window, or somewhere else like web or Slack?
A screenshot right after it happens would help a lot, and also the Request ID from the broken session right corner of the chat > Copy Request ID. I can already see the version 3.17.8 on Windows, thanks.
Once you’ve got that, send it here and I’ll take a look.
Thanks for the video and the extra info. What you’re describing, the workspace switching when the agent starts or while you’re typing a prompt, especially when multiple projects are open and you’re using combined workspaces with multiple repos, is an issue we’re already tracking in the multi-root scenario. I shared your case with the team along with the details.
This shouldn’t happen, and it’s not something in your setup. I can’t share an exact timeline yet, but I’ll post here when there’s an update.
same problem. Opened the agent, opposite the desired project. Made changes, but it turned out that a completely different project was active and the changes flew to the prod server, disrupting its operation.
Similar problem here, but it happens also when i click on an existing chat in the agents window.
Project A
Chat A1
Chat A2
Project B
Chat B1
Chat B2
If i now click e.g. on Chat B1 to add something there or look at the results of an agent, it randomly jumps to e.g. Chat A1. If i then click again on B1 it usually stays there.
I only saw it for now with WSL mounted workspaces ~/projects and i think i saw some message like “Connecting WSL” before it switched for a split-second, so it could be related to a lost connection to the workspace and therefore switching to another one.
It does not prevent working with Cursor, but for sure is highly annoying.
Hey, thanks everyone for the extra details. For the main case where the workspace switches when creating an agent or while typing a prompt when multiple projects are open, including a combined multi-root, that’s something we’re already tracking. It shouldn’t happen, and it’s not caused by anything in your settings. I can’t share an exact timeline yet, but I’ll post here when there’s an update.
@astheras: edits being applied to the wrong project sounds especially bad. Until this is fixed, I’d recommend keeping active commits in git and double checking which workspace is actually selected before you run or apply changes. That should help prevent edits from landing in the wrong place.
@Karsten_Beyer: your case looks a bit different. It switches when you click an existing chat, and only on WSL-mounted workspaces, with the “Connecting WSL” step right before the jump. To keep this separate from the main case and track it on its own, please start a separate thread and include:
the Request ID from the session (top right of the chat > Copy Request ID)
your Cursor version and short repro steps
if you can, a short screen recording showing the switch happening
That’ll make it easier for the team to dig into the WSL side of the issue.
I have the same problem. I use AI agents view/windows only in the Cursor Windows app.
The last couple of days, quite often when I press the “+” sign in the left side workspace/projects pane to start a new session/chat something strange happens, and that chat gets like a new dupilcated folder in the left side pane, and also that the agent is spawned from another workspace. This is a critcal bug and could cause major havoc!
For me it’s not intermittent: it reproduces every time I open a New Chat. I pick a repository in the repo picker, and a few seconds later it switches back to a different (recently used) repository on its own, taking the branch and machine selection with it. Example: I selected my home directory (~), and while typing the prompt it switched to another project I’d worked in previously.
It also happens via the per-project “+” button in the sidebar — the new chat opens with a different project selected.
Hey @Thomas_Axelsson, thanks. Your screenshot shows the core issue well: the chat was opened from C:\Dev\domainforge, but the environment snapshot passed to the agent was C:\Dev\workforge with git status showing Workforge files, and then the workspace switched mid-session to domainforge. Also, in your previous screenshot you can see a duplicated folder in the sidebar when you click +. This is the workspace desync in a multi-project setup that we’re tracking. It shouldn’t happen, and it’s not something in your setup.
On the risk you mentioned could cause major havoc, I agree. The worst part is that changes could land in the wrong project. Until this is fixed, I’d recommend:
Keep your work under git with regular commits so it’s easy to roll back if a change goes to the wrong place.
Before starting the agent or applying changes, double-check which workspace is actually selected in the session.
I can’t share an exact timeline yet, but I’ll reply in the thread when there’s an update.
Hey @boke0, thanks for the macOS data point, it’s really helpful. Most reports here are from Windows, and yours also reproduces every time on New Chat, which is more valuable to the team than intermittent cases. The fact that the picker flips back to a recent repo after a couple seconds and pulls the branch along with the machine selection and the same happens via the sidebar + is the same workspace desync we’re tracking. That shouldn’t happen.
Since you have a stable repro, could you share a short screen recording that shows the selected repo switching by itself? And if it’s available, the Request ID from that session right top corner of the chat > Copy Request ID. That would help the team a lot.
I can’t share a timeline yet, but I’ll reply in the thread when there’s an update.
