Mobile project name is incorrect while in the remote view

Below are the images to show the differences.

<img width="388" height="301" alt="Image" src="https://github.com/user-attachments/assets/40f55c2a-d219-4f8b-8ca6-886ba05605c4" />
<img width="266" height="333" alt="Image" src="https://github.com/user-attachments/assets/0856bab5-6f1f-48f8-91bb-f006ba85add7" />

I’m seeing what appears to be another manifestation of this issue on Windows + Android Remote.

Instead of showing another human-readable project/repository name, Remote displays an internal-looking identifier such as g-p-6a8bf03bcf408191b978b0b93bd02..., while the associated conversation still appears normally under Recent as 執行 Task 25 bounded repair.

The affected conversation had previously been pinned and then unpinned in Codex Desktop. However, I could not reproduce the problem with a simple test conversation, so pin/unpin is only a suspected trigger, not a confirmed cause.

I originally reported this separately as #40750. Since the observable behavior is the same class of Remote project-name mismatch, I’m consolidating the report here and closing #40750 as a duplicate.

Additional evidence

I can now confirm that the affected conversation belongs to the Stock project on Codex Desktop.

The project was previously named TwStock and has since been renamed to Stock.

On Android Remote, however, the Projects list still shows TwStock, and it also shows the internal-looking g-p-6a8bf03bcf408191b978b0b93bd02... entry.

The affected conversation 執行 Task 25 bounded repair is visibly located under the Stock project in Codex Desktop.

This strengthens the evidence that the Remote project metadata is not synchronized with the current Desktop project name. It also suggests that the g-p-... entry may refer to the same Stock project, possibly as an internal/fallback identifier, although that mapping is not yet independently confirmed.

This makes project rename / stale project metadata a more direct observable clue than the earlier pin/unpin hypothesis.

<img width="1080" height="2400" alt="Image" src="https://github.com/user-attachments/assets/ced569e8-fb33-441e-a4f4-8cb4da897c49" />

<img width="1109" height="787" alt="Image" src="https://github.com/user-attachments/assets/409618c7-b950-490e-94b8-3a9b43d721b9" />

<img width="1080" height="2400" alt="Image" src="https://github.com/user-attachments/assets/6c26d5d6-f15d-4ef1-8e97-b7f3fd7e94c7" />

New recurrence / additional reproduction evidence

I observed another new internal-looking g-p-... project entry on Android Remote:

g-p-6a7bca7f8de08191bd540f13fe26d...

This is a different identifier from the previously reported:

g-p-6a8bf03bcf408191b978b0b93bd02...

I can now provide a more specific sequence for this new occurrence:

1. I started work from ChatGPT and sent it directly to Codex for execution.
2. Codex created a new chat for that task.
3. Android Remote showed a new g-p-... entry associated with that newly created chat.
4. I later moved the chat into my existing AllyVoxNote project in Codex Desktop.
5. Android Remote continued to show the original g-p-... entry instead of fully reconciling the chat/project association.

The earlier g-p-... entry and this new one belong to different conversations/projects, so this no longer appears to be a one-off corrupted project record.

This suggests that ChatGPT → Codex-created chats may retain a stale internal project/container association in Android Remote after the chat is moved into a normal Codex project.

I am using “internal project/container association” descriptively here; I cannot independently confirm what the g-p-... identifier represents internally.

Screenshot attached separately shows both distinct g-p-... entries at the same time.