Codex macOS app: switching between cloud and local can move conversations into the wrong project

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

26.309.31024 (962)

What subscription do you have?

Unknown

What issue are you seeing?

Switching a conversation between cloud and local modes in the Codex macOS app can cause the conversation to become attached to the wrong project/environment.

I have now observed this in both directions:

• Case 1: a conversation belonging to project A was switched from cloud to local, and then ended up under project B.
• Case 2: a conversation belonging to project B was switched from local to cloud, and then ended up under project A.

For reference, the default displayed project names were:

• Project A: agent-storage-manager
• Project B: agents-lab

So this does not appear to be a one-off issue with a single project. It looks more like conversation-to-project binding can become crossed during cloud/local handoff, and the crossing can happen in both directions.

This appears closely related to #11563, but it adds two clarifications:

• Similarity to #11563: both involve a conversation ending up in the wrong environment after switching context and sending the next prompt.
• Difference from #11563: this report highlights explicit cross-project switching between two known projects, and also shows that the problem can happen in both cloud -> local and local -> cloud transitions.

What steps can reproduce the bug?

1. Open the Codex macOS app.
2. Open an existing conversation that belongs to one project/environment.
3. Switch that conversation from cloud to local, or from local to cloud.
4. Send the next follow-up message after the mode switch.
5. Observe that Codex may create or continue the conversation under a different project/environment than the one it started from.

Concrete observed examples:

• agent-storage-manager conversation: cloud -> local ended up in agents-lab
• agents-lab conversation: local -> cloud ended up in agent-storage-manager

What is the expected behavior?

Switching a conversation between cloud and local modes should preserve the correct project/environment binding. A conversation that starts in agent-storage-manager should remain associated with agent-storage-manager, and a conversation that starts in agents-lab should remain associated with agents-lab, regardless of whether the handoff is cloud -> local or local -> cloud.

Additional information

Related issue: #11563

The broader pattern seems to be incorrect conversation/environment binding during mode handoff. The newer observation here is that the misbinding appears bidirectional and can cross between two concrete projects in opposite directions.