When I added files to context in composer mode - the content of those files would be passed along and it would be able to read the context
In agent mode, for whatever reason, if I add files to context, it then decides it should search for those same files (as if it can’t see them)
In composer, if I tag 13 files (my routes, controller, several example frontend components) - it sees all of them and follows the pattern
Do the same in agent mode - it uses file search to file the controller, reads it in portions, sometimes misses to add routes, and doesn’t always explore component examples so comes up with new stuff.
Why is the file tagging even there if it doesn’t work in agent mode!?
Please, please address this as it is the only step away from me using Agent properly and it is incredibly misleading UX
I hate to bump this but it’s frustrating when this issue is still prevalent as larger features are still being added - and it’s been a problem since the mode existed
There are competitors that are now coming up that do not lose file context in the sub-routine
Even today, I did the following:
Add this to the end of every message: “Please read files in full and instruct any sub agents to read files in full, including the ones I provided. These are critical context and it is only useful if the full file is read at once - partial reads are pointless”
Ticked the longer context box
Added similar instructions to my cursor rules
Yet still, 3 tool uses in, it reads 50 lines of a 664 line controller where the whole context is extremely important, leading it to output broken and useless code apply suggestions
Having been a paid user for a long time, and Ask (composer renamed?) seeming to have regressed even further, this is mega frustrating
This is a core feature that is just NOT WORKING according to user expectation. I have been a Cursor Pro user for a while, and if this isn’t addressed I am also considering switching.
