fix: avoid BLE reconnect race when Agent owns device - #49
Draft
sunflower-zzn wants to merge 1 commit into
Draft
Conversation
sunflower-zzn
force-pushed
the
codex/fix-agent-ble-ownership-race
branch
from
August 11, 2026 06:23
036a62b to
2f5d0b6
Compare
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
ahakeyconfig-agentowns the keyboardRoot cause
The App BLE manager remained capable of reconnecting after ownership had moved to the Agent. Its cached state could therefore show an old device name and repeated connection failures while the Agent already held the GATT connection.
Validation
swiftc -parsepassed for all changed Swift sources and the new focused testsgit diff --checkpassedswift testcould not run locally because the installed Command Line Tools compiler does not match the macOS SDK, and full Xcode is unavailable