A few important questions

How To
1

  1. When I start a new conversation - what are the easiest and best way to get the agent to read ALL of the project files so it can understand what the project is about without asking it again and again to read every single file?

  2. One of the significant issues that is happening is that the agent is reading files from the codebase when it tries to fix problems no matter how many times I ask him to read the actual files. This problem causes the agent to create more problems than fix the problems; is there any way to overcome this problem?

  3. Is there any chance you get an option to connect the project to Supabaase and Firebase like other platforms are allowing us to do today?

Thanks!

2

Maintaining context is kind of the universal rate-limiting factor with these things. Once that’s solved, it’s a bit of a holy grail. It’s become a bit of an art form to come up with ways to help maintain context that spans several different composer sessions. Folks have come up with their own ideas, I’m sure you’ll find lots of tips on here and youtube and /r/cursor subreddit.

Lately, I try to find natural places to stop and the last thing I get the agent to do is write a summary of what it’s done to this point. I frame it like “Summarize the work done so far, and outline the next step. Include all the necessary context and details so that a new developer coming in cold can pick up and get started right away.” With the next agent being the new developer coming in cold. Then I use this as the starting point for the next composer session.

Also, I have a Notepad called “current task” which is a brief detail of what the current task is. I keep it short and tag it to each prompt like a reminder. Some people find using .cursorrules helps, too. But I agree, having a built-in context extension system would be a boon.