Title: Restore automated creation of visible project-owned Codex project chats
Problem: In my current Codex project, the agent can create hidden/internal sub-agents but cannot create visible, user-owned chats within the project. Earlier project workflows supported creation of a separate project task from a coordinating chat.
Impact: This breaks project-management visibility, auditability, ownership, handover, and recovery. A hidden sub-agent is not a durable workstream owner: it is not visible in the project sidebar, cannot serve as an independently reviewable participant record, and cannot reliably demonstrate work assignment, acknowledgement, checkpoint, or coordinator receipt.
Why the fallback is unacceptable: Replacing visible participants with sub-agents forces manual task creation, repeated prompts, and extra project files merely to reconstruct state that the product previously represented visibly. It also makes an agent appear to comply with a governance framework while the required visible ownership model is absent.
Requested behavior: Expose a supported in-chat control to create one visible, user-owned project chat with:
- project/host and working-directory selection;
- title and initial bounded assignment;
- clear user-owned vs. internal-subagent status;
- a stable task/thread ID plus provisioning status;
- no automatic implementation before explicit activation;
- sidebar visibility, searchable history, and an auditable handover route.
Expected outcome: A project chat can create visible participant chats after planning, each chat can acknowledge its role and wait, and the user can inspect ownership and execution directly without extra administrative reconstruction.