Remove hardcoded model information from Duo Workflow payload builder
Problem
After the fix in ai-assist!3748, passing model information from the Rails monolith to Duo Workflow Service is no longer necessary. The model information is now ignored by Duo Workflow Service, which instead respects the model chosen by the model switching framework.
Current Behavior
-
The Rails monolith currently supplies hardcoded model information (e.g.,
'claude-sonnet-4-5-20250929') to Duo Workflow Service in the payload builder. This is redundant and should be removed. See: https://gitlab.com/gitlab-org/gitlab/blob/master/ee/lib/ai/catalog/duo_workflow_payload_builder/experimental.rb#L101 -
Currently, when an AI catalog flow is created from the YAML-based editor, users have the ability to select a model by adding model details from the prompt component. We need to restrict users so that model details cannot be added by the user.
Expected Behavior
The Rails monolith should not supply model information to Duo Workflow Service. The model selection should be entirely handled by the model switching framework on the Duo Workflow Service side. Users should not be able to manually add model details when creating AI catalog flows from the YAML-based editor.
Related Issues
- ai-assist#1596 - Original error
- ai-assist!3748 - Fix that made model info redundant
- MR !204781 - Discussion where this cleanup was requested
Implementation Notes
- Remove the hardcoded model information from the payload builder
- Ensure model selection is handled entirely by the model switching framework
- Restrict users from adding model details in the YAML-based editor for AI catalog flows
- This ensures consistent behavior across all environments (GitLab.com, Self-Managed, and Self-Hosted Duo)
- Update any related documentation if needed