API Keys not Loading - or where do I put them?

[mrisher]

Hi:
I know this is stupid, but I've spent 20+ minutes and am still stuck: The Continue extension in VSCode seems to be ignoring the config.yaml and the secrets on the Hub. I'm not sure what to do, since the docs assume this is step 0 and just works.

In my Secrets menu on the Hub I have a MISTRAL_API_KEY (e.g. here) but no matter what I do, I get

Error handling model response
...
It's possible that your API key is invalid.
...
401 status code (no body)

I've tried Refresh agent secrets in the Extension but nothing seems to change. I've also tried adding the model (Mistral/Codestral) locally in config.yaml but it doesn't seem to read anything from that file, only from the Hub.

When I load https://hub.continue.dev/continuedev/mistral I have a sidebar that doesn't seem to accept API keys anywhere; there's a settings button but clicking it just says "Choose an existing secret, create a new secret, or set a raw input..." with a Save button but no input box... where do I add the key?

I realize this is evolving quickly and the docs are out of sync with reality in some places; is there something simple I'm missing?

Thank you,
/m

[bdougie]

Apologies on this not being documented well. I will make sure to update this myself. But if you are storing a key in the hub and using it local in a config.yaml, you need to use ${{ inputs. MISTRAL_API_KEY }} and not ${{ secrets. MISTRAL_API_KEY }}. The latter checks locally only, but inputs checks you hub stored secrets.

update: This is incorrect information.

[mrisher]

Thanks for the reply. I'm still not getting it to work. Maybe it's something more fundamental? I tried uninstalling the extension, removing the ~/.continue directory, and doing a fresh install. I have a single secret configured named `MISTRAL_API_KEY` which looks like the one in the YAML on the server (I no longer have any local agent AFAICT): https://hub.continue.dev/continuedev/mistral?view=config Still get a 401 error regardless of what I put into the hub secret, and the logs don't show anything I can interpret. I also tried what you said, putting `inputs.MISTRAL_API_KEY` into the local config.yaml but that doesn't seem to be loaded. Thanks.

…

On Thu, Sep 11, 2025 at 12:03 AM Brian Douglas ***@***.***> wrote: Apologies on this not being documented well. I will make sure to update this myself. But if you are storing a key in the hub and using it local in a config.yaml, you need to use ${{ inputs. MISTRAL_API_KEY }} and not ${{ secrets. MISTRAL_API_KEY }}. The latter checks locally only, but inputs checks you hub stored secrets. — Reply to this email directly, view it on GitHub <#7485 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABVHNQSWOWSKUTLYWW6CST3SCN3FAVCNFSM6AAAAACFEZOH3WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZWG43DINA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[RomneyDa]

@mrisher it looks like the agent has some invalid YAML.
with: apiKey: ${{ ... }} is not valid.
We can get this fixed.
For now, you could remix it to say with: MISTRAL_API_KEY: ${{ secrets.MISTRAL_API_KEY }} and see if that works

[RomneyDa]

@mrisher I pushed a fix for this!
https://hub.continue.dev/continuedev/mistral

[mrisher]

Awesome, thank you so much!

…

On Thu, Sep 11, 2025, 9:36 PM Dallin Romney ***@***.***> wrote: @mrisher <https://github.com/mrisher> I pushed a fix for this! https://hub.continue.dev/continuedev/mistral — Reply to this email directly, view it on GitHub <#7485 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABVHNXQO3YKQQR7JM2FZCD3SHFKZAVCNFSM6AAAAACFEZOH3WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZXG42TGNA> . You are receiving this because you were mentioned.Message ID: ***@***.***>