Twenty blocks built-in AI provider names in admin panel form

Twenty now rejects built-in AI provider names in the New AI Provider form of the admin panel. Before this fix, choosing "openai" saved a custom entry with no models. That entry replaced the built-in OPENAI_API_KEY provider, according to the release notes.

The form now shows a banner with a link to the built-in provider's page for models and API key. Saving a built-in name returns a BUILT_IN_AI_PROVIDER_NAME error on the Label field.

Instances that already have the bad entry still show OpenAI as a custom provider. Removing that provider brings the built-in models back. Nothing is migrated or deleted, and setting AI_PROVIDERS directly works as before.

The change applies to the /admin-panel API, which the breaking-changes check does not cover. The integration test was not run locally, the source says.

What it means

If you use Twenty. Admins who added a provider named after a built-in one, such as openai, now see the form reject it. Built-in models return once the custom entry is removed.

What to do. Check AI_PROVIDERS for built-in names such as openai and remove those overrides to restore the built-in models.

Watch for. Scripts calling addAiProvider with built-in names will now get rejected, since the breaking-changes check does not cover this API.