No microphone input
- Check Rudr’s microphone permission in the OS’s privacy settings.
- Open Settings → Devices and choose an available Microphone.
- Replace Saved device (disconnected) with a connected device or System default.
- In an active voice session, check whether the microphone is muted.
- End and restart the intended voice or dictation flow after changing configuration.
A microphone that works in another application may still lack permission for Rudr. Do not repeatedly change API keys to fix a local permission issue.
Recording works but no useful text appears
For a dictated message, inspect Preferences → Dictation for the correct Chat or Code transcription provider/model. For a live conversation, inspect Preferences → Voice mode and the actual model selected on the setup pane.
These are independent defaults. Check the matching connection under Models and preserve any model or endpoint error. Correct text-chat credentials do not prove a transcription or realtime endpoint is available.
Replies are silent or interrupt unexpectedly
Check Devices → Speaker, OS output volume, and whether the requested speech was generated. For a finished answer’s speaker button, inspect Preferences → Read aloud; changing the live voice default does not repair that route.
For early interruptions or long pauses, review the active provider’s listening settings under How each provider listens. The controls differ by provider. End a stale or failed live session before starting another so you know which connection owns the audio.
Record OS, devices, selected voice/transcription/speech model, and sanitized error for a problem report. See audio settings and dictation/read aloud.