Cmd+N new chat should support a fixed default workspace instead of reusing the last/current project
Resolved 💬 3 comments Opened Jun 1, 2026 by zhyuzhyu Closed Jun 12, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
Summary
In Codex Desktop App, creating a new chat with Cmd+N currently reuses the last selected or current project/workspace. I would like Cmd+N to always start from a fixed default workspace, for example the home directory (~), while preserving the existing behavior for project-specific "new chat" buttons.
Current behavior
If I create a chat under a subdirectory/project such as ~/kk, the next Cmd+N new chat may also start in ~/kk. This makes it easy to accidentally start general chats in the wrong workspace.
Desired behavior
- Global Cmd+N / File > New Chat should use a configurable default workspace, ideally
~. - New chat buttons inside a specific project/subdirectory should still create the chat in that selected project/subdirectory.
- This could be a setting such as "Default workspace for global new chat".
Environment
- Codex Desktop App: 26.519.81530
- Codex CLI: 0.133.0
- macOS: 26.5
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I missed the duplicate search before filing this; sorry for the noise.
After checking the related issues, this overlaps with #24731 and the broader workflow discussion in #24222, and is adjacent to the projectless workspace-root requests in #22875 / #24883.
The narrower distinction I intended to capture here is: I do not necessarily want global Cmd+N to default to
No Project; I want it to be able to default to a configured neutral workspace such as~, while project-scoped new-chat buttons continue to use the selected project/subdirectory. If maintainers consider that covered by #24731, this can be closed as a duplicate.Closing as a duplicate of #24731.