"New Chat" at top-level of app attaches chat to arbitrary existing project

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

Windows Version 26.616.71553

What subscription do you have?

Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

The heuristic is that the perceived command scope of a “New” action should match the visual and structural scope in which that action is placed. A “New” button associated with a parent-level context should be expected to create a parent-level object, not an object inside the currently selected child context.

Projects have a "new chat" button -- these work clearly.
Outside the scope of projects, above any projects in the list, there's a separate "new chat" button -- this button works outside their command-scope.

None of this would be a problem if a existing chat could be moved into a different project.

What steps can reproduce the bug?

1. Work in an existing project
2. From left side-bar, at top level above projects start "new chat" (attempt to create a new unattached chat)
3. Chat will be created with existing project populated

What is the expected behavior?

1. New chat made in first-class app scope is not attached to a project by default
2. If chat is being irrevocably attached to a project, this is first-class information and clearly displayed (not a small grayed-out drop-down that my eyes are trained to ignore).

Additional information

_No response_