Reverting to old Playground UI

API Feedback
1

I’m having difficulty with the updated Playground UI. The older version felt much simpler.

Editing messages, cutting text, deleting, and requesting a new response could all be done within 2-3 seconds. Now, with the updated UI, I have to scroll all the way up just to find the dumpster icon or the delete button, and text is non-editable unless I click the ‘pencil’ icon. Assuming the AI generate pages of response, and you have to look for those buttons, to edit to regenerate another response.

This feels like a downgrade in user experience. I understand OpenAI may want users to stay on the site longer, but I hope there’s an option to revert to the old version.

2

It was indeed much simpler. Feature-less. Didn’t expect it to go away completely, but no loss.

Past issues

You could not edit the role of a conversation message. You were hosed if you accidentally added the wrong role sequence that would auto-switch on you. Copying long text was horrendous. You had no choice to see a rendered version of output. It had a bug where you couldn’t even add linefeeds without pasting.

Now - a chain-of-thought enhanced bot, rendered

A text instructs the creation of a rich-text, emoji introduction, with the assistant outlining the guidelines and providing an overview of its capabilities. (Captioned by AI)
A text instructs the creation of a rich-text, emoji introduction, with the assistant outlining the guidelines and providing an overview of its capabilities. (Captioned by AI)658×433 25.5 KB

(the width at least is good for screenshot)

The user message markdown I gave gets pretty, along with the output being as your app should show.

You have to click “edit” for the message source.

But over here, that’s what I do also - edit and you get monospace. It’s like they looked at my personal app screenshots from a year ago…

A screenshot of a chat interface displaying a welcome message and a demonstration of rich text rendering. (Captioned by AI)
A screenshot of a chat interface displaying a welcome message and a demonstration of rich text rendering. (Captioned by AI)528×203 13 KB

Improvements

  • A “developer sees exactly the output, everywhere” switch to turn off markdown render would be nice.

  • Leave the buttons and the frame around messages shown. Stop the hovering hiding actions.

  • The entire message could easily be an “edit button”

  • Stop guessing JSON badly. A square bracket does not mean a switch to monospace.

  • Collapsible “instructions” side panel, or a handle for the divider, to solve everyone’s width complaints

  • Pressing “enter” does not insert a linefeed, it stops editing (your button click saver). You have to discover yourself that shift-enter is needed.

  • The new playground can unexpectedly move messages over to the left panel, unseen past the bottom, especially for presets. That’s already caught me, sending undesired messages.