openclaw-kickoff

To finalize GoC onboarding for OpenClaw hosts, run the OpenClaw kickoff extension after completing the generic kickoff. It verifies ClawHub readiness, plugin registration, and environment preparation to ensure the host is deployment-ready.

OpenClaw kickoff verification checks ClawHub readiness, confirms the GoC plugin is registered, validates required host tooling, and ensures no private-notes files exist. It confirms the environment is fully prepared for GoC deployment.

No, you do not need to grant host permissions or create private-notes files for OpenClaw GoC setup. The kickoff extension enforces a strict no-permission grant policy and validates the absence of host-specific private-notes files.

You should run the OpenClaw kickoff extension immediately after the generic kickoff completes on an OpenClaw host. It serves as the final ready-state verification step before GoC can run without further kickoff intervention.

If your GoC plugin is not registering on OpenClaw hosts, the kickoff may be incomplete. The OpenClaw kickoff extension performs a state detection sweep to confirm plugin registration and ensures the plugin is installed and up to date.

No, generic kickoff alone cannot fully prepare OpenClaw hosts for GoC deployment. You need the OpenClaw kickoff extension to handle OpenClaw-specific setup, including ClawHub compatibility checks and plugin readiness validation.