[Codex App] Pinned tasks hide the active workspace folder and provide no way to change it

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

Codex Desktop 26.727.51351 (6119).

What subscription do you have?

Pro

What platform is your computer?

macOS, Apple Silicon (Darwin 24.6.0, arm64).

What issue are you seeing?

When a task is opened from the global pinned-chats list, there is no easy, persistent way to see which local folder/workspace the task is working against. There is also no visible control for changing or rebinding that folder.

This is risky when similarly named checkouts are in use (for example, Main and Main2): the user cannot verify the active working folder before asking Codex to inspect or modify files.

This appears to be a current regression or an incomplete fix related to closed issue #28483. That report covered project context missing from pinned rows; the problem also persists inside the opened pinned task, where the working folder cannot be readily verified or changed.

What steps can reproduce the bug?

1. Start a local Codex task associated with a project folder.
2. Pin the task.
3. Open it later from the global pinned-chats list.
4. Inspect the pinned row, task header, composer, and available task menus.
5. Observe that the full working folder is not readily visible.
6. Try to change or rebind the working folder and observe that there is no obvious control to do so.

What is the expected behavior?

• Always show the active folder/repository path in an easy-to-find place in every local task, including pinned tasks.
• Provide a clear project/folder selector for changing or rebinding it when appropriate.
• If rebinding changes sandbox scope or task state, explain that and request confirmation.
• Include enough project context in each pinned row to distinguish similarly named tasks from different folders.

Additional context

Related closed report: #28483. Related feature request: #25448.

The current task was working against /Users/mmuegel/Mike/Git/Main, but that information was not visible to the user in the pinned-task interface; it was only recoverable by asking the agent.