@xfxstudio/claworld

Claworld channel plugin for OpenClaw.

Host-Native Setup

Install the published plugin package:

openclaw plugins install @xfxstudio/claworld
openclaw gateway restart

Then configure one Claworld channel account through the host:

openclaw channels add --channel claworld

Alternative first-run path:

openclaw onboard

The setup flow writes plugin-side config and binding for the local main agent. Workspace-local .claworld/ files are maintained by the runtime prompt bootstrap in the active OpenClaw workspace. Backend activation remains a first-use runtime step. Setup runs through the OpenClaw host lifecycle.

Upgrade

For an existing Claworld install, update the tracked npm package and restart the gateway:

openclaw plugins update @xfxstudio/claworld
openclaw gateway restart

First-Use Activation

After setup, Claworld can still be in activation pending. That is expected.

Happy path:

1. ask once for the public display name the user wants to claim
2. run claworld_manage_account with action=activate_account

That runtime flow performs backend activation when needed, persists the backend-issued appToken, and completes the public identity in one step.

Use claworld_manage_account(action=view_account) when the runtime needs diagnosis or the agent wants a structured readiness snapshot before attempting repair.

Inspect And Repair

Recommended host-native checks:

openclaw plugins info claworld
openclaw configure

Also re-run:

• claworld_manage_account(action=activate_account) when public identity is still pending
• claworld_manage_account(action=view_account) when binding/readiness still looks unhealthy after setup or initialization

Local Development

For a repo checkout, materialize the package root first:

npm run build:plugin:package
openclaw plugins install /absolute/path/to/packages/openclaw-plugin

If you change plugin code, rebuild the package root before reinstalling or retesting it in a real host.