<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Label this issue](https://contributors.gitlab.com/manage-issue?action=label&projectId=278964&issueIid=571515) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=571515) </details> <!--IssueSummary end--> <!--This issue template can be used as a great starting point for feature requests. Learn more about the process: https://handbook.gitlab.com/handbook/product/product-management/#customer-feature-requests. The section "Release notes" can be used as a summary of the feature and is also required if you want to have your release post blog MR auto generated using the release post item generator: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-item-generator. The remaining sections are the backbone for every feature in GitLab. The goal of this template is brevity for quick/smaller iterations. For a more thorough list of considerations for larger features or feature sets, you can leverage the detailed [feature proposal](https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md).--> ### Release notes <!--What is the problem and solution you're proposing? This content sets the overall vision for the feature and serves as the release notes that will populate in various places, including the [release post blog](https://about.gitlab.com/releases/categories/releases/) and [Gitlab project releases](https://gitlab.com/gitlab-org/gitlab/-/releases). "--> ### Problem to solve <!--What is the user problem you are trying to solve with this issue?--> GitLab Duo Code Suggestions offers a limited set of programming languages that are officially supported. https://docs.gitlab.com/user/project/repository/code_suggestions/supported_extensions/#supported-languages-by-ide The settings are confusing for customers - while aimed at Duo Code Suggestions only, the IDE UI implies at the bottom "GitLab Duo disabled". You need to hover over the ALT text to learn that only Duo Code Suggestions are affected.   The confusion also stems from other platform areas: Duo Chat and more Duo Enterprise features leverage the LLMs' knowledge ("all"). Claude Sonnet 3.5,3.7/4.0 proved to know mature languages well. Duo Agent Platform with the AI Catalog puts another layer of supported languages ("any"). ### Proposal <!--Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues.--> Long-term goal: 1. Deprecate the IDE settings (and LSP support) for Duo Code Suggestions [additional languages](https://docs.gitlab.com/user/project/repository/code_suggestions/supported_extensions/#add-support-for-more-languages) and hide these settings in the IDE UI. 2. Simplify the documentation for supported languages. https://docs.gitlab.com/user/project/repository/code_suggestions/supported_extensions/#supported-languages-by-ide by adding more supported languages (see below). 3. Unify the IDE health status indicators to show the important information to users - overall health status, usage, etc. (separate issue). #### Iterations The original list was inspired by Language Server markers for languages detected in source code file extensions. https://gitlab.com/gitlab-org/editor-extensions/gitlab-lsp/-/blob/main/code_suggestions_config.json We can iterate by adding known languages by default, and minimize the "optional additional setting". I've been testing the following languages in my development environment in VS Code for 1+ year now: 1. Ansible - works great, the custom rules deep dive tutorial used it https://about.gitlab.com/blog/custom-rules-duo-agentic-chat-deep-dive/#ansible-linter-compliance 2. Markdown - All my blog posts and documentation are written using Duo Code Suggestions. 3. Perl - works great. 4. PowerShell - works fine. 5. YAML - needs more context (a comment, or existing config). Works great with Kubernetes YAML, GitLab CI/CD, and other formats of YAML as well. 6. Dockerfile - with comments and context, works fine. 7. COBOL - not really yet. That needs to be replaced with Duo Agents I've also tested `vb` (Visual Basic) but this is in maintenance mode, so not necessary. `json` is only for experiments, really depends on the existing content. VS Code Settings: https://gitlab.com/dnsmichi/dotfiles/-/blob/main/vscode/settings.json?ref_type=heads ### Intended users * [Sasha (Software Developer)](https://handbook.gitlab.com/handbook/product/personas/#sasha-software-developer) * [Priyanka (Platform Engineer)](https://handbook.gitlab.com/handbook/product/personas/#priyanka-platform-engineer) * [Amy (Application Security Engineer)](https://handbook.gitlab.com/handbook/product/personas/#amy-application-security-engineer) * [Isaac (Infrastructure Engineer)](https://handbook.gitlab.com/handbook/product/personas/#isaac-infrastructure-security-engineer) * [Alex (Security Operations Engineer)](https://handbook.gitlab.com/handbook/product/personas/#alex-security-operations-engineer) <!--Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Personas are described at https://handbook.gitlab.com/handbook/product/personas/ * [Parker (Product Manager)](https://handbook.gitlab.com/handbook/product/personas/#parker-product-manager) * [Delaney (Development Team Lead)](https://handbook.gitlab.com/handbook/product/personas/#delaney-development-team-lead) * [Presley (Product Designer)](https://handbook.gitlab.com/handbook/product/personas/#presley-product-designer) * [Sasha (Software Developer)](https://handbook.gitlab.com/handbook/product/personas/#sasha-software-developer) * [Priyanka (Platform Engineer)](https://handbook.gitlab.com/handbook/product/personas/#priyanka-platform-engineer) * [Sidney (Systems Administrator)](https://handbook.gitlab.com/handbook/product/personas/#sidney-systems-administrator) * [Rachel (Release Manager)](https://handbook.gitlab.com/handbook/product/personas/#rachel-release-manager) * [Simone (Software Engineer in Test)](https://handbook.gitlab.com/handbook/product/personas/#simone-software-engineer-in-test) * [Allison (Application Ops)](https://handbook.gitlab.com/handbook/product/personas/#allison-application-ops) * [Ingrid (Infrastructure Operator)](https://handbook.gitlab.com/handbook/product/personas/#ingrid-infrastructure-operator) * [Dakota (Application Development Director)](https://handbook.gitlab.com/handbook/product/personas/#dakota-application-development-director) * [Dana (Data Analyst)](https://handbook.gitlab.com/handbook/product/personas/#dana-data-analyst) * [Eddie (Content Editor)](https://handbook.gitlab.com/handbook/product/personas/#eddie-content-editor) * [Amy (Application Security Engineer)](https://handbook.gitlab.com/handbook/product/personas/#amy-application-security-engineer) * [Isaac (Infrastructure Engineer)](https://handbook.gitlab.com/handbook/product/personas/#isaac-infrastructure-security-engineer) * [Alex (Security Operations Engineer)](https://handbook.gitlab.com/handbook/product/personas/#alex-security-operations-engineer) * [Cameron (Compliance Manager)](https://handbook.gitlab.com/handbook/product/personas/#cameron-compliance-manager)--> ### Feature Usage Metrics <!--How are you going to track usage of this feature? Think about user behavior and their interaction with the product. What indicates someone is getting value from it? Explore (../../doc/development/internal_analytics/internal_event_instrumentation/quick_start.md) for a guide.--> ### Does this feature require an audit event? <!--- Checkout these docs to know more https://docs.gitlab.com/ee/development/audit_event_guide/#what-are-audit-events https://docs.gitlab.com/administration/compliance/audit_event_reports/ ---> <!--Label reminders Make sure to add the appropriate labels for the product stage and/or group (e.g ~"devops::plan") if known and add a comment tagging the appropriate Product Manager. Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ Examples: /label ~"GitLab Free" ~"GitLab Premium" ~"GitLab Ultimate"--> /cc @jordanjanes @dashaadu