Now the composer is only in the chat on the right? When I press ctrl+shift+i - I can’t open it in a separate window
I can’t find @codebase, how can I work on the whole project now?
The agent does not make changes to the code itself, but works as a chat. That is, you have to open each file manually and click “apply”
Perhaps everything has become more convenient, but we need to understand how to work with updates that have fundamentally affected the user interface.
Found another problem.
I’m developing a mobile app on Flutter. It only sees native code, right away without using @CODEBASE, but it doesn’t see the lib folder and dart files. Please fix it. It’s become very difficult to work.
Hey, Cursor will ignore files that are in .gitignore or .cursorignore so make sure they aren’t in there!
If they aren’t, can you see them in your codebase index settings? You might have to delete and recreate the index, but you can see all the files Cursor indexes to ensure it’s looking at all your field.
I think they are trying too much to keep up with windsurf as it has had a lot of buzz in the last few weeks. However, personally whilst this is a good move as windsurf is very good at maintaining context, windsurf felt too autopiloted. Composer felt more like you had control as a dev and that’s why I liked it. I have just tested the agent mode and it’s a good approach, as we also have normal mode meaning we still have the previous functionalities of composer. What they have broken is the UI in trying too much to be like windsurf. I’m guessing this is easily fixable. They just need to make sure people that have used cursor for a while don’t feel like it’s a completely new UI etc. which is the way I feel now. I cancelled cursor subscription and went windsurf but came right back to composer because the experience felt like it gave some power to the dev. There’s a market for us!
Updated. @codebase returned. Thank you
If it is possible to make the agent work with third-party AI, except for anthropic, it will be absolutely great. I am interested in QWEN 2.5 Coder. I connected it through third-party resources. If you can add it to native neural networks, within the tariff, it will be just as wonderful and excellent!
Bumping this, as the original bug report still applies to 0.43.5. I see “Add to Chat” but not “Add to Composer”. This is critical for my unit testing flow, as I need to be able to easily send failed test results to Composer.
This is bad timing, as I’m trying to get the full dev team to get back to good unit testing habits, and this breakage makes this far harder.
