There’s three things to note here with all these strange occurrences.
-
The interface, and the backend are being updated constantly without any transparency or true changelogs.
-
These strange issues occurred at the same time (I believe).
-
There are most likely other issues that we aren’t aware of
As soon as this edit issue occurred I was compelled to investigate. Strange things are fun. It was not a css issue, but more of a rendering issue. As noted previously the edit button did appear for only a moment before a network connection was made (which is indicated by the share link appearing and cGPT responding).
By throttling the network I was able to catch the edit, and send it in (indicating a front-end issue). The interesting thing I found was that the edit successfully sent but the history was not acknowledged. I had no way to go back even though I just made the edit.
So two thoughts:
- They prematurely implemented some new change to prevent first post edits (wouldn’t be surprised)
- They had made some changes (such as a rollback) and were not correctly identifying the first post
I quickly noticed the following: Sometime after July 30th they have been prepending an “unknown” field to messages. Just for reference Custom Instructions came out July 20th. I say July 30th because I just so happened to have screenshot the components on that day for a different reason as seen here (ignore the red circle)
In this screenshot on July 30th it is clear that the user has the EVEN keys (starting from 0) and the model gets ODD keys. So each conversation should end ODD as the model always is the last response. Again, this was already when custom instruction was released.
I also took a screenshot when all of this weird shit was going on. Notice something different?
There is a “ghost” component being prepended with no information. AGAIN. CUSTOM INSTRUCTIONS ALREADY EXISTED. Also, I tested this with custom instructions on and off with no change.
Then, finally, the edit button reappeared. Look at what they did now.

Yes, they hacked a solution by prepending ANOTHER ghost component (indicated by no arrow)
Why would it only be the first comment that was affected? No idea. But the fact that the “fix” was to prepend a second phantom element makes me think that #2 is more likely.
It seems to me the reason the edit button appears only momentarily is because once the conversation is realized & sent back it, is sent with the phantom component causing the edit and history sub-components to vanish.
It seems to me that for whatever reason they rolled back certain parts of ChatGPT. My best guess is that this initial “unknown/ghost” component IS their code not correctly parsing and popping the custom instructions. Resulting in an “unknown” role and empty content. Then again with these very weird titles to me it seems like some miscommunication.
I’m sorry for being late to the party. I was doing some kinky shit for a week. PS If I never post again I have gone on a lifetime vacation so pour one out for me if it be like this.