Thanks for the detailed review @litecode, that was very helpful! I’ll think of ways to make the UX more intuitive.
2 Likes
Thanks for a great feature, From what I can see so far it replaces a good chunk of what I would use Intepreter mode for.
Personally not a fan of having it as a floating box and would like to pin it somewhere, Have lost the top bar once or twice as it expands upwards.
I love the ‘floating’ feature - can we have both? 
A dockable mode and a pop out mode?
Also, in regards to the ‘floating’ feature, perhaps a bug:
- I have noticed when i try and drag the ‘Composer’ window to another screen it ‘disappears’ (it’s like the
z-indexof the ‘Composer’ window is lower than the content of my other screen)
I’d also love Ctrl + L to be able to ‘pop out’ so that I could drag it to another screen - currently I can click on the ‘Chat in Editor’ icon, and then drag the ‘AI Chat’ tab to another screen, but there seems to be a bug where the prompt area then stops accepting text.
2 Likes
Here is a simple demonstration of what is possible in Composer, in case you were still wondering.
I entered this prompt in Composer:
I want to demonstrate the multiple file editing capabilities of the new Composer feature in Cursor (the fork of VS Code).
Plese create a folder called ‘TestHTMLSite’ that contains an index.html file and css and js folders that contain the code required to create a simple HTML website.
Add any simple JS functionality that you think would be cool.
The theme of the site should be:
Cartoons and clouds and fun, happy things!
Thanks!
Below are screenshots of:
- The prompt
- The response
And then after clicking ‘Accept All’:
- The generated folder/file structure
- The frontend site
The prompt
The response
The generated folder/file structure
The frontend site
3 Likes
Thanks for the good work. Cursor has changed the way I write code. Indeed, I almost do not write code and I’ve become more productive by orders of magnitud.
I haven’t used composer too much, but here I leave my first impressions.
I’ve found it very powerful. This is what I used in the interpreter, but much better.
I miss to be able to reopen the old session, like in the classic chat bar. I needed to use the console to deploy and closed the modal. WHen I reopened, the history was lost and I didn’t found any option to open it back (though I didn’t search a lot).
Also I found it cumbersome to add the files to edit.
But overall, a step in the good direction. In my edits I usually referenced many files, as good code should be split by concerns. Then, I applied the changes one by one. Composer streamlines the process. I foresee me using this feature much more than the classic chat.
2 Likes
One thing I noticed that was consistently frustrating was that the context is not persistent between sessions. So say I generated a bunch of folders and files in one session, close, then open another. There’s no easy way to quickly get back to the context I had before. You can add files for context one by one, but that would take a long time for complicated generations.
2 Likes
Noted, will improve
@kuakeye - do you think that issue would be resolved through some sort of ‘Composer Chat History’? I wondered about that in this post:
https://forum.cursor.com/t/does-composer-retain-composer-chat-history/6508
3 Likes
I think so! The current chat history restores all context of that history that was pulled up correct? Then you can pick right up from that chat thread?
1 Like
It seems not to work with custom models (DeepSeek-Coder with its OpenAI base URL) / I can’t choose one, so it throws ‘Connection failed.’ every time
Changelog link:
1 Like