Normal: the AI replies only to you
The AI can hear the meeting, but its reply stays on your normal Mac output. AI audio to the meeting remains OFF.
Connect a meeting app and a voice AI on macOS
Let AI hear the meeting.Keep its reply private, or share one.
Viyv Meeting Bridge is an audio router that connects meeting apps such as Zoom with voice AI clients such as ChatGPT Voice or Codex on your Mac. It is not an AI, recorder, or transcription service.
The free v1 opens after signing, notarization, and real-meeting E2E are complete.
- AI audio starts OFF
- No meeting bot
- No recording
- macOS 14.2+
Meeting app audioZoom / Meet / Teams
Microphone selected by the AIViyv Meeting Mic
Voice AI supplied by youChatGPT Voice / CodexLISTENING
Microphone selected by the meetingViyv Meeting Send
AI audio to meeting OFFNormally, the AI reply stays on your Mac output and is not sent to other participants.
CONCRETE EXAMPLE
For example, let ChatGPT hear a question from Zoom
Meeting Bridge does not join calls for you. You join the meeting and open a voice AI normally; the app only connects their audio on your Mac.
What you need
- A Mac on macOS 14.2+
- A meeting app
- A voice AI app
- Headphones
- Participant and organization permission
- 01
Open the meeting and voice AI
Join Zoom or another meeting normally, then open the voice AI you want to use.
- 02
Choose both apps in Bridge
Choose the meeting under audio for AI, and the voice AI under AI for the meeting.
- 03
Assign two microphone inputs
Use Viyv Meeting Mic in the AI and Viyv Meeting Send in the meeting app.
- 04
Confirm permission and start
Confirm the meeting audio may be shared with the AI, then start. AI audio to the meeting begins OFF.
- 05
Share only the next reply
Normally, hear the AI privately. Press Share next AI reply only when a reply should reach the meeting.
- 06
Stop and restore
At the end, Stop closes AI audio, removes temporary routes, and restores any input Bridge changed.
Share: send one reply
Arm the next reply. The gate opens only when AI audio begins and closes after silence or the maximum duration.
THE ACTUAL APP
See listening, speaking, consent, and on-air state in one window
You operate the real app, not an abstract patch bay. Meeting capture and AI audio to participants are shown as separate states.
1 · LISTEN
Audio the AI hears
Choose one meeting app or system audio.
2 · TALK
AI that may speak
Limit meeting output to one selected AI app.
3 · CONSENT
Confirm every meeting
Capture cannot begin until permission is confirmed.
4 · ONE SHOT
Share the next reply only
Wait for AI audio, then close after silence or the time limit.
WHAT YOU CAN DO
Use AI when useful, without adding a meeting bot
PRIVATE COPILOT
Review an answer privately
Let a voice AI hear the question, listen to its suggestion in headphones, and decide for yourself whether to use it.
ONE REPLY
Share one AI reply
Send one explanation, translation, or demo reply, then return to OFF automatically.
MIC CONTROL
Control your mic and AI separately
Switch among you only, AI only, both, and all muted without rebuilding the route.
SAFE BY DEFAULT
Hearing the meeting and speaking to it are separate actions
Launching the app, capturing meeting audio, and sending AI audio to participants are three distinct states.
CONSENT REQUIRED
Confirm every meeting
Neither GUI nor MCP can start meeting capture until participant and organization permission is confirmed.
AI OFF
AI audio starts OFF
Starting the listening route never sends an AI reply to other participants automatically.
AUTO-OFF
One reply, then automatic OFF
Bounded start wait, silence, and maximum duration keep a reply from remaining on air.
KILL
Stop AI audio immediately
Close only the AI path while keeping your physical microphone route intact.
COMPATIBILITY STATUS
We do not promise compatibility by assumption
These are the current pre-release states. A combination becomes Verified only after a real-counterparty E2E passes.
| macOS 14.2 or later | Required | Uses Core Audio process taps |
|---|---|---|
| Zoom | Real-meeting E2E pending | A release gate; not currently marked supported |
| Google Meet / Chrome | Real-meeting E2E pending | Other tabs in the same browser process may be included |
| Microsoft Teams | Real-meeting E2E pending | Real send and receive validation is required |
| ChatGPT Voice / Codex | Combination testing | Input selection and reply capture must pass before release |
TWO CONTROL MODES
The standard GUI, plus local MCP
MCP is not required for normal use. Use the local stdio control surface only when you want agent automation.
GUI · DEFAULT
Operate safely in the app
Confirm permission, start, share only the next AI reply, kill AI audio, and Stop from the window. Continuous transmission lives in an advanced menu.
LOCAL MCP · ADVANCED
Expose the same safety controls to an agent
Inspect state, prepare listen-only, start, speak once, kill, stop, and restore over stdio.
stdio://localhostLOCAL
- No HTTP listener, LAN port, or cloud MCP
- No audio samples or transcripts in MCP
- Separate scopes for one-shot and continuous audio
- EOF, cancellation, and exit close AI audio
PRIVACY BOUNDARY
Separate the local route from the AI service you choose
ON YOUR MAC
What Meeting Bridge does on your Mac
- Realtime Core Audio routing
- Temporary taps and aggregate devices
- Short in-memory audio buffers
- No recording, transcription, database, or account
AI SERVICE BOUNDARY
What belongs to the selected AI app
- The AI app may send audio to an external service
- Storage, training, and retention follow the AI provider's settings and terms
- Local routing does not mean the AI itself runs locally
- Follow organizational policy for confidential meetings
BEFORE YOU START
What to know before installation
DRIVER
One administrator approval
Installs two user-space AudioServerPlugIns. No kernel extension is used.
PERMISSIONS
Audio capture and microphone access
macOS permission is required for selected app audio and an optional physical microphone.
HEADPHONES
Headphones recommended
Speakers can let AI audio leak back through the physical microphone.
TWO INPUTS
Two virtual microphones
The AI selects Viyv Meeting Mic; the meeting selects Viyv Meeting Send.
What Meeting Bridge does not provide
- Automatic meeting join or UI control
- An AI model or answer generation
- Recording, transcription, summaries, TTS, or STT
- Automatic participant or speaker identification
- Unattended always-on AI audio
- Control over an AI provider's data retention
FIRST SETUP
First-time setup after release
- 01
Get the notarized DMG
We publish only after Developer ID signing, notarization, stapling, and fresh-Mac Gatekeeper checks.
- 02
Install the app and two drivers
Move the app to Applications and approve the user-space audio drivers once.
- 03
Choose the meeting and AI
Follow the app guidance to select both sources and assign the two virtual microphones.
- 04
Confirm each meeting and start
Start with AI audio OFF. At the end, Stop removes temporary routes and restores input settings.
This is still in pre-release validation. We do not distribute unsigned builds or Gatekeeper bypass instructions.
FAQ
What you need to know first
Does Meeting Bridge include an AI?
No. It is an audio router between your meeting app and a separate voice AI app. It does not generate answers, transcribe, summarize, perform TTS, or perform STT.
What do other participants hear?
Normally, only your physical microphone. After you arm Share next AI reply only, one AI reply is sent and the path returns to OFF after silence or the time limit.
Can I use one-shot from the GUI?
Yes. The main GUI can share the next AI reply only. MCP is optional automation. Continuous transmission is separated into an advanced menu and requires manual stop.
Does it join meetings as a bot?
No. It does not handle invitations, joining, or meeting UI. You join normally and select microphone inputs.
Does all audio stay on the Mac?
Bridge routing, buffering, and control stay on the Mac. The selected AI app may send audio to an external service, subject to that provider's settings and terms.
Does it work with Zoom, Meet, Teams, and ChatGPT?
They are intended scenarios, but real-counterparty E2E is still a pre-release gate. Verified combinations will be listed at release.
What should I know about Google Meet in Chrome?
Capture follows the process macOS exposes. Other tabs in the same Chrome process may be included, so a meeting-only browser context is recommended.
Why is there no download yet?
The download remains fail-closed until Developer ID signing, notarization, fresh-Mac Gatekeeper, driver install/update/uninstall, and real Zoom/Meet/Teams E2E all pass.
FREE v1 · PREPARING
The workflow and safety boundary are public before the binary is.
The free v1 opens after signing, notarization, and real-meeting validation. Until then, you can review the exact operation and release gates.
No waitlist form, account signup, or unsigned DMG.