make sure to include your version number 
. btw doesn’t happen to me on latest. but I have dozen of other small bugs, this composer needs some serious love from the UX team (when I click any file, it can scroll the chat backwards thousands of lines for no reason, buttons that don’t work or not disappear when they should, and stuff like that).
Hi @aliensoul,
Sorry for buttons missing! Could you show me how to repro? Would love to fix. In terms of “clicking the file” what file are you referring to? Is it the code pills?
yup here’s exact things I notice when working, I’m in a 80 files codebase of typescript, cocos2dx game but not really relevant - that’s the total size, and index is on. I’m using o1-mini. The first few questions to composer were “describe the project structure etc” to pre-warm it and it’ll understand the files and what’s where. Then I started editing components (like the player movement and acceleration, rotation, controls of on screen joystick, etc) and noticing the following:
- when composer completes a suggestion, the green circles near files that it already edited in the past, will be lit, as if there’s a new change incoming, but when I click it (and I’m in diff mode selected) there’s no new content, so the green circle was lit by mistake, since composer did not edit the file.
- when we have a diff, and click on ‘accept’, the button will remain there, instead of disappearing or I don’t know, maybe becoming greyed out, but it needs to get out of there
because in an hour if I go for lunch and come back, I’ll not remember if I already clicked it or not. reproducible 100% for me currently. I think it should disappear and a ‘save’ and ‘reapply all’ text buttons will appear? it was like that, but now doesn’t. The “check mark” did appear instead of green circle though (on the file in sidebar) so that part works on click of accept. - after few iterations and thousands of lines in chat on right side, when I click a file on left side which was already edited many times before, I will end up scrolled upwards in the chat on right side, to possibly the first ever interaction that led to that file being edited (just a guess), but that completely throws me away from ‘current’ conversation with the ai. seems like an easy fix, it needs to know the ‘latest’ interaction with that file and not start from first?. I hope it’s in the right direction, but if not, that’s all I can observe from my side.
- when the green circle lights for no reason (the issue N 1), navigating to that file and clicking the ‘accept’ in the bottom, (which should not even appear I think, since was no diff anyway), does not convert green circle to ‘check mark’, which is confusing and I might go over the same files again thinking there’s some content in them which I didn’t save (while if the ‘accept’ click on this ‘no changes were made file’ would at least convert the circle to check mark, then I’ll know “I’ve been there and dealt with it” .
I am testing this on an open source repo of cocos creator game, it’s one of the games from their examples, so you can play with the same exact repo as well (I excluded the**/*.metafiles, so you can do too, in order to reproduce my exact settings). It’s this game GitHub - MartinKral/Slash-The-Hordes: Rougelite game, made in Cocos Creator
I also noticed this, when I sent the prompt I tagged the “@folder” of all scripts of the game (it has the 80-100 files, they’re all tiny though, I think might even all fit into a 10k context) but it says file was not provided - AND it actually does edit the file which it says was not provided (destroying all its code and making a mess, but that’s another story and we need to wait for better models, the o1-mini is not the messiah we’ve been waiting for 
unfortunately, it feels roughly same like sonnet3.5, at least on the typescript code)
here’s the situation after clicking “accept all” and “save all” (in the composer chat), the green circles are all on, except those where I manually went in the specific file and clicked an accept on a single file there. They all had to become green check marks? so we’ll know they’re applied. Also diff visuals remain - but this is by design I think so we’ll see what was applied in last iteration (‘checkpoint’ of the chat)? what are the checkpoints by the way, how does it keep them? (I have auto-commit off)
I to have had this issue sporadically recently as well. I’m not able to intentionally reproduce it and have not found a way to work around it other than to resend the prompt.
I also want to add that I frequently see the Accept All button be available while it is still generating. Not sure if they are related though.