Current Behavior
When Wave is running on my second monitor, switching focus from Wave to any other application (browser, editor, Notepad, etc.) often leaves my keyboard completely unresponsive in that other app for about 10–15 seconds:
I frequently cannot type anything at all in the target app immediately after leaving Wave.
In many cases, no keys register.
After roughly 15 seconds, or after clicking around/alt‑tabbing a bit, keyboard input starts working again.
Completely quitting Wave instantly restores normal keyboard behavior across all applications; the problem does not occur when Wave is not running.
Expected Behavior
When Wave is open but not the active/focused window, it should not affect keyboard input in other applications at all.
Switching focus from Wave to any other app should allow immediate, normal typing with no delay or loss of input.
Steps To Reproduce
- Launch Wave.
- Monitor setup: Wave on the second monitor (it is the only visible window on that monitor).
Open another application (e.g. browser, code editor, Notepad) on the primary monitor.
- In Wave, interact normally for a bit.
- Switch focus from Wave to the other app then try typing in the other app.
Observed:
For roughly the next 15 seconds:
No keys register at all in the target app.
Sometimes after waiting 15 seconds, or after changing focus, typing begins to work normally again.
If you now quit Wave and repeat the same test, keyboard input in the other app works immediately and reliably with no blocking.
Wave Version
0.14.5 (202604161539)
Platform
Windows
OS Version/Distribution
Microsoft Windows 11 IoT Enterprise LTSC (64‑bit)
Architecture
x64
Anything else?
Display setup: Dual‑monitor
Wave is always open on the second monitor.
Main work apps (browser, editors, etc.) are on the primary monitor.
Wave usage pattern:
Typically have at least:
One local CLI terminal widget open (git bash).
One file/preview widget open for a project directory.
Sometimes one Wave AI window.
Wave Settings UI:
No visible sections for “Hotkeys”, “Shortcuts”, or “Keyboard”.
No obvious way to configure or disable global keybindings.
On‑disk config (high level):
The Preferences file under the Wave data directory only contains basic settings (e.g. spellcheck) and no apparent keybinding/shortcut configuration.
The issue affects all apps I’ve tried (browser, editors, Notepad, etc.), not a specific program.
The behavior is tightly correlated with Wave’s process:
As long as Wave is running, I can reproduce the blocking nearly every time I switch from Wave to another app.
As soon as I exit Wave, the problem disappears entirely.
This suggests Wave is installing a low‑level system‑wide keyboard hook and either:
Continuing to intercept keystrokes for several seconds after its window loses focus, or
Encountering an error/deadlock that temporarily swallows input events before releasing them.
Impact
My main workflow is to keep Wave on the second monitor and rapidly switch between Wave and other applications.
The recurring 15 second window where my keyboard is unusable every time I leave Wave makes this workflow extremely disruptive.
For now, the only reliable workaround is to completely close Wave whenever I need to type in other apps, which defeats the purpose of using Wave as a side tool.
Current Behavior
When Wave is running on my second monitor, switching focus from Wave to any other application (browser, editor, Notepad, etc.) often leaves my keyboard completely unresponsive in that other app for about 10–15 seconds:
I frequently cannot type anything at all in the target app immediately after leaving Wave.
In many cases, no keys register.
After roughly 15 seconds, or after clicking around/alt‑tabbing a bit, keyboard input starts working again.
Completely quitting Wave instantly restores normal keyboard behavior across all applications; the problem does not occur when Wave is not running.
Expected Behavior
When Wave is open but not the active/focused window, it should not affect keyboard input in other applications at all.
Switching focus from Wave to any other app should allow immediate, normal typing with no delay or loss of input.
Steps To Reproduce
Open another application (e.g. browser, code editor, Notepad) on the primary monitor.
Observed:
For roughly the next 15 seconds:
No keys register at all in the target app.
Sometimes after waiting 15 seconds, or after changing focus, typing begins to work normally again.
If you now quit Wave and repeat the same test, keyboard input in the other app works immediately and reliably with no blocking.
Wave Version
0.14.5 (202604161539)
Platform
Windows
OS Version/Distribution
Microsoft Windows 11 IoT Enterprise LTSC (64‑bit)
Architecture
x64
Anything else?
Display setup: Dual‑monitor
Wave is always open on the second monitor.
Main work apps (browser, editors, etc.) are on the primary monitor.
Wave usage pattern:
Typically have at least:
One local CLI terminal widget open (git bash).
One file/preview widget open for a project directory.
Sometimes one Wave AI window.
Wave Settings UI:
No visible sections for “Hotkeys”, “Shortcuts”, or “Keyboard”.
No obvious way to configure or disable global keybindings.
On‑disk config (high level):
The Preferences file under the Wave data directory only contains basic settings (e.g. spellcheck) and no apparent keybinding/shortcut configuration.
The issue affects all apps I’ve tried (browser, editors, Notepad, etc.), not a specific program.
The behavior is tightly correlated with Wave’s process:
As long as Wave is running, I can reproduce the blocking nearly every time I switch from Wave to another app.
As soon as I exit Wave, the problem disappears entirely.
This suggests Wave is installing a low‑level system‑wide keyboard hook and either:
Continuing to intercept keystrokes for several seconds after its window loses focus, or
Encountering an error/deadlock that temporarily swallows input events before releasing them.
Impact
My main workflow is to keep Wave on the second monitor and rapidly switch between Wave and other applications.
The recurring 15 second window where my keyboard is unusable every time I leave Wave makes this workflow extremely disruptive.
For now, the only reliable workaround is to completely close Wave whenever I need to type in other apps, which defeats the purpose of using Wave as a side tool.