Why does Cursor not show the file path every time it creates a new file for me?

[ssdesign]

Whenever cursor proposes to create a new file, it generates the file name, but it does not tell me where in the code should I place or if I need to create a new folder inside some other folder etc.

eg.
While creating a React app, it said Let’s create AddTeamMemberDialog.js and then gave me some code. In the code block the file name was AddTeamMemberDialog.js

Since my code base had lots of folders and sub folders, I had to ask, where should I place this file? and then it replied:

src/components/team/AddTeamMemberDialog.js

The full path structure would look like this:
src/
├── components/
│ ├── navigation/
│ │ └── LeftNavigation.js
│ └── team/
│ └── AddTeamMemberDialog.js
├── config/
│ └── firebase.js
└── …

Do I have to always spend a rquest to clarify such small things? or is there a way to tell Cursor to always show full file paths whenever it is making suggestions?

Just curious how you conserve your requests

[deanrie]

Hey, you can set this in the rules if you’re not using it yet. You can include something like: always specify where I need to place the file. The wording can be different, but I think you get the idea. I hope this helps you.

[ssdesign]

Thanks for the tip. Sometime its working, but its not consistent.

[SoMaCoSF]

Yeah set it in rules, but also in a project instructions.rmd file and keep refering to it in context. Check my post history for some examples - and I can feed you some gists if you want for what I have bnen wokring on to force certain behavior of the Composer Agents

Document	Description	Link
Agentic Workflow System	Comprehensive guide to multi-agent workflow orchestration and documentation database as Source of Truth	View
Development Standards	Core principles, file structure, and coding standards for Cursor IDE development	View
Environment Configuration	Template and guidelines for project environment setup	View
Project Structure	Standard project layout and directory organization	View
Database Documentation	Database schema, migration, and maintenance standards	View

Key Features:

• Complete documentation system for Cursor IDE development
• Multi-agent workflow orchestration framework
• Centralized documentation database as Source of Truth
• Standardized interfaces for agent communication
• Comprehensive tracking and analytics
• Built-in validation and quality assurance
• Scalable and extensible architecture

These documents provide a foundation for building complex, multi-agent systems with Cursor IDE while maintaining consistency and traceability across all project artifacts.

---

Look at my other posts about self documenting agents:

Development_diary and Diary for Context Continuity with Agent Composer

Some QoL requests and sharing how I DocuGent with Composer Agents (well all AIs actually) Looking for feedback on my Agenting .rmd farming documentation and explanations. I have it do extensive project documentation-as-I-go [image] And You can see that, for this project, for example - I am building a Roulette Simulator which will use FluidX3D Fluid Dynamics to model the actual ball physics, I have it document from the operations manuals and gaming regulations all the variables the tables ac…

+++++

ITS STILL WRANGLING CATS with these fn Agents - but YOLO makes it a much smoother experience as it will respond to its own errors and iterate to a solution, which is sublime.

[POWERUSER]

Is this when you’re using Chat or Composer? Only Composer has your file structure in context I believe. You could try adding rules but it seems like rules only apply to the Chat context and command - K context.