openai / openai/codex

Codex App shows a remote project UUID instead of the folder name in the new task composer

Open
#38,496 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

app bug remote
Dominant language
Rust
Stars
125k
Forks
19.5k
PR merge metrics
PR metrics pending

Description

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

26.803.61601 (build 6396)

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Darwin 25.6.0 arm64 arm

What issue are you seeing?

The new task composer sometimes shows a remote project UUID in the folder selector instead of the repository name.

The folder on disk keeps its correct name. The problem is limited to the project label shown in the composer.

The project list contains a local and remote record for the same repository. Both records have the correct label and path. The UI displays the remote record's projectId instead of its label.

Sanitized records:

{ projectKind: "local", label: "sample-repo", path: "/Users/example/projects/sample-repo" }
{ projectKind: "remote", label: "sample-repo", path: "/Users/example/projects/sample-repo", hostDisplayName: "Mac" }

The composer displays a value shaped like <remote-project-uuid> where it should display sample-repo.

What steps can reproduce the bug?
  1. Open a Git repository as a local Codex project.
  2. Make the same repository available through Codex Remote on the Mac.
  3. Open the new task composer for that repository.
  4. Check the folder selector below the prompt field.

In my setup, the selector shows the remote project's UUID instead of the repository label.

What is the expected behavior?

The folder selector should show sample-repo. If Codex needs to distinguish the two records, it could also show Local or the remote host name.

Additional information

Selecting the local project is a temporary workaround. The saved default can still point to the local project while the composer displays the remote UUID.

The screenshot below does not show the repository path, account IDs, host IDs, or session IDs.

Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the new task composer and its folder selector, then trace how local and remote project records are mapped to the displayed value. Reproduce with matching local and remote records and verify that the selector shows the project label, optionally with a local or host distinction, rather than the remote project UUID.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.