openclaw - 💡(How to fix) Fix doctor reports gateway service entrypoint mismatch on macOS LaunchAgent in v2026.4.1 (entry.js vs index.js) [1 participants]

Summary

After upgrading to OpenClaw v2026.4.1 on macOS, openclaw doctor --non-interactive reports a gateway service entrypoint mismatch (entry.js vs index.js) while the macOS LaunchAgent still uses dist/entry.js and the gateway works normally.

This looks like a mismatch between what doctor expects and what the LaunchAgent generator/service setup actually writes.

Environment

• OpenClaw: v2026.4.1
• OS: macOS
• Service mode: LaunchAgent

Observed behavior

• openclaw doctor --non-interactive reports a gateway service entrypoint mismatch
• openclaw gateway status shows the gateway service is healthy and running
• The LaunchAgent plist still points to dist/entry.js
• The gateway continues to function normally

Expected behavior

Either:

1. the generated LaunchAgent should use dist/index.js, or
2. doctor should accept dist/entry.js if that is still intended/compatible on macOS in v2026.4.1.

Actual behavior

• Service works correctly
• doctor keeps reporting a mismatch
• Manual alignment attempts do not appear to stick / are not the intended fix

Why this matters

This makes it unclear whether the service is actually misconfigured or whether doctor is reporting a false positive, which can lead users to perform unnecessary manual service edits.

Repro steps

1. Upgrade OpenClaw to v2026.4.1
2. Run openclaw doctor --non-interactive
3. Run openclaw gateway status
4. Inspect ~/Library/LaunchAgents/ai.openclaw.gateway.plist
5. Observe that doctor expects dist/index.js while the LaunchAgent still uses dist/entry.js

Additional note

A separate openclaw security audit --deep warning about gateway.trusted_proxies_missing was also observed, but it seems unrelated and likely expected for loopback-only/local setups.