Let other people talk to your ChatGPT dots. Let your ChatGPT dots hear your computer.
Two abilities, a wide range of uses:
| Ability | What it opens up |
|---|---|
| Shared conversations | Friends, collaborators and other callers can address your ChatGPT dots directly, ask their own questions and hear the replies—just as you can. |
| Computer-audio listening | Your ChatGPT dots can hear the audio from live videos, presentations, tutorials, music and other applications routed into their input. |
The idea is to make your dots part of what people are discussing and hearing. A business call, a shared work session or a live video can become a conversation with an AI participant. You do not have to relay every question or repeat everything playing on the computer.
Discord is the call application used in the tested setup below. It is an example of the shared-conversation use case, not the definition of the project. The published instructions currently cover Windows, Discord and Voicemeeter Banana; other call apps and voice clients need their own routing checks.
Set it up · Understand the routing · Test both abilities · Troubleshoot
I wanted two things: for other people to be able to talk directly to my ChatGPT dots, and for my ChatGPT dots to hear the audio on my computer. Those abilities are useful far beyond gaming—business discussions, collaboration, shared learning and listening to live videos are all reasons I wanted this working.
Other people should be able to use the dots conversationally, just as I can, without me acting as the middleman. And when something relevant is playing on the computer, the dots should be able to hear it as part of the discussion.
Voicemeeter Banana and VB-Audio cables provide the current mixing engine and virtual devices. This project's contribution is the reproducible routing guide, tested setup, diagram and troubleshooting. It is not an official OpenAI integration or a standalone mixer; a custom setup companion is not included.
- Someone else talks to your dots: have another caller ask a question while you stay quiet, then ask a follow-up and listen to the reply directly.
- Your dots hear computer audio: play a short video or live audio segment and ask about something audible in it.
- Combine them: discuss that audio together, with you, the other caller and the dots participating in the same conversation.
A combined-input test covered the host, a Discord caller and video audio on one Windows setup. Other applications, every live-video service and business-task accuracy are not established by that test. See what has actually been tested.
This routes audio, not video frames or screen vision. Shared conversation access does not define account access, private context or tool permissions; those remain governed by the host's dot configuration. Dot-to-dot voice communication is another exploration goal, not a validated agent-to-agent protocol in this guide.
- Talk to your dot while it also hears people in your Discord call.
- Let it hear videos, music and other apps using Windows default playback.
- Send the dot's spoken replies to your callers without sending those replies back into its own input.
- Keep listening locally through your audio interface or headphones.
This carries audio. It does not give the dot video frames or screen vision.
- Windows and a ChatGPT/dot voice interface that lets you select an audio input.
- Voicemeeter Banana.
- VB-CABLE and Hi-Fi Cable, providing two distinct cable pairs.
- Discord desktop and your existing microphone/headphones or audio interface.
Download drivers from VB-Audio. Installation can require administrator access and a restart. Banana and the cables are third-party donationware; review VB-Audio's licensing terms, including professional-use requirements. They are not open-source components of this repository.
The names B1 and B2 are important: B1 feeds the dot; B2 feeds Discord's microphone input.
| Banana source | Local headphones A1 | Dot B1 | Discord microphone B2 |
|---|---|---|---|
| Your microphone | Optional direct monitoring | On | On |
| Discord receive, through basic VB-CABLE | On | On | Off |
| Dot playback, through Hi-Fi Cable | On | Off | On in voice-sharing mode |
| Computer playback, through VAIO | On | On | On in voice-sharing mode |
flowchart LR
Mic[Your microphone] --> B1[Dot input: B1]
Mic --> B2[Discord input: B2]
Discord[Discord receive] --> Cable[Basic VB-CABLE]
Cable --> B1
Programs[Computer playback: VAIO] --> B1
Programs --> B2
Dot[Dot reply] --> HiFi[Hi-Fi Cable]
HiFi --> B2
Cable --> Local[Local listening: A1]
Programs --> Local
HiFi --> Local
- Record your existing Windows and application device choices so you can restore them. Start at modest levels.
- Choose your listening device as Banana A1. Choose your microphone on hardware input 1. Confirm the actual microphone channel before routing it.
- Choose CABLE Output on hardware input 2. This strip receives Discord, and must never feed B2.
- Choose Hi-Fi Cable Output on hardware input 3. This strip receives the dot, and must never feed B1.
- Apply the routing table above. Keep virtual buses stereo; do not turn the whole mix mono merely to fix a microphone channel.
- Set Discord output to Speakers (VB-Audio Virtual Cable) and Discord input to Voicemeeter Out B2.
- Set the dot's call microphone to Voicemeeter Out B1, and its playback to Hi-Fi Cable Input. Check the selector inside the call: Windows defaults alone may not override an explicit app selection.
- Set Windows default playback to Voicemeeter Input (VAIO) for ordinary computer apps. Keep Discord and the dot assigned to their separate outputs. Apps with an explicit device or ASIO driver can bypass the Windows default.
- Test the microphone, friend and program audio separately. Save the working Banana preset only after checking each path.
Banana must be running for its virtual default playback device to produce local sound. Keep an easy route back to your physical playback device if Banana is stopped.
When A1 uses your interface's ASIO driver, use Banana's ASIO input patch to select the microphone channel. Avoid opening the same interface simultaneously as both ASIO A1 and WDM/MME microphone input. Channel numbers depend on the interface: the tested Apollo Twin USB setup used analog input 2; do not assume input 2 is correct for your hardware. See VB-Audio's ASIO setup guide.
Voice-sharing mode: B2 includes your microphone, programs and the dot reply. Keep Discord stream sound off to avoid sending the same audio twice. This was the route used for the explicit improved-music-quality report.
Screen-stream test mode: B2 carries only your microphone; turn off every non-mic B2 send. Keep local A1 and dot B1 routes as shown. Use Discord's screen share with audio for the program/reply delivery. Friends must watch the stream to receive its sound. Restore the non-mic B2 sends when returning to voice-sharing mode.
Discord controls native screen-stream capture. Banana's bus switches do not select the stream's audio source or prove that Discord excludes its own receive audio. Check whole-screen behavior with your actual interface and Discord version. Stream capture may bypass Banana's program gain, so check stream loudness independently. See Discord's screen-sharing guide.
- Ask the dot to respond to you, then have a friend speak. Both should reach the dot.
- Play a short video and ask the dot about something audible in it.
- Have friends confirm that your voice and the dot's reply are both clear.
- Play music long enough to check for fading or distortion.
- Have a friend speak while you are quiet: they should not hear themselves returned.
- For stream mode, have a viewer mute the stream: only your microphone should remain. Unmute it: program/reply audio should appear once, without the friend's own voice returning.
One Windows setup using an Apollo Twin USB, Banana 2.1.3.0, the two cables and Discord was tested interactively. Friends confirmed microphone reception and substantially improved Chrome music quality. A combined-input test included the local speaker, a Discord friend and video audio; the dot responded to both speakers and repeated a sentence from the video. The operator subsequently reported that everything worked.
That is evidence for this setup, not a compatibility guarantee. Sustained stream quality, return balance and absence of echo should each be checked on every new setup. Protected media, apps bypassing Windows playback, other ChatGPT clients and different audio interfaces are not established by that test.
| Symptom | Check |
|---|---|
| Dot hears friends but not you | Its call microphone must be B1, not CABLE Output. |
| Friends hear themselves | Discord receive strip must not feed B2; also test stream capture separately. |
| Dot hears itself | Dot playback must not feed B1 or the general shared-program device. |
| Friends hear no music | Check the selected delivery mode: B2 for voice sharing, stream audio for streaming. |
| You hear no computer sound | Banana must be running; A1 and the program strip must be enabled and point to your headphones/interface. |
| Quiet dot reply | Check the dot's actual output device, app volume and its dedicated Banana strip; avoid raising every source together. |
| Banana opens but Apollo A1 stays blank | Match Banana's 32/64-bit build to the installed ASIO driver; the tested Apollo USB setup required Banana 64-bit. |
| Duplicate music/reply | Check whether both B2 and the screen stream are carrying it. |
This first publication is a guide. A polished setup/control companion is planned, not included. No custom mixer executable, installer, private device preset, session log, credential or vendor binary is included. No project license has been selected yet; third-party products retain their own terms.
Independent, unofficial community project. No affiliation with or endorsement by OpenAI, Discord or VB-Audio is implied.
If this helped, star the repository so you can find it again. To report a problem or add a confirmed setup, open an issue with your Windows version, audio interface, sharing mode and which test failed. Share reproducible steps rather than personal device logs or credentials.