• Explain code in the Web UI with Code explanation
• Summarize issue discussions with Discussion summary
• Forecast deployment frequency with Value stream forecasting
• Root cause analysis
• Summarize an issue with Issue description generation

GitLab Duo experiments

The following GitLab Duo features are experiments.

Explain code in the Web UI with Code explanation

To use this feature:

• The parent group of the project must:
  • Enable the experiment and beta features setting.
• You must:
  • Belong to at least one group with the experiment and beta features setting enabled.
  • Have sufficient permissions to view the project.

GitLab can help you get up to speed faster if you:

• Spend a lot of time trying to understand pieces of code that others have created, or
• Struggle to understand code written in a language that you are not familiar with.

By using a large language model, GitLab can explain the code in natural language.

To explain your code:

1. On the left sidebar, select Search or go to and find your project.
2. Select any file in your project that contains code.
3. On the file, select the lines that you want to have explained.
4. On the left side, select the question mark (). You might have to scroll to the first line of your selection to view it. This sends the selected code, together with a prompt, to provide an explanation to the large language model.
5. A drawer is displayed on the right side of the page. Wait a moment for the explanation to be generated.
6. Provide feedback about how satisfied you are with the explanation, so we can improve the results.

You can also have code explained in the context of a merge request. To explain code in a merge request:

1. On the left sidebar, select Search or go to and find your project.
2. Select Code > Merge requests, then select your merge request.
3. On the secondary menu, select Changes.

4. On the file you would like explained, select the three dots () and select View File @ $SHA.

   A separate browser tab opens and shows the full file with the latest changes.

5. On the new tab, select the lines that you want to have explained.
6. On the left side, select the question mark (). You might have to scroll to the first line of your selection to view it. This sends the selected code, together with a prompt, to provide an explanation to the large language model.
7. A drawer is displayed on the right side of the page. Wait a moment for the explanation to be generated.
8. Provide feedback about how satisfied you are with the explanation, so we can improve the results.

We cannot guarantee that the large language model produces results that are correct. Use the explanation with caution.

Summarize issue discussions with Discussion summary

To use this feature:

• The parent group of the issue must:
  • Enable the experiment and beta features setting.
• You must:
  • Belong to at least one group with the experiment and beta features setting enabled.
  • Have sufficient permissions to view the issue.

You can generate a summary of discussions on an issue:

1. In an issue, scroll to the Activity section.
2. Select View summary.

The comments in the issue are summarized in as many as 10 list items. The summary is displayed only for you.

Provide feedback on this experimental feature in issue 407779.

Data usage: When you use this feature, the text of all comments on the issue are sent to the large language model referenced above.

Forecast deployment frequency with Value stream forecasting

To use this feature:

• The parent group of the project must:
  • Enable the experiment and beta features setting.
• You must:
  • Belong to at least one group with the experiment and beta features setting enabled.
  • Have sufficient permissions to view the CI/CD analytics.

In CI/CD Analytics, you can view a forecast of deployment frequency:

1. On the left sidebar, select Search or go to and find your project.
2. Select Analyze > CI/CD analytics.
3. Select the Deployment frequency tab.
4. Turn on the Show forecast toggle.
5. On the confirmation dialog, select Accept testing terms.

The forecast is displayed as a dotted line on the chart. Data is forecasted for a duration that is half of the selected date range. For example, if you select a 30-day range, a forecast for the following 15 days is displayed.

Provide feedback on this experimental feature in issue 416833.

Root cause analysis

To use this feature:

• The parent group of the project must:
  • Enable the experiment and beta features setting.
• You must:
  • Belong to at least one group with the experiment and beta features setting enabled.
  • Have sufficient permissions to view the CI/CD job.

When the feature is available, the “Root cause analysis” button will appears on a failed CI/CD job. Selecting this button generates an analysis regarding the reason for the failure.

Summarize an issue with Issue description generation

To use this feature:

• The parent group of the project must:
  • Enable the experiment and beta features setting.
• You must:
  • Belong to at least one group with the experiment and beta features setting enabled.
  • Have sufficient permissions to view the issue.

You can generate the description for an issue from a short summary.

1. Create a new issue.
2. Above the Description field, select AI actions > Generate issue description.
3. Write a short description and select Submit.

The issue description is replaced with AI-generated text.

Provide feedback on this experimental feature in issue 409844.

Data usage: When you use this feature, the text you enter is sent to the large language model referenced above.