Troubleshoot voice input and replies

Voice input and spoken output use different paths. Start by asking whether Nock recognized the request, whether an answer appeared, and whether that answer was audible. A text answer with no sound is different from a request that never reached the agent.

Test each part separately

1. Type a short question in Nock’s chat. If it answers, the agent path is working for that request.
2. Make a short recording and check the transcript. This tests input and recognition.
3. Open Settings → Agent → Agent voice and play a voice preview. This tests spoken playback.

These small checks avoid repeating a long task while the failing component remains unknown. Do not interpret a successful voice preview as proof that the agent completed work.

No recognized speech

If the notch does not react, check shortcuts and keyboard permissions. If recording starts, inspect the Mac’s input device and Microphone grant, including Nock Speech where shown. Speech Recognition permission applies to Apple’s fallback.

The menu-bar status can distinguish a missing grant from a helper that is down or temporarily paused. Speech is still starting and Transcription is not connected yet ask you to wait for initialization. Already listening means another recording is active; finish or cancel it first.

When the speech helper repeatedly crashes, Nock spaces out restart attempts and displays a retry message. Typing can remain usable while speech recovers. Restarting the keyboard listener will not restart this separate speech service. If the state persists, quit Nock normally, reopen it, and check the permission status before another test.

An answer appears, but Nock is silent

Enable Agent voice and try Normal speed. Check the Mac’s output device and mute state. Review account or provider access if the voice picker cannot play a sample; the current voice service requires supported credentials/access and an available connection.

If media lowering left the output quiet, restore the system volume manually. Another recording can lower the already-low level again, so it is not a useful recovery step. See sound and media.

The reply stops or says less than the screen

Starting a new voice recording or request interrupts current speech. The stop control deliberately silences playback and can stop work still in progress. Check whether a shortcut is being pressed accidentally.

Nock generally speaks a short response while showing the detail on screen. It does not read every code block, path, or long result aloud. Read the visible response before assuming that a short spoken answer means the rest is missing.

Useful support information

Share the app version, input/output devices, whether typed chat worked, whether transcripts appeared, and whether a voice preview played. Include the visible error without secrets or private recording content. If the problem follows one voice or speed, name that choice and try another preset as a comparison.