Projects use only their own provider keys
v0.124.1
What changes
A prompt or an evaluator runs on the provider keys saved in its project.
- If a project has no key for a provider, the run fails with "No API key found for model". Add the key in Settings > Providers & Models.
- A custom provider that signs in with a key needs its own non-empty API key. Bedrock, SageMaker and Vertex use their own credentials. Without a key, the run stops with a
400configuration error before it calls the provider.
Self-hosting
Provider keys set on the services container (for example OPENAI_API_KEY) serve projects that have no key of their own only when AGENTA_SERVICES_ENV_PROVIDER_KEYS_ENABLED is true.
| Edition | Default |
|---|---|
| Open source | true (unchanged) |
| Enterprise | false |
To keep shared keys in an Enterprise deployment, set AGENTA_SERVICES_ENV_PROVIDER_KEYS_ENABLED=true. A custom provider always uses its own key. See the configuration reference for details.
Improvements1
- ModelsBuilt-in Gemini uses gemini-3.8-flash with low thinking by default
Fixes2
- ModelsBuilt-in Gemini turns no longer hang when a Vertex call stalls
- Sign-upGmail addresses with dots or a +tag count as one address at sign-up