fix: auto-clean leftover legacy launch agent#20
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
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.
Summary\n- detect a leftover legacy LaunchAgent at app startup\n- automatically boot out and remove the stale plist when found\n- show a user-visible status message when cleanup succeeds or fails\n\n## Why\nA leftover LaunchAgent could cause ProcessBarMonitor to start at login even when the current launch-at-login toggle was off, and in some cases cause duplicate startup.\n\n## Validation\n- swift build\n- ./install_app.sh 1.0.5-local 1 --configuration release\n- manually recreated ~/Library/LaunchAgents/ai.openclaw.ProcessBarMonitor.plist\n- launched the app and verified the legacy plist was auto-removed