Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@roshanasingh4
Copy link
Contributor

Fixes #902.

What was happening

The macOS app starts the gateway via a launchd LaunchAgent and configures StandardOutPath/StandardErrorPath to /tmp/clawdbot/clawdbot-gateway.log. On clean machines, /tmp/clawdbot may not exist. launchd does 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/clawdbot exists whenever the macOS app computes launchd log paths (via LogLocator). This guarantees the parent directory exists before the LaunchAgent plist is written/loaded.

Tests

Adds a regression test that deletes /tmp/clawdbot, accesses LogLocator.launchdGatewayLogPath, and asserts the directory is recreated.

@steipete
Copy link
Contributor

Thank you!

@steipete steipete force-pushed the fix/macos-wizard-gateway-logdir branch from 089f35e to e9d6dec Compare January 15, 2026 06:13
@steipete steipete merged commit 9603eff into openclaw:main Jan 15, 2026
@steipete
Copy link
Contributor

Landed via temp rebase onto main.\n\n- Gate: pnpm lint && pnpm build && pnpm test\n- Land commit: e9d6dec\n- Merge commit: 9603eff\n\nThanks @roshanasingh4!

steipete added a commit to mneves75/clawdbot that referenced this pull request Jan 15, 2026
cpojer pushed a commit to cpojer/clawdbot that referenced this pull request Jan 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

macOS App: Wizard stuck on 'Starting wizard' / 'Gateway did not become ready'

2 participants