Title: config.yaml is being ignored, system defaults to google provider
Hello,
I am experiencing a persistent issue where my OpenClaw installation seems to be completely ignoring my ~/.openclaw/config.yaml file. No matter what I configure, the agent attempts to resolve models using the google provider, leading to an "Unknown model" error.
My goal is to use a model from the nvidia provider.
Here is a summary of the troubleshooting steps we have already taken:
We correctly configured the nvidia provider and the model ID (moonshotai/kimi-k2-5) in ~/.openclaw/config.yaml.
We confirmed the gateway is installed and running as a persistent systemd user service.
We resolved a conflict where an old pm2 instance of the gateway was also running. The systemd service is now the only one active.
We ran openclaw doctor --fix, which found no errors in the config.yaml file itself.
We checked for any .env files in ~/ or the application directory that could be causing an override, but found none.
We even tried to force the configuration directly into the systemd service using environment variables, but this was also ignored.
Key Finding:
After exhausting all other options, a grep search revealed a potential source of the problem. A file located at /opt/openclaw/vendor/a2ui/mkdocs.yaml contains the line provider: google.
It appears this unrelated documentation file might be overriding all other user configurations on my system. We have not edited this core file due to the risk involved.
Could you please advise on why this might be happening and how to resolve it?
Thank you.
I am experiencing a persistent issue where my OpenClaw installation seems to be completely ignoring my ~/.openclaw/config.yaml file. No matter what I configure, the agent attempts to resolve models using the google provider, leading to an "Unknown model" error.
My goal is to use a model from the nvidia provider.
Here is a summary of the troubleshooting steps we have already taken:
We correctly configured the nvidia provider and the model ID (moonshotai/kimi-k2-5) in ~/.openclaw/config.yaml.
We confirmed the gateway is installed and running as a persistent systemd user service.
We resolved a conflict where an old pm2 instance of the gateway was also running. The systemd service is now the only one active.
We ran openclaw doctor --fix, which found no errors in the config.yaml file itself.
We checked for any .env files in ~/ or the application directory that could be causing an override, but found none.
We even tried to force the configuration directly into the systemd service using environment variables, but this was also ignored.
Key Finding:
After exhausting all other options, a grep search revealed a potential source of the problem. A file located at /opt/openclaw/vendor/a2ui/mkdocs.yaml contains the line provider: google.
It appears this unrelated documentation file might be overriding all other user configurations on my system. We have not edited this core file due to the risk involved.
Could you please advise on why this might be happening and how to resolve it?
Thank you.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
134,426Members
Resources
Similar Threads
Was this page helpful?
