[Bug][macOS] Startup Safety remains AT RISK on 2.84.0 with enabled current-app login item #7019

Client or integration

OpenCodex Desktop / dashboard / ocx

Area

Platform (macOS) / Startup safety

Summary

On macOS, OpenCodex 2.84.0 continues to report that Desktop startup “could not be verified” and marks restart safety “AT RISK” even though OpenCodex is present in System Settings → General → Login Items & Extensions → Open at Login, launchd reports the OpenCodex job as enabled, and the LaunchAgent points to the current /Applications/OpenCodex.app copy.

The proxy is healthy and its running version matches 2.84.0. This appears to be a login-registration verification/status problem, not a proxy availability or version-skew problem.

Reproduction

1. On macOS, install/update OpenCodex Desktop to 2.84.0.
2. Enable/retain OpenCodex under System Settings → General → Login Items & Extensions → Open at Login. The user's screenshot shows OpenCodex in that list.
3. Reopen OpenCodex so its bundled proxy starts.
4. Run ocx status and ocx doctor.
5. Both continue to report restart safety at risk because desktop startup could not be verified, while the proxy is running and routing through opencodex-local.

Expected

With the current app registered under Open at Login, launchd showing the item as enabled, and the registered program path matching the current app copy, Startup Safety should verify the registration or explain the precise reason it cannot. A healthy desktop-supervised proxy should not be presented as unhealthy solely because the login item probe is inconclusive.

Actual

ocx status reports:

Proxy: running (health endpoint ok)
Runtime: /Applications/OpenCodex.app/Contents/MacOS/ocx
Restart safety: AT RISK after restart (desktop startup could not be verified; reopen OpenCodex and check Start at Login)
routing=opencodex-local
service=installed-but-unhealthy

ocx doctor reports the same restart-safety warning, and confirms:

ok ocx 2.84.0 matches the running proxy

macOS registration evidence

System Settings screenshot shows OpenCodex in the Open at Login list. The user reports that login startup is enabled in macOS settings.

launchctl print-disabled gui/$(id -u) includes:

"OpenCodex" => enabled

~/Library/LaunchAgents/OpenCodex.plist contains:

Label = OpenCodex
ProgramArguments = [
  /Applications/OpenCodex.app/Contents/MacOS/opencodex-desktop,
  --autostart
]
RunAtLoad = true

launchctl print gui/$(id -u)/OpenCodex reports:

managed_by = com.apple.xpc.ServiceManagement
state = not running
program = /Applications/OpenCodex.app/Contents/MacOS/opencodex-desktop
runs = 1
last exit code = 0

The job is submitted and points to the current app path, but its state is “not running.” It is unclear whether this is a valid registered-at-login state that the health check is misclassifying or a remaining registration problem.

Versions and related issues

• OpenCodex Desktop: 2.84.0
• ocx: 2.84.0
• Running proxy: 2.84.0
• OS: macOS; exact version not captured
• Device: MacBook Air

Related reports/fixes:

• [Bug]: ocx status says Desktop Start at Login "could not be verified" when the LaunchAgent is registered but not yet loaded #6948: ocx status reports login startup unverified when the LaunchAgent is registered but not yet loaded; closed as fixed by fix(cli): harden hub disable, log filters and service startup diagnostics #6954.
• [Bug][macOS] Tray "Start at Login" checkbox reads plist existence only; Startup safety reports it unverified when launchd disables or points at another app copy #6972: macOS tray Start at Login and Startup Safety can disagree; closed as fixed by fix(desktop): tray Start at Login shows only what Startup safety verifies #6996, stated to ship in 2.84.0.
• Dekstop App doesnt pick up codex or allow shim install or repair. #6963: Desktop-owned proxy shown as installed but unhealthy; wording adjusted by fix(startup): dashboard installer on compiled ocx and clearer Desktop Start at Login state (#6963) #6980.

This report provides a post-update observation with the current app path and launchd reporting the item enabled, but the Startup Safety warning remains in 2.84.0.

Additional context

There was initially version skew: ocx was 2.84.0 while the already-running proxy was 2.83.0. The proxy was stopped and OpenCodex was quit/reopened; it came back healthy as PID 57448. The current ocx doctor confirms 2.84.0 matches the running proxy, but restart safety remains at risk.

The service manager is installed but not running while the Desktop owns the active proxy. No attempt was made to start a competing background service. ocx stop temporarily stopped the proxy and left Codex on native routing; reopening OpenCodex brought the proxy back and restored opencodex-local routing.

Could you clarify whether launchd's state = not running with this submitted, enabled, current-app LaunchAgent is expected, and whether Startup Safety should treat it as a valid next-login registration in 2.84.0?

Checks

• I searched existing issues and documentation.
• I removed secrets, account identifiers, tokens, and personal data.