# One-Click "Continue in New Chat" Button for Seamless Thread Migration

**URL:** <https://community.openai.com/t/one-click-continue-in-new-chat-button-for-seamless-thread-migration/1401276>\
**Category:** Feature requests\
**Tags:** chatgpt, feature-request, chat, chatgpt-ux, memory\
**Created:** [September 27, 2026, 1:40pm UTC](https://community.openai.com/t/one-click-continue-in-new-chat-button-for-seamless-thread-migration/1401276 "2026-09-27T13:40:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![neeraj.lilani](https://avatars.discourse-cdn.com/v4/letter/n/5e9695/32.png) [@neeraj.lilani](https://community.openai.com/u/neeraj.lilani)\
**Post date:** [September 27, 2026, 1:40pm UTC](https://community.openai.com/t/one-click-continue-in-new-chat-button-for-seamless-thread-migration/1401276/1 "2026-09-27T13:40:23Z")

</div>

When a chat thread reaches its token limit or enters a state of context degradation, users face a significant workflow disruption. They must manually copy the latest code or project state, open a new chat, and write a prompt to re-establish the context before they can continue working.

To resolve this friction, I propose introducing a native **“Continue in New Chat” button**. This feature would automate the transition by taking a pre-set prompt, combining it with the relevant current state or the user’s latest clipboard text, and launching a brand-new chat instantly.

Furthermore, this mechanism should trigger automatically as a **final system message** right before the platform’s hard chat limits are reached. Instead of abruptly blocking the user, the interface would present this automated migration prompt, ensuring zero inconvenience and a completely seamless handoff from the old thread to the new one.