Quick checks
Confirm Clack is on, the volume is up, a sound pack is selected, and Windows is sending audio to the right device.
Support
Get Clack feeling right again.
Start with the tray toggle, selected sound pack, Windows output device, and visualizer settings. Most Clack issues can be solved without reinstalling.
Privacy baseline
Clack uses physical key and mouse button identifiers. It does not read or transmit the contents of what you type.
Common fixes
Practical checks for the Windows app.
Open Clack from the Windows system tray and make sure the main toggle is on. Confirm the volume slider is above 0%, choose a sound pack, and check that Windows is using the output device you expect.
Open the Windows notification area overflow and pin Clack if you want it visible. Relaunching Clack will also bring it back quietly into the tray.
Use a local output device first to rule out Bluetooth latency. Clack plays sounds on a background audio queue and ignores held-key repeats, so one stuck key should not flood playback.
Turn on Mouse Clicks in the tray flyout or Settings. Pick a click tier (softest, soft, medium, or hard) and use Preview to hear it before you keep typing.
Enable Reactive Visualizer, then choose cursor-follow, top-center, or pinned. If you work across monitors, try top-center once to confirm it is appearing on the active display.
External packs belong in %LocalAppData%\Clack\Packs, one folder per pack. Reopen Settings after adding a pack so Clack reloads the catalog.
Still stuck? Write to me.
Email with your Windows version, audio device, selected sound pack, and what changed before the issue started. A real person replies.