Feature request: persistent, project-aware voice navigation

Summary

Voice mode is currently tied to a single full-screen conversation. Leaving it to inspect another Codex thread stops the live interaction, even when multiple projects and agent tasks are active.

Please consider an optional, persistent voice layer that remains available while a user navigates between conversations and projects.

Proposed interaction model

• A general voice companion for cross-project priorities and routing.
• A project-specific voice context for work inside a project, visibly identified by project name, role, and a distinct visual treatment.
• Clear voice-first navigation: “switch to Project A”, “open the release conversation”, “return to the previous project”, and “create a new conversation in Project B”.
• A “capture this for Project B without switching context” command for cross-project thoughts.
• On returning to an inactive project conversation, an optional concise briefing: progress, blocker, and next decision.
• A choice to pin voice to the current project or let it follow navigation.

The key requirement is explicit context. Every switch should be visible, briefly acknowledged, and easy to undo so instructions never silently land in the wrong project.

Autonomy and control

Project contexts could coordinate background agents around short-, medium-, and long-term objectives. Their autonomy must be bounded and inspectable: show current work, pending decisions, approvals required, and a compact status on demand. Routine progress should be quiet by default.

Mobile first, desktop native

Mobile is the right place to validate the interaction contract: minimal taps, limited screen space, and instant clarity about who is listening and which project is active. Desktop should preserve the same model while adding native strengths such as keyboard shortcuts, multi-window work, and lightweight overlays.

Clicky is a useful interaction reference: it treats voice as a persistent, screen-aware companion rather than a chat screen. Codex would need to extend that idea with project-scoped context and safe routing across multiple ongoing tasks.

Relationship to existing requests

This complements #33966, which focuses on duplex voice collaboration with one active Codex session. This request focuses on keeping voice available across sessions and projects without losing context or control.

Why this matters

For users coordinating several projects, voice should reduce navigation friction rather than force a stop-and-restart loop. The goal is not more agents or more narration; it is a calm, persistent conversational layer with unambiguous context and human control.