[BUG] Transcription doesn't get captured unless handy gets restarted

[mjaffer2]

Before You Submit

Bug Description

After an extended idle period (~hours), Handy's event loop gets stuck. The tao event loop emits repeated NewEvents emitted without explicit RedrawEventsCleared warnings, and Ctrl+Space stops being captured entirely — no handy-keys event entries appear in
the log. The app remains running (process alive, tray icon may still show) but is completely unresponsive to the hotkey. Only a full
process kill + restart resolves the issue.

Observed timeline:

• Last successful transcription: 2026-03-30 18:47:36
• First tao event loop warning: 2026-03-30 18:47:43 (7 seconds later)
• Hotkey remained dead for ~29 hours until manual restart
• After restart, hotkey immediately worked again

This has occurred multiple times on the same machine.

System Information

App Version: 0.8.1

Operating System: Windows 11 Enterprise 10.0.26200

CPU: AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics

GPU: AMD Radeon™ 780M; NVIDIA RTX 2000 Ada Generation Laptop GPU

Logs

Last successful activity before freeze:

[2026-03-30][18:47:36][handy_app_lib::shortcut::handy_keys][DEBUG] handy-keys event: binding=transcribe, hotkey=ctrl+space,
state=Pressed [2026-03-30][18:47:36][handy_app_lib::managers::transcription][INFO] Transcription completed in 286ms

Freeze begins — tao warnings, no more hotkey events:

[2026-03-30][18:47:43][tao::platform_impl::platform::event_loop::runner][WARN] NewEvents emitted without explicit RedrawEventsCleared
... [2026-03-31][23:30:44][tao::platform_impl::platform::event_loop::runner][WARN] NewEvents emitted without explicit
RedrawEventsCleared

After manual restart — immediately healthy:

[2026-03-31][23:37:21][handy_app_lib::managers::audio][DEBUG] Recording started for binding transcribe
[2026-03-31][23:37:26][handy_app_lib::shortcut::handy_keys][DEBUG] handy-keys event: binding=transcribe, hotkey=ctrl+space,
state=Pressed [2026-03-31][23:37:26][handy_app_lib::managers::transcription][INFO] Transcription completed in 204ms

[mjaffer2]

It seems like this could only be happening after my laptop is locked and then unlocked.