Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

The macOS app shows first-run onboarding for an already configured Gateway instead of opening the dashboard after that Gateway connects successfully.

Steps to reproduce

1. Start with an existing OpenClaw Gateway configuration and agent.
2. Launch the macOS app with openclaw.onboardingSeen unset or false.
3. Let the app connect to the configured Gateway.
4. Observe the native onboarding flow, including the Connect your AI step, instead of the dashboard.

Expected behavior

When the configured Gateway connects successfully, treat the existing installation as already set up, complete the app-local onboarding marker, and open the dashboard immediately.

Actual behavior

The app schedules onboarding independently of the asynchronous Gateway connection. A configured installation with no app-local onboarding marker therefore enters the full setup flow and asks for provider configuration again.

OpenClaw version

Current main at 4be6fa7413af0fdc6a3624f99045406dc6419bd0.

Operating system

macOS; exact version not provided.

Install method

OpenClaw macOS app with an existing configured Gateway.

Model

Existing configured agent; exact model not relevant to the launch-routing defect.

Provider / routing chain

Existing configured Gateway and agent; exact provider not provided.

Additional provider/model setup details

The defect occurs before a normal agent turn. The relevant observed state is a configured Gateway that can connect successfully.

Logs

No redacted runtime log supplied. Current source schedules first-run onboarding before the asynchronous connection-mode coordinator finishes.

Screenshots, recordings, and evidence

Observed native screen: Connect your AI, with the app attempting ws://127.0.0.1:18789, despite the user already having an existing Gateway/agent configuration. Screenshot supplied privately with the report and not uploaded here.

Impact and severity

• Affected: macOS app users connecting to an existing Gateway from a fresh app-local preferences state.
• Severity: blocking/confusing onboarding regression.
• Frequency: deterministic when the Gateway is configured but openclaw.onboardingSeen is false.
• Consequence: users repeat provider and Crestodian setup instead of reaching their existing dashboard.

Additional information

The regression was made visible when local Gateway automation changed the configured-installation fast path to also require the app-local onboarding marker in #99767. The fix should preserve onboarding when the configured Gateway cannot connect.