Troubleshooting
Find the right checks for dictation, slow responses, coding chats, Team messages, and cloud work.
First identify which stage failed: the shortcut, recognition, AI response, tool action, or delivery of the result. Read the visible status before restarting or retrying. A completed recognition and a completed task are different events.
Choose the symptom
Section titled “Choose the symptom”| What you see | First check | Guide |
|---|---|---|
| A hold does nothing | Selected shortcut, microphone, and system permissions. | Dictation troubleshooting |
| Nock hears nothing | The microphone meter and selected input device. | Microphone |
| A local model cannot run | Download status, language, operating-system support, and local-only choice. | Local dictation |
| Words appear but do not land in the app | Focus the text field, then use Paste last transcript if needed. | Paste last |
| A Nock panel or window stops responding | Wait briefly for its automatic reload; use Restart Nock if it keeps freezing. | Recovery steps below |
| Text answers arrive without speech | Output device, voice preparation, mute, and speech-output route. | Voice troubleshooting |
| A screen question lacks its image | The attached thumbnail, circle setting, and Mac Screen Recording permission. | Screen troubleshooting |
| Coding chat opens but a message was not sent | Whether it is an external app chat, a saved chat, or waiting for a move/approval. | Coding troubleshooting |
| A teammate message waits | The inbox item, selected destination, and that chat’s automatic-delivery setting. | Shared chats |
| A cloud bot or connected app refuses a request | Connection, plan access, selected account, and the relevant usage meter. | Connection troubleshooting |
The first answer is slow
Section titled “The first answer is slow”At startup, Nock prepares its speech and agent connections. A local model may still be downloading or loading; a provider may need to connect or refresh sign-in. Wait for the readiness or preparation message, then try a short question.
If the transcript appears but no reply follows, check whether Nock is reconnecting and whether the configured AI connection is ready. A missing model, an expired sign-in, and a usage limit need different fixes. Providers and Usage troubleshooting show the relevant controls.
The editor or project work feels slow
Section titled “The editor or project work feels slow”Check the active project folder first. A stale copy, a duplicate project root, or a different checkout can make search results look wrong and cause unnecessary indexing work. Run a simple search for a file you know belongs to the active project and inspect its location.
Then check running Tasks and coding chats. Stop work you no longer need rather than repeatedly starting the same job. Code intelligence explains indexing and language tools; Continue a task explains recovery after interruption.
Nock seems to have disappeared
Section titled “Nock seems to have disappeared”On Mac, look for the menu-bar icon and check the primary display. On Windows, look for Nock’s tray entry and top bar. Hide top notch and the side-panel visibility controls can hide the resting surfaces while keeping shortcuts available.
Open Settings from the app menu, check visibility and Game mode, and use Keyboard shortcuts if the hold itself is not detected.
A Nock panel or window is frozen
Section titled “A Nock panel or window is frozen”When the operating system reports that a Nock window is not responding, its clicks pass through to the app underneath. If it has not recovered after about eight seconds, Nock reloads that window; your other windows, chats, voice, and running agent work continue. If the same window reloads twice within two minutes and freezes again, Nock offers to restart.
To restart Nock yourself, choose Restart Nock from the menu:
- Mac: click the menu-bar droplet, or right-click the Dock icon (Control-click also works), then choose Restart Nock.
- Windows: right-click Nock’s tray droplet by the clock; it may be under the ^ hidden-icons menu.
Restart closes Nock’s windows and local agent engine, then opens Nock again. Your chats, settings, and sign-in are kept; the helper that holds coding-agent chats continues running. If an update has already downloaded, restarting also installs it. If Nock’s own menus do not respond, force-quit and reopen it instead. See Permissions for access problems and Continue a task if work was interrupted.
Sign-in or payment does not reach the app
Section titled “Sign-in or payment does not reach the app”Start a fresh sign-in inside Nock, keep it open, and check that browser and desktop use the same account. If checkout completed, refresh Usage before starting another purchase. Use Sign-in troubleshooting or Billing.
An action may have completed
Section titled “An action may have completed”Inspect the destination before repeating a send, post, or other external change. A missing confirmation is different from a confirmed failure. Read the task’s result and ask Nock about that task instead of immediately starting a duplicate.
Send a useful report
Section titled “Send a useful report”Open Settings → About → Report a problem, or ask Nock to prepare a report. Include the version, operating system, steps, expected result, exact message, and approximate time. Review the report and optional diagnostics before sending. Feedback and reports explains each sharing choice.