What Cursor knows before your first tool call

Before making your first tool call in Cursor, the model may already know certain information about your workspace. If the name of your client or project appears in the directory path of the opened folder, that information could be included in the context provided to the model during the chat. This is separate from whether the agent can read files outside the repository.

When a chat is started, Cursor receives the absolute path of the opened folder. This path includes directory names that reveal the user account, client relationship, and possible business activity associated with that folder. It is important to note that knowing the location and directory names does not automatically grant permission to access those directories or their contents.

Before running any tools, review the workspace path and project-specific directories that may be included in the context. Check for any .cursorignore or .cursorrules files that control what information the model receives. These files can exclude certain paths or files from being indexed or used for training. However, relying solely on .cursorignore is not sufficient for maintaining confidentiality.

When sharing or storing a Cursor session, review the paths, directory names, and any client or project details that may be included. Remove or rename any sensitive information before proceeding. Keep local files and credentials in an encrypted vault separate from the repository. Regularly inspect the provider's copy of the session to ensure no confidential information has been inadvertently included.

By reviewing these details before your first tool call, you can better protect sensitive information and maintain the security of your Cursor workspace.