Repository navigation
feat(voice): talk to existing threads with GPT-Live - #11667
quentinsteinke wants to merge 2 commits into
Conversation
|
Hi @quentinsteinke, I updated the voice UI and rebased the branch onto current main. Key changes:
Branch: https://github.com/mujuni88/t3code/tree/jbuza/voice-inline-prototypes If this direction looks good, please pull it into feat/gpt-live-voice. |
|
Note 🤖 GPT-6 Astra responding on behalf of Theo We're closing this as part of a cleanup of stale PRs. Thank you for the time and care you put into this contribution. A local merge check found conflicts in 8 files against the current target branch. The latest implementation commit is from 2026-09-14, and there has been no contribution update in over a week. At this point, regenerating a focused patch against the current intended base would be easier to review and maintain than updating this PR. We appreciate the work and will keep this thread as a reference. If you revisit it, please check the current direction with us and link the fresh PR back here. |
What Changed
Adds experimental GPT-Live voice conversation to an existing thread on web, desktop, and native mobile. Users can speak with GPT-Live, send coding requests to the thread's selected agent, hear agent updates, and read captions during the call.
The environment server creates the Live session using its
OPENAI_API_KEYand handles client delegation through the existing thread command path. Audio travels directly between the client and OpenAI over WebRTC. The API key stays on the server, and voice uses separate OpenAI API billing.Calls stay attached to one environment and thread. Mute pauses microphone input; End call releases voice resources while accepted coding work continues. Navigation, backgrounding, or connection loss ends the call. Existing provider approvals remain in the thread. Mobile microphone ownership prevents overlapping Live capture and dictation.
Why
T3 already lets users direct their coding agents across devices. This adds a spoken interface to the same thread without adding voice methods to each provider adapter or replacing existing dictation.
Unlike #8324, GPT-Live manages the conversation and delegates to T3's existing command flow; this does not negotiate Codex-native realtime sessions or require a Codex-specific voice protocol. Related prior voice proposals include #6206 and #3997. This is still an experimental feature contribution; the different implementation does not assume maintainer approval of the product scope.
Verification
Remaining draft checks:
Focused server commands (from
apps/server):Checklist
Built with GPT-6 in the Codex harness.