Waltz Flight Assistant Setup
Install and configure the Waltz Flight Assistant plugin before trying to route flight work through it.
Setup workflow
- Check whether the plugin is already installed and loaded:
openclaw plugins inspect waltz-flight-assistant --json
- If the plugin is missing, install it:
openclaw plugins install clawhub:@waltzlabs/flight-assistant-plugin
- If the plugin was just installed, restart OpenClaw before editing config or testing flight requests.
- Update
~/.openclaw/openclaw.jsonsoplugins.entries.waltz-flight-assistantexists with:
{
"enabled": true,
"config": {
"baseUrl": "https://waltz-flight-staging.up.railway.app"
}
}
- Restart the gateway after writing or changing
baseUrl:openclaw gateway restart
- Verify the config took effect:
openclaw plugins inspect waltz-flight-assistant --json- confirm the plugin is loaded and the config entry exists
Runtime rules
- Use published plugin package
clawhub:@waltzlabs/flight-assistant-pluginfor installs. - Use plugin id
waltz-flight-assistantfor config. - Use
https://waltz-flight-staging.up.railway.appas the defaultbaseUrlunless Waltz provides a different deployment. - If OpenClaw says the Waltz config is being ignored, restart first and then apply the config change again.
- After any
baseUrlchange, restart the gateway before testing the plugin. - Do not ask the user to edit
openclaw.jsonmanually if you can update it directly.
After setup
- Route flight requests through
flight_assistant. - Reuse the same
context_idfor follow-ups about the same trip. - Use the plugin for:
- searching flights
- booking flights
- retrieving existing bookings
- continuing payment setup and authentication flows
If setup is incomplete
- If the plugin is not loaded in the current session, tell the user exactly what remains:
- install plugin
- restart OpenClaw
- apply Waltz config
- restart the gateway
- retry the flight request
- Keep the explanation short and concrete. Do not send the user to local repo paths.