Composer Autosave UX Failure

I just experienced a really frustrating UX failure in the ChatGPT desktop app that I think needs urgent attention for power users, developers, writers, researchers, and anyone using ChatGPT as a real cognitive workspace instead of just a quick chatbot.

I had several long paragraphs typed into the composer. Detailed product architecture, formulation concepts, ingredient systems, positioning ideas, etc. I switched to “Thinking” mode, and the entire message draft was instantly erased. I forgot to command C which i usually do, but USUALLY it saves the draft in the composer when its not in a project folder I just didnt know it wouldnt this time.

Not submitted. Not recoverable. Just gone.

The biggest issue is that the composer currently behaves like a disposable text field when many of us are now using it like an active IDE / notes app / creative workspace / research environment.

Losing a 30-second message is annoying.
Losing 20+ minutes of structured ideation breaks flow state completely.

Suggestions:

• Persistent autosave drafts
• Local encrypted draft recovery
• Draft history/versioning
• Recovery banner after composer reset
• Prevent mode/model switches from touching the text buffer
• “Are you sure?” warnings before destructive rerenders
• Automatic backup for long-form drafts

The current workflow makes users afraid to switch models or modes while brainstorming because there’s a real risk of losing unsent work.

This becomes especially important as ChatGPT evolves into a serious creation environment for coding, design, writing, product architecture, and technical ideation.

Would love to know if others have experienced this too.

Hi @protoolsqueen, losing a long draft like that is incredibly frustrating, especially when you’re using ChatGPT as a real workspace for brainstorming or architecture thinking.

A few people have reported similar issues around mode/model switching wiping the composer unexpectedly. The current behavior definitely feels risky for long-form work.

Your suggestions around autosave, draft recovery, version history, and safer mode switching all make sense. I’ll make sure this gets captured as product feedback because this isn’t ideal for power users at all.

-Mark G.