macOS: fix wizard hang when /tmp/clawdbot is missing #909
+49
−5
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.
Fixes #902.
What was happening
The macOS app starts the gateway via a
launchdLaunchAgent and configuresStandardOutPath/StandardErrorPathto/tmp/clawdbot/clawdbot-gateway.log. On clean machines,/tmp/clawdbotmay not exist.launchddoes not create parent directories for log paths, so the job can fail to start and the onboarding wizard times out waiting for the gateway health endpoint.Fix
Ensure
/tmp/clawdbotexists whenever the macOS app computes launchd log paths (viaLogLocator). This guarantees the parent directory exists before the LaunchAgent plist is written/loaded.Tests
Adds a regression test that deletes
/tmp/clawdbot, accessesLogLocator.launchdGatewayLogPath, and asserts the directory is recreated.