Bug type

UI / Gateway integration

Summary

Approving the first-run Crestodian setup in the macOS app successfully writes the configuration, but the required Gateway restart closes the crestodian.chat socket before the RPC result reaches the app. The app then shows a transport error even though setup succeeded.

Steps to reproduce

1. Start the macOS app against a fresh isolated OpenClaw state directory with a reusable Claude Code login.
2. Open the Crestodian onboarding conversation.
3. Approve the proposed setup with yes.

Expected behavior

The app reconnects after the configuration-triggered Gateway restart, confirms the completed setup, and continues onboarding without exposing a transport error.

Actual behavior

The setup and audit entry complete, but the RPC fails with gateway closed (1012): service restart. Manually choosing Restart reconnects and shows the configured agent as ready.

OpenClaw version

2026.6.11 / 4068f3

Operating system

macOS

Install method

Packaged branch build

Model / provider

claude-cli/claude-opus-4-8 via an existing Claude Code login

Logs / evidence

The setup config, workspace bootstrap, crestodian.setup audit record, Gateway health, and a normal agent turn all succeeded. Only the in-flight crestodian.chat response was lost to close code 1012.

Impact

First-run onboarding reports failure after a successful setup and requires a manual recovery click.

Additional context

The structured AI activation screen already reconciles an outcome-unknown transport drop after a Gateway restart; the conversational onboarding path does not.