Troubleshooting

Fix common issues with audio, suggestions, and connectivity.

Audio Microphone not picking up sound

  1. Check that your browser has microphone permission. Click the lock icon in the address bar and ensure the mic is set to "Allow."
  2. Verify your system's default microphone is correct in your OS sound settings.
  3. Make sure no other application is using the microphone exclusively (close other video call apps).
  4. In Cuebird, click the microphone button to toggle capture off and on again.
  5. Try a different browser — Chrome and Edge have the best microphone support.

Audio System audio capture shows "No audio" or silence

  1. System audio capture only works in Chromium-based browsers (Chrome, Edge, Brave). Firefox and Safari do not support it.
  2. When sharing, make sure you select the "Chrome Tab" or "System Audio" option — not "Entire Screen."
  3. Check that the tab you're capturing is actually playing audio. Muted tabs produce silence.
  4. On Windows, system audio capture may require the "Stereo Mix" input to be enabled in Sound settings.
  5. On macOS, install a virtual audio driver like BlackHole or Loopback for system audio routing.

Suggestions Suggestions not appearing

  1. Verify that suggestions are enabled — check the toggle in the interview page settings panel.
  2. Make sure audio is actually being transcribed. Look for the live transcript text appearing in the feed.
  3. If the transcript is updating but no suggestions appear, the AI may have hit a rate limit. Wait 10 seconds and try again.
  4. Check that your OpenAI API key is valid and has sufficient credits. You can verify this on the Provider Usage page in the admin dashboard.
  5. Click the "Suggest" button to manually trigger a suggestion from the current transcript.

Suggestions AI responses are slow or timing out

  1. The default model is GPT-4o-mini, which responds in ~1-2 seconds. If it's slower, OpenAI may be experiencing high demand.
  2. Check your internet connection — the AI response streams over a WebSocket. A slow connection will delay delivery.
  3. If suggestions consistently take >5 seconds, try switching to a faster model in settings.
  4. Too many concurrent sessions on the same API key can cause throttling. Check your OpenAI rate limits.

Connection "Authentication required" or session disconnects

  1. Your session token may have expired. Refresh the page to get a new token.
  2. If you're on the free plan, you may have reached the 3-session monthly limit. Upgrade to Pro for unlimited sessions.
  3. Check that your browser isn't blocking WebSocket connections. Some corporate firewalls block WSS traffic.
  4. Try connecting from a different network (e.g., switch from VPN to direct connection).

Connection "Invalid frame header" or WebSocket errors

  1. This is a known issue when connecting through certain proxies. In development, connect directly to the Flask port (3001) instead of through the Vite proxy (5173).
  2. In production, this should not occur. If it does, clear your browser cache and reload.
  3. If using a corporate VPN, try disconnecting and reconnecting.