The “Include project structure” feature currently does not respect the rules defined in the .cursorignore file. As a result, directories like .venv, __pycache__, and other ignored paths are included in the generated project structure view. This can make the structure overly verbose and difficult to navigate, especially in projects with large virtual environments or many cached files.
Ideally, the feature should parse .cursorignore and exclude any files or directories listed there from the project structure output, similar to how .gitignore works for Git operations.
+1 to this. Atm the feature basically fills the context window with thousands of tokens of irrelevant file paths, which isn’t great for model performance (and cost).
Though it seems to be selective, at least for me. E.g., my node_modules/ paths seem to be correctly ignored in the project structure while my .venv/ and .next/ paths are included.
Separately, assuming the above gets fixed soon, one request I have for this feature would be either 1) the ability to control its level of nesting, and/or 2) having deeper levels of nesting in the tree get automatically added to context as the agent reads files in deeper parts of the project. Though not a huge deal since this can be done manually via .cursor/rules and glob patterns