Closing this as implemented after Codex automated review.

Current main already covers the reported stale macOS LaunchAgent entrypoint after package/non-git updates: package updates run the updated install's doctor in update-repair mode, doctor detects entrypoint drift, and update repair stages a rewritten service plist even when the gateway is not currently loaded. Loaded services still get the force install refresh before restart.

What I checked:

Package update runs doctor from updated entrypoint: After a global package update, current main resolves the updated package root entrypoint and runs doctor --non-interactive with OPENCLAW_UPDATE_IN_PROGRESS=1, so service metadata repair is driven by the newly installed package rather than the stale entrypoint. (src/cli/update-cli/update-command.ts:424, d228463120a5)
Doctor detects service entrypoint drift: Doctor builds the expected gateway install plan, compares the current service entrypoint to the expected current install entrypoint, and emits Gateway service entrypoint does not match the current install. when they differ. (src/commands/doctor-gateway-services.ts:280, d228463120a5)
Update repair stages rewritten plist: When doctor is running in update repair mode, it calls service.stage instead of service.install; for launchd, staging writes the LaunchAgent plist. This updates the on-disk plist without requiring the service to already be loaded. (src/commands/doctor-gateway-services.ts:336, d228463120a5)
LaunchAgent staging writes plist: stageLaunchAgent delegates to writeLaunchAgentPlist, which writes the LaunchAgent file before printing the staged path. (src/daemon/launchd.ts:554, d228463120a5)
Regression coverage for entry.js to index.js drift: Tests cover a service currently pointing at dist/entry.js while the install expects dist/index.js, including the non-interactive update path where repair is staged rather than installed. (src/commands/doctor-gateway-services.test.ts:384, d228463120a5)
Regression coverage for package-update doctor: Tests verify package updates invoke the updated entrypoint's doctor --non-interactive with OPENCLAW_UPDATE_IN_PROGRESS=1, and that already-current package installs still refresh/verify instead of skipping post-update repair. (src/cli/update-cli.test.ts:995, d228463120a5)

So I’m closing this as already implemented rather than keeping a duplicate issue open.

Codex Review notes: model gpt-5.5, reasoning high; reviewed against d228463120a5; fix evidence: release v2026.4.14, commit d228463120a5.

Uh oh!

Uh oh!

Gateway LaunchAgent not updated on non-git installs #48992

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions