Vibecom
Support
Set up your intercom, troubleshoot audio, and send useful tester feedback.
Testing Vibecom?
You need an invited build and access to a Vibecom Server. Your test coordinator supplies the invitation and connection details. There is no public download link on this page yet.
Get connected
One Mac hosts the intercom for your team. Vibecom Server is built into the macOS app. Start hosting on that Mac before connecting your other devices. If someone else is hosting, ask them for the room name and password and skip to joining their network.
Install your invited build.
On iPhone or iPad, accept the invitation in Apple's TestFlight app. Your test coordinator supplies the Mac app. Server hosting is built into that app.
Start hosting on a Mac.
Follow Start the server in the Mac app below. Keep Vibecom running on that Mac while your team uses the intercom.
Join the server's network.
Use the same trusted local network as the server. Connect the server Mac by Ethernet if you can.
Allow permissions.
Allow Microphone and Local Network access when prompted. You can change them later in your device's Settings.
Connect to the room.
Select the discovered server, or enter the address and ports supplied by its operator. Enter your display name and the room password.
Check audio before the session.
Select the intended audio route and channel. Test push-to-talk in both directions with another participant. Start at a comfortable listening volume.
No Vibecom account is required. The room password comes from your server operator.
Start the server in the Mac app
Open Vibecom on the host Mac.
In the Connect screen, select Begin Hosting beside Discovered servers. This opens the Server window. You can also open it with the network-shaped Server button in the main app window.
Set up the room.
In the Server window, open Settings and select Edit. Set the Workspace name and Workspace password. Choose a password for your team instead of leaving the default. Select Save Changes.
Start the server.
Open Overview and select Start Hosting. Opening the Server window alone does not start it. When hosting starts, the button changes to Stop Hosting.
Connect the other devices.
On each device, open Vibecom, choose the room from Discovered servers, and enter the room password. Keep the host Mac awake, connected to the network, and running Vibecom.
To end the session, return to the Server window and select Stop Hosting. This stops the intercom for everyone connected to that server.
Connection and audio help
The server does not appear
On the host Mac, open Vibecom's Server window and confirm that Overview shows Stop Hosting. If it shows Start Hosting, select that first. Then confirm both devices are on the same network. Guest Wi-Fi or client isolation can prevent devices from reaching one another. Check Local Network permission. Ask the operator for the server address if discovery is unavailable.
I can see the server but cannot connect
Check the room password, address, and ports with the operator. The server and clients must use compatible builds. If you see a server trust or certificate warning, verify it with the operator before changing trust settings.
I cannot hear someone, or they cannot hear me
Confirm both participants are connected and listening on the intended channel. Check microphone permission, mute state, selected input and output devices, and output volume. Test with built-in audio or a wired headset to isolate a Bluetooth route problem.
Audio breaks up or arrives late
Use a stable network and connect the server Mac by Ethernet where possible. Avoid AirDrop transfers during an intercom session. AirDrop and other nearby-device activity can interrupt Wi-Fi audio delivery. Note whether reconnecting or changing audio route restores normal audio.
Can I connect over the internet?
Vibecom is designed for trusted local networks. It does not set up internet routing or NAT traversal for you. Remote use needs a network setup that your operator manages. Do not expose the server directly to an untrusted network.
Current tester notes
The September 26 beta review records Mac audio ducking issues and intermittent AirPods route switching. Test your intended headset before a session, and keep a wired or built-in audio option available. Report which route was active and whether changing it restored audio.
These builds are for limited testing. Keep another way to communicate for critical cues. Vibecom is not an emergency calling service.
Report a problem
On iPhone or iPad, you can send beta feedback from the Vibecom entry in TestFlight. For direct support, use the contact section below. Include:
- App version and build, device model, and operating-system version.
- The microphone, headset, speaker, or Bluetooth device in use.
- What you were doing, what you expected, and what happened.
- The approximate time of the problem, your time zone, and whether it recovered.
- Whether the device and server used Wi-Fi or Ethernet.
Do not send the room password. Remove unrelated personal information from screenshots and logs.
Export logs after a problem
- Open Vibecom's Settings soon after the problem occurs.
- Select Export Logs. On iPhone or iPad, use the share sheet to save or share the file. On Mac, choose a location to save it.
- Review the file before sending it. Logs can contain participant names, device details, and network information.
- Attach the file to your report when requested. Include the incident time so the developer can find the relevant entries.
The export contains recent in-memory events. Export soon after the incident and before quitting the app.
Optional server diagnostics
Send diagnostic snapshots to server is off by default. Enable it only when your server operator asks you to help investigate a problem on a trusted network. It enables automatic capture and upload to the connected server, not a support inbox. Turn it off when the test is finished.
Reports already uploaded remain with the server operator. See the privacy policy for report contents and transport limitations.
Contact Vibecom
Email support@vibecom.dev for help with Vibecom or a privacy request.
Invited testers can use TestFlight feedback or the contact supplied with their invitation. For a room password, server access, or deletion of server reports, contact your server operator.