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.