RESOLVED - for those people looking for Composer - it was merged with chat / agent to simplify UI. I think they may remove Composer references from Keybinds / other UI sections if / where references to it may or may not exist.
Hey, actually, Agent and Edit are the same as Composer. We’ve combined them for your convenience. Edit is equivalent to Composer in normal mode, and Agent is the agent mode.
The Keybinds section still refers to Composer, and changing the keybind to open composer opens chat. I’m delighted that agent and edit are the same as composer, but I would advocate for updating all references to composer to agent - if you’re feeling frisky call it “SuperAgent” or “IntelliAgent”, and add that to the documentation, as I checked the documentation and couldn’t find a specific line mentioning removal of composer or merging it with chat. I looked for that specifically. I thought that might be the case but various chatter around Composer in the last 2-4 weeks made me think it was still there.
I no longer understand the difference between Agent, Edit, and Ask. To me it looks like Edit and Ask are basically the same thing? This could do with a doc update Cursor – Composer (well, an overview on the Editor parent heading). Thanks
why is this convenient? we’re using them for different tasks, sometimes simultaneously. use chat for intermittent questions while composer is doing feature development. also, composer doesnt work at all with jupyter notebooks, so using chat for notebook code and composer for feature dev at the same time. terrible UX decision tbh
if the agent and edit is now working as composer then why @codebase is not there anymore? I want cursor to make some changes and I want him to change it in entire codebase wherever it’s necessary to make changes, but now how to do it? Do i have to manually add individual file by tagging them which I think is necessary?
Its frustrating to be honest, I took cursor PRO but it seems like its not worth it, if it’s gonna be like this, I most probably going to cancel the plan because GPT can assist me better if I only have to explain the whole codebase to the AI, in composer @codebase was there and it was pretty cool to save the time, i didn’t have to explain the codebase it automatically does those things but now there no more @codebase, I have to individually tag the files or have to explain it, its similar to GPT now and not worth paying a single penny
Здравствуйте! зачем вообще было так делать и менять что и так работало? просто отняли кучу времени на поиск этого сообщения и понятия что и как теперь работает. Просто верните composer! please return composer
Yeah, this was a terrible decision. I have tried to adapt. The history menu is right there to let you toggle back, so in theory we still have multiple threads of context, but:
Toggling to another thread only changes the mode, not the model being used, thus 4 clicks to go back to a previous context
Even if both changed, you’re still talking about two clicks and less convenience than having a tab
It’s core to many people’s workflow to have a chat going with a cheaper/faster model and then compose work going in a different context. We don’t need to go back to the same UI, but we should at least being able to create multiple tabs (one-click access).