Repository navigation
VibeController v1.1.0 - #1
Merged
Merged
Conversation
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
Why
VibeController v1.0 supported Xbox and DualSense input, but DualSense pointer movement could feel uneven and the app could not expose microphone availability or Codex task state through the controller lightbar. The first Hook implementation also used CMD-style quoting that failed when Codex Desktop executed it through PowerShell, and some Desktop sessions omit the
Stoplifecycle event.User impact
Validation
powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\test.ps1powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\package-release.ps1 -Version 1.1.0powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\smoke-test-release.ps1 -Version 1.1.005E6E8AA337CBB5D094C9177AE2500E25B0DC515F528017C860A3C0E7093F504