Summary

Detect launchctl bootstrap domain errors ("Domain does not support specified action" / code 125) and show actionable install guidance. This clarifies that LaunchAgent install needs a logged-in GUI session and often fails under SSH/headless or wrong-user contexts.

Current baseline implementation has no clear guidance for users and is often quite confusing in openclaw doctor commands. This improves the mssaging and adds a targeted test for the domain-error path.

• Fixes Gateway install fails with launchctl bootstrap domain error #13794
• Fixes LaunchAgent bootstrap fails on macOS Sequoia 15.2 (error 125) #7417
  lobster-biscuit

Greptile Overview

Greptile Summary

This change improves installLaunchAgent’s error reporting when launchctl bootstrap fails due to an unsupported GUI domain (e.g., headless/SSH sessions or wrong-user contexts), by detecting the specific launchctl failure text/code and throwing a more actionable message with next steps.

It also adds a focused unit test that stubs launchctl on PATH to force the domain-error output and asserts the resulting guidance text is included in the thrown error.

Confidence Score: 4/5

• This PR appears safe to merge; it adds targeted error messaging and a focused test without changing normal success paths.
• The new logic is isolated to the launchctl bootstrap failure branch and only triggers on well-scoped substrings. The added test uses a PATH-stubbed launchctl consistent with existing patterns in this test file. I couldn’t execute the test suite in this environment (no node/pnpm available), so confidence is slightly reduced.
• src/daemon/launchd.test.ts

Context used:

• Context from dashboard - CLAUDE.md (source)
• Context from dashboard - AGENTS.md (source)