fix(pulse): create ~/Library/LaunchAgents before writing launchd plist#1310
fix(pulse): create ~/Library/LaunchAgents before writing launchd plist#1310stevetr68 wants to merge 1 commit into
Conversation
|
Hey @stevetr68, thanks for raising this, and sorry it sat for a while. We're changing how LifeOS ships. Instead of cloning a full That's aimed right at what you hit here. The old "one directory, one layout, hope it matches your setup" approach is exactly what broke for so many people, and the new model should handle it far better because your AI does the integration per machine instead of us guessing. So we're closing this in prep for that release. If it still bites you once the skill-based version is out, reopen or file a fresh one and we'll jump on it. Appreciate you taking the time. |
Problem
PULSE/manage.sh installwrites the launchd plist to$HOME/Library/LaunchAgents/:…but the
install)case only createsstate/andlogs/:On a fresh macOS user account,
~/Library/LaunchAgents/does not exist until somethingcreates it. When it's missing, the
> "$PLIST_DST"redirect fails withNo such file or directory, the install aborts, and the user sees a confusingport 31337 did not binderror with no obvious cause.Fix
Add
"$HOME/Library/LaunchAgents"to the existingmkdir -p. One-line, idempotent,no behavior change on accounts where the directory already exists.
Hit this on a fresh-account PAI 5 install; this exact patch has been running locally
since. Related to the opaque-install-failure reports.