fix: update macOS node service to use current CLI command shape (closes #43171) by Br1an67 · Pull Request #46843 · openclaw/openclaw

Br1an67 · 2026-03-15T04:02:18Z

Summary

Problem: The macOS app starts the local node service using the obsolete openclaw service node start command shape, which no longer exists in current CLIs. This causes the node service to fail to start, resulting in missing system.run.prepare capability and nodes.run failures.
Why it matters: Without this fix, the macOS app cannot serve as a complete exec-capable node for nodes.run on current CLI installs.
What changed: Updated NodeServiceManager.swift to use subcommand: "node" instead of subcommand: "service", and adjusted the args arrays from ["node", "start"]/["node", "stop"] to ["start"]/["stop"], so the constructed command is openclaw node start --json instead of openclaw service node start --json.
What did NOT change (scope boundary): No changes to CommandResolver, ShellExecutor, or any other files. Only the command shape in NodeServiceManager was updated.

Change Type

Bug fix

Scope

Linked Issue/PR

Closes macOS app still starts node service via obsolete openclaw service node start command #43171

User-visible / Behavior Changes

The macOS app will now correctly start and stop the local node service using the current CLI command surface (openclaw node start/stop), enabling the full exec capability including system.run.prepare.

Security Impact

New permissions/capabilities? No
Secrets/tokens handling changed? No
New/changed network calls? No
Command/tool execution surface changed? No (same command, corrected shape)
Data access scope changed? No

Repro + Verification

Steps

Launch the macOS app with a current CLI install (2026.3.x)
Observe node service startup in app logs

Expected

Node service starts successfully via openclaw node start --json
Node advertises full exec surface including system.run.prepare

Actual (before fix)

App logs: node service start failed: (Did you mean devices?)
Node connects but missing system.run.prepare capability

Evidence

Failing test/log before + passing after
Diff matches issue description exactly: changed subcommand: "service" to subcommand: "node" and removed redundant "node" from args arrays

Human Verification

Verified scenarios: reviewed diff matches issue description; confirmed command shape aligns with current CLI surface
Edge cases checked: both start() and stop() paths updated consistently
What you did NOT verify: runtime end-to-end testing with actual macOS app build

Review Conversations

I replied to or resolved every bot review conversation I addressed in this PR.

Compatibility / Migration

Backward compatible? Yes
Config/env changes? No
Migration needed? No

Failure Recovery

How to disable/revert: revert this commit

Risks and Mitigations

None

greptile-apps · 2026-03-15T04:03:29Z

Greptile Summary

This PR fixes a broken CLI command shape in the macOS app's NodeServiceManager.swift by updating from the obsolete openclaw service node start/stop invocation to the current openclaw node start/stop. This is a focused, single-file bug fix that corrects the root cause of the node service failing to start and the missing system.run.prepare capability.

The subcommand parameter was corrected from "service" to "node" and the redundant "node" prefix was removed from both the start() and stop() args arrays — resulting in the correct command openclaw node start --json / openclaw node stop --json.
Both the start() and stop() paths are updated consistently.
The configRoot: ["gateway": ["mode": "local"]] override is preserved, ensuring service management always runs locally and the SSH code path in CommandResolver is never invoked for these calls.
No other files are touched; the change is minimal and exactly matches the issue description.

Confidence Score: 5/5

This PR is safe to merge — it is a minimal, correct single-file fix with no side effects.
The change is a straightforward two-part correction (subcommand string + args array) that maps cleanly to the current CLI surface. Both start() and stop() are updated consistently, the --json flag handling is unaffected, the local-mode override is preserved, and no other files are touched. The logic is easy to reason about and the diff exactly matches the stated intent.
No files require special attention.

_{Last reviewed commit: 45f567e}

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 45f567ead4

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector · 2026-03-15T04:06:42Z

@@ -6,7 +6,7 @@ enum NodeServiceManager {

    static func start() async -> String? {
        let result = await self.runServiceCommandResult(
-            ["node", "start"],
+            ["start"],


Use a valid node subcommand for service startup

NodeServiceManager.start() now invokes openclaw node start --json (["start"] under subcommand: "node"), but the current CLI surface does not expose node start: registerNodeCli only wires run/status/install/uninstall/stop/restart, and the published subcommand list in docs/cli/index.md matches that set (node start is absent at lines 1013-1018). In remote mode this means startup still fails, so the macOS app cannot bring up the local node service needed for exec-capable nodes.run flows.

Useful? React with 👍 / 👎.

openclaw#43171) The macOS app was using the obsolete `openclaw service node start` command shape which no longer exists in current CLIs. Updated NodeServiceManager to use `openclaw node start` instead, matching the current CLI surface. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…@Br1an67

…@Br1an67)

openclaw-barnacle · 2026-03-17T09:46:57Z

Closing this PR because the author has more than 10 active PRs in this repo. Please reduce the active PR queue and reopen or resubmit once it is back under the limit. You can close your own PRs to get back under the limit.

ImLukeF · 2026-03-17T09:47:02Z

Merged via squash.

Prepared head SHA: dbf2edd6f4fdc89aea865bec631f7a289a4dcbd1
Merge commit: 73032534276d1dedf645e785f02ec2a3c0a2cf89

Thanks @Br1an67!

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: dbf2edd6f4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-03-17T09:50:34Z

    static func start() async -> String? {
        let result = await self.runServiceCommandResult(
-            ["node", "start"],
+            ["start"],


Use a supported node lifecycle command for startup

NodeServiceManager.start() now builds openclaw node start --json, but node start is not exposed by the CLI: registerNodeCli only wires run/status/install/uninstall/stop/restart in src/cli/node-cli/register.ts, and docs/cli/node.md lists the same lifecycle commands. In remote mode, startup still fails with an unknown subcommand, so the macOS app cannot bring up its local node service and exec-capable node flows remain unavailable.

Useful? React with 👍 / 👎.

@ImLukeF