Support "all" programming languages across Duo Agent Platform (deprecate Code Suggestions additional languages)
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
Problem to solve
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
Long-term goal:
- Deprecate the IDE settings (and LSP support) for Duo Code Suggestions additional languages and hide these settings in the IDE UI.
- 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).
- 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:
- 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
- Markdown - All my blog posts and documentation are written using Duo Code Suggestions.
- Perl - works great.
- PowerShell - works fine.
- YAML - needs more context (a comment, or existing config). Works great with Kubernetes YAML, GitLab CI/CD, and other formats of YAML as well.
- Dockerfile - with comments and context, works fine.
- 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)
- Priyanka (Platform Engineer)
- Amy (Application Security Engineer)
- Isaac (Infrastructure Engineer)
- Alex (Security Operations Engineer)