Workspace mode and context

Discussion
1

Cursor works well when you are not using VS Code’s workspace feature. When I have a workspace open with multiple folders, however, Cursor seems to get confused.

For example, let’s say I have two folders: A React project named “my-react” and a backend project named “my-python”.

workspace
 |
 + -- my-react/ # Located at /home/myname/code/my-react
 |      + -- README.md
 |.     + -- package.json
 + -- my-python/ # located at /home/myname/code/my-python
        + -- README.md
        + -- pyproject.toml

Let’s say I ask the agent to run “ls”, which directory the agent runs ls on is poorly defined.

And if I ask the agent “what is the root directory?” Cursor’s agent appears to refer to the first folder in the workspace. I don’t think this is clearly defined either.

It’d be great to get some clarity on how to talk to Cursor’s agent/chat about workspaces.

Thanks.

2 Likes
2

same for cursor rules - they are not applied according to the workspace folder i’m editing in

edit:
also .cursorignore is not working properly

1 Like
3

From what i see Cursor is implemented as a single project. They also mentioned this in indexing and other VScode comparison posts.

Usually the first project folder is used. That doesnt mean if its a single project that only one folder is usable, I use more than that without issues. But when 2 projects are added to workspace as folders only the first one is usually used.

I myself use just single project Cursor window. SO each project has its own and no intereference or issue with what goes from where