What we win:
Nothing, the new way is doable right now.
What we loose:
A lot of speed, right now we can iterate faster on prompts in the playground. Just get a prompt that is not working and iterate over it without needing to touch the code.
Welcome back, @Gustavo_Stefani …
I still use the playground quite a bit personally.
Everything is changing so fast these days… I still miss text-davinci-003 personally. 
This is terrible I have a lot of web apps based on prompt objects, is super convenient cause I can make small fixes to the prompt without redeploying, and also rollback to previous versions. I don’t understand what’s the reason behind this, it’s actually an efficient “vendor lock” they have in place. I hope they reconsider
agreed- the main advantage of stored prompts is application independent, rapid prompt development, model optimizations and hotfixing. Migrating prompts to the projects codebase won’t help with either of these.
Totally agree.
My customers will probably start asking me to move to a more stable AI provider since OpenAI very frequently forces us to migrate/change to other ways of doing things.
The migration from Assistants API to Responses API was full of benefits, and I got that. But this does not have any benefit that I can see and actually is a step back in many aspects and makes it more difficult for non-programmer users to maintain and evolve chatbot and AI automation solutions.
Yes and this is not a transition they are just removing a useful feature without a replacement. The “migration guide” is like “put this back into your code and good luck”. Not a good sign honestly
Does this mean that the “Chat” prompt menu and functionality within OpenAI API Dashboard will now be deprecated?
I use this functionality in all of my projects, and if the deprecation notice is true, requires changing many, many projects, and hence receiving less functionality and adaptability.
I trust OpenAI will reconsider this deprecation notification.
IMHO: Nothing lost.
An attempt to force you into a UI to make a prompt as a reusable undiscoverable incomplete request shape that requires knowledge of it for success anyway.
Developed as playground-UI-only simply to increase the friction of simulating a “GPT” for a user on demand?
How to use the API like a normal person:
Maybe now: turn back on the Playground Chat Completions presets, which were locked from editing and creating, now pinned to shutoff models, as a scheme to force-promote “prompts”.
Is our stored prompt will be gone? where do you guys save the template?
If you really want back out what you put in, you can use a browser’s web developer tools → network, and monitor the requests and responses to the API URL that services the web page of “chat” when you switch between prompts (preset settings) and the values are pushed to the UI.
Another internal API gated to Oauth2->session token and browser signature - where API access could have made the system a bit more useful.
Whats the point of separate projects in the openai UI Dashboard? No agent builder, no chat prompts, … there doesnt seem to be any reasons to have a dashboard.