Open
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
[5/7] windows merge-in
What
Merge the Windows implementation into the mainline package on top of the new runtime boundary.
vibemouse/platform/system_integration.pyfor Win32 active-window, text-input, workspace, and cursor integrationvibemouse/listener/keyboard_listener.pyfor the Windows listener pathvibemouse/ops/deploy.pyandvibemouse/ops/doctor.pyfor Windows deploy and health-check flowsvibemouse/config/schema.pyfor Windows-facing config surface updatestests/platform/test_system_integration.py,tests/listener/test_keyboard_listener.py,tests/ops/test_deploy.py,tests/ops/test_doctor.py, and related runtime testsWhy
Windows support should land on top of the reviewed config, bindings, and IPC boundaries so platform behavior can be reviewed separately from protocol/runtime changes and without keeping a fork-only implementation path.
Stack
[1/7]-[4/7] config / files / bindings / ipc runtime
-> [5/7] windows merge-in <- you are here
-> [6/7] macos port
-> [7/7] panel tests ci