Frequently asked questions
Practical answers for what you might see while your agent and model providers are set up. For live status and errors, use Technical details on your runtime.
I see a log about xai-auth or "no config-backed key" during OpenClaw setup. Is something wrong?
Usually no — that line does not mean your computer failed to install or that Provisionario skipped a required step.
OpenClaw talks to several model providers (Anthropic, OpenAI, xAI, and others). The [xai-auth] label refers to the xAI (Grok) integration: on startup it looks for a saved xAI API key. If you never added one, it may log something like bootstrap config fallback: no config-backed key found. That is the xAI connector saying "no key on file," not a verdict on your whole system.
It does not mean Grok is secretly powering your session or that you must have clicked Grok. Different parts of the app can initialize or list providers; one module may log while others stay quiet.
If you only use another provider (for example Anthropic) and never intend to use xAI, you can ignore this message. It matters if you want to use Grok and then see errors or missing models for xAI — then add an xAI API key in OpenClaw's configuration.
Does automatic agent setup from Provisionario skip steps I would do manually?
When you connect your model through Provisionario, we run OpenClaw's installer and onboarding in a non-interactive way and pass your provider credentials (for example an Anthropic API key) directly. That replaces the interactive menus you would click in an SSH session — it is not a weaker or incomplete install.
You might still see provider-related log lines for services you did not configure (such as xAI), because OpenClaw may still initialize those modules. That behavior is not specific to automatic setup; it can appear in manual flows too.
SSH asks for a password instead of connecting. What should I check?
First, confirm you actually downloaded the private key when it was shown. Provisionario only reveals that private key once.
Then make sure the local file name in your terminal command matches the key file you saved, including the path after ssh -i. If the path points at the wrong file or a file that does not contain the downloaded private key, SSH usually falls back to asking for a password.