feat(macos): support VirtualHIDDevice v8 - #2123
Merged
Merged
Conversation
This was referenced Jul 27, 2026
jtroo
approved these changes
Jul 28, 2026
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
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.
Summary
karabiner-driverkitfrom 0.3.x to 0.4.0Why
Karabiner-Elements 16.1 uses VirtualHIDDevice v8. Kanata currently depends on the protocol-5 driverkit client and documents VirtualHIDDevice v6.2.0, so it cannot communicate with the current v8 daemon.
karabiner-driverkit0.4.0 adds the protocol-7/v8 client support. This intentionally updates Kanata to v8 rather than maintaining two IPC implementations. Users of the standalone v6.2.0 driver must upgrade the driver and Kanata together.Closes #2105.
Runtime validation
The driverkit migration was validated in a disposable macOS 15.7.7 ARM VM during psych3r/driverkit#20. The validated scenarios included:
The controlled v6/v8 comparison found the same same-device exclusive-input behavior in both versions; it was not introduced by the v8 migration.
Local checks
cargo fmt --all --checkRUSTFLAGS="-Dwarnings" cargo build --all-targetsRUSTFLAGS="-Dwarnings" cargo test --allRUSTFLAGS="-Dwarnings" cargo clippy --all -- -D warningsRUSTFLAGS="-Dwarnings" cargo test --all --features=cmdRUSTFLAGS="-Dwarnings" cargo clippy --all --features=cmd -- -D warningsRUSTFLAGS="-Dwarnings" cargo build --releaseRUSTFLAGS="-Dwarnings" cargo build --release --features=cmd