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

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

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗