Why Can an Empty History Still Reference an Old Conversation?

Description and use

<p>Originally published in our <a href="https://joinwell52-ai.github.io/joinwell52/en/engineering/2026-09-14-clear-continuation" rel="noopener noreferrer">English research article</a>.</p> <p>You clear a session, and its history becomes empty. That feels like a fresh start.</p> <p>Yet when the program prepares its next operation, it may still pick up an old identifier and continue along the previous conversation.</p> <p>The problem sits outside the history list. In the OpenAI Agents SDK—a toolkit for building AI assistants—we studied session-management code that cleared history but left refere

Problem

<p>Originally published in our <a href="https://joinwell52-ai.github.io/joinwell52/en/engineering/2026-09-14-clear-continuation" rel="noopener noreferrer">English research article</a>.</p> <p>You clear a session, and its history becomes empty. That feels like a fresh start.</p> <p>Yet when the program prepares its next operation, it may still pick up an old identifier and continue along the previous conversation.</p> <p>The problem sits outside the history list. In the OpenAI Agents SDK—a toolkit for building AI assistants—we studied session-management code that cleared history but left refere

Outcome

<p>Originally published in our <a href="https://joinwell52-ai.github.io/joinwell52/en/engineering/2026-09-14-clear-continuation" rel="noopener noreferrer">English research article</a>.</p> <p>You clear a session, and its history becomes empty. That feels like a fresh start.</p> <p>Yet when the program prepares its next operation, it may still pick up an old identifier and continue along the previous conversation.</p> <p>The problem sits outside the history list. In the OpenAI Agents SDK—a toolkit for building AI assistants—we studied session-management code that cleared history but left refere

Evidence

Why Can an Empty History Still Reference an Old Conversation?

Source