[UX] Design for Expanded Chat Sub-Features

Currently, Duo Code Suggestions in expanded out into its supported sub-features (Code Generation and Code Completion) while Duo Chat is not expanded. This means that a user can only configure a single model to support Chat.

The front end for Chat expansion has been built, and it is possible to expand the sub-features for Duo Chat by enabling the ai_duo_chat_sub_features_settings feature flag.

The potential sub-features to be included in a Chat sub-feature expansion include:

• Zero Shot Agent
• EpicReader
• IssueReader
• GitlabDocumentation
• Explain Code - /explain
• RefactorCode - /refactor
• FixCode - /fix
• WriteTests - /test
• Explain Vulnerability - /vulnerability_explain
• Troubleshoot_Job - /troubleshoot
• MergeRequestReader
• CIEditorAssistant
• SummarizeComments

Proposal

Prior to enabling Chat sub-feature expansion we need to address the following:

• does the current by-sub-feature expansion serve our customers?
  • expanding as-is would require customers to manually configure for each sub-feature of chat
  • should we enable a cascade? Whereby a customer can configure one code-specific model for code sub-features and then cascade that setting to other supported sub-features (i.e. configure Codestral for /refactor and cascade to /fix, /test, and /explain)
  • should we simply represent two sub-features of Chat
    • general Chat (the ReAct prompt) - this would include all the NLP-centric functions
    • code specific slash commands - this would include all the code-specific functions

Definition of Done

• Customers are able to have sufficiently granular control of Chat features and sub-features in a way that is seamless and easy.