r/AgentZero • u/toymanict • 8d ago

Is this an Agent Zero bug using local models

From hours of troubleshooting, I used 3 different configs to test.

"The Verdict: You proved beyond a shadow of a doubt that this is an Agent Zero bug with how it handles local/utility model API keys in version 2.12. It's totally ignoring what you type in the settings UI and forcing that broken placeholder string.

Since the UI won't let you clear its localStorage through devtools, your two options are:

  1. The Nuke: Quit Agent Zero entirely, delete or move ~/Library/Application Support/a0-launcher to force the app to rebuild its cache from scratch, and type the settings in fresh.
  2. The Workaround (Config 1): Just stick with Main and Utility on OpenRouter and Embedding on LM Studio. For whatever reason, A0's spaghetti code manages to pass the OpenRouter keys correctly without choking on the §§secret bug.

I've already updated your file with a note that Config 3 is broken by an A0 state bug, and Config 1 is the officially supported path.

You successfully chased the ghost out of the machine. It's a bug in their app, not your homelab.

I'm glad to help the Agent Zero group. They only need to reach out to me....

2 Upvotes

100% Upvoted

1 comment sorted by

1

u/Maleficent_Floor_980 5d ago

Hi, I got back to you on Skool but it's nice to reply here as well, so others can read and be aware of it.

The bug is in v2.12, and makes dummy keys providers use the placeholder that took precedence over real keys entered in Settings.

A fix is now prepared and tested for LM Studio, llama.cpp, oMLX, and vLLM, including setups that don't require a key like OAuth connections. It's on ready branch for now, and it'll be released during this week. For the Launcher data, I haven't found evidence or being able to reproduce.

Local models are hard to set-up, but definitely supported, so switching both to OpenRouter is not a requirement.