Skip to content

[BUGFIX] Derive Symfony AI bridge capabilities from the catalog - #42

Open
o-ba wants to merge 1 commit into
mainfrom
issue-41
Open

o-ba wants to merge 1 commit into
mainfrom
issue-41

Conversation

@o-ba

@o-ba o-ba commented Oct 9, 2026

Copy link
Copy Markdown
Member

A bridge with a static model catalog was granted every AiM capability, so a bridge without any image model listed image generation. Catalog models mapping to no AiM capability, such as text-to-speech models, were treated as unlisted and inherited chat, vision and image generation.

Every catalog model is now listed with its mapped capabilities, possibly none, and the provider advertises their union. An unlisted model never inherits image generation, and "provider:*" picks the first enabled configuration whose model supports the requested capability.

Resolves: #41

A bridge with a static model catalog was granted every AiM
capability, so a bridge without any image model listed image
generation. Catalog models mapping to no AiM capability, such as
text-to-speech models, were treated as unlisted and inherited
chat, vision and image generation.

Every catalog model is now listed with its mapped capabilities,
possibly none, and the provider advertises their union. An
unlisted model never inherits image generation, and "provider:*"
picks the first enabled configuration whose model supports the
requested capability.

Resolves: #41
Signed-off-by: Oliver Bartsch <bo@cedev.de>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Symfony AI bridges always advertise all capabilities, regardless of their ModelCatalog

2 participants