Feature request: move an active voice session to another Codex task

Problem

An active realtime voice session is attached to its current Codex task. When a conversation needs a clean continuation task—because the topic changed or the existing context has become too broad—there is no way to move the live voice session to that task.

The current workaround is to end voice, open the destination task, and start a new voice session. This breaks conversational flow and makes task-context management awkward.

Requested feature

Add an explicit, user-controlled action to move an active realtime voice session to another Codex task.

The destination could be:

• a newly created clean continuation task;
• a fork;
• an existing task selected from the sidebar.

Desired behavior

1. Provide a “Move voice conversation to…” action in voice controls or the task menu.
2. Let the user select and confirm the destination before changing anything.
3. Preserve the live voice connection when possible.
4. Treat the destination task’s context as authoritative.
5. Let the user choose whether recent transcript is copied into the destination.
6. Never merge unrelated source-task history automatically.
7. If live transfer cannot complete, offer a graceful fallback: open the destination and restart voice with a short handoff summary.

Example use case

A user is discussing a technical design, creates a clean continuation task containing only that design context, and wants to keep speaking without restarting their voice session. The original task may contain unrelated digressions that should not enter the new task’s context.

Why this matters

Realtime voice naturally supports exploratory conversation, where temporary digressions are normal. Task-level context management and voice should work together so users can preserve clean task context without losing the momentum of a live discussion.

Scope

This request is about explicit task ownership and session routing. It does not require automatic semantic summarization, memory changes, or automatic merging of task histories.

Start by tracing how active voice sessions are owned by tasks, then inspect the voice controls or task menu entry points and the destination-task selection flow. Done means a user can explicitly confirm a destination, preserve the live connection when possible, choose transcript handling, avoid unrelated history, and receive a fallback when transfer fails.