macOS app returned content from an unrelated conversation and showed inconsistent thread state

What version of the Codex App are you using (From “About Codex” dialog)?

26.803.61601

What subscription do you have?

ChatGPT Plus

What platform is your computer?

macOS, Apple Silicon (arm64)

What issue are you seeing?

On August 13, 2026, the macOS app returned content apparently belonging to a separate conversation.

In an independent non-project travel-weather chat, I submitted this prompt:

“What is the current tropical situation and potential implications for the cruise? Also include focus on sea conditions for the vessel.”

Instead of answering that prompt, the app returned detailed continuity-migration content associated with an unrelated confidential client-project conversation. The preceding messages in the displayed thread were correctly about tropical weather. I also observed the reverse behavior: a client-project conversation unexpectedly initiated a National Hurricane Center search.

I have no evidence that information crossed between user accounts, but content crossed conversation and project boundaries within my account. Please determine whether a response or tool run was generated under one conversation and attached to another, and confirm the containment boundary.

Potentially related macOS app behavior observed the same day:

1. One long conversation displayed: “You've reached the maximum length for this conversation, but you can keep talking by starting a new chat.” That conversation remains unable to accept messages.

2. A different conversation displayed the identical notice temporarily, but the notice later disappeared and the conversation became writable again.

3. Adding a clarification while a response is actively thinking can freeze the application. Stop becomes ineffective, requiring a complete app restart. After restarting, reasoning has reverted from Extra High to Light.

Private diagnostic feedback, including the affected session logs, was submitted under Feedback ID:

no-active-thread-019ffba0-b700-76c0-92b2-228339cffef1

Please use that private feedback submission for the affected content and telemetry. I am intentionally not posting confidential conversation text or screenshots publicly.

What steps can reproduce the bug?

Feedback ID: no-active-thread-019ffba0-b700-76c0-92b2-228339cffef1

What is the expected behavior?

No response

Additional information

No response

Start with the private diagnostic feedback identified by Feedback ID no-active-thread-019ffba0-b700-76c0-92b2-228339cffef1 and investigate the affected macOS app sessions. Determine whether a response or tool run was generated under one conversation and attached to another, and confirm the conversation and project containment boundary.