doc/user/duo_agent_platform/turn_on_off.md
{{< details >}}
{{< /details >}}
GitLab Duo Agent Platform is on by default. Agent Platform includes a set of features.
You can turn Agent Platform on or off:
To configure tool governance for Agent Platform, see agent tool governance.
{{< details >}}
{{< /details >}}
{{< history >}}
{{< /history >}}
Prerequisites:
To turn Agent Platform on or off for a top-level group:
Agent Platform availability changes for all subgroups and projects.
When Agent Platform is turned off, the following features are hidden:
Prerequisites:
To turn Agent Platform on or off for an instance:
When Agent Platform is turned off, the following features are hidden:
{{< history >}}
{{< /history >}}
Turn GitLab Duo on for all users, regardless of group or project settings.
When you set GitLab Duo availability to Always on, experiment and beta features are not automatically turned on. To use experiment and beta features, you must turn them on separately.
{{< tabs >}}
{{< tab title="On GitLab.com" >}}
Prerequisites:
To lock GitLab Duo on for a top-level group:
GitLab Duo is locked on for all subgroups and projects. Users with the Owner role for a subgroup or project cannot turn GitLab Duo off.
{{< /tab >}}
{{< tab title="On GitLab Self-Managed" >}}
Prerequisites:
To lock GitLab Duo on for an instance:
GitLab Duo is locked on for all groups, subgroups, and projects. Users with the Owner role for a group, subgroup, or project cannot turn GitLab Duo off.
{{< /tab >}}
{{< /tabs >}}
GitLab Duo is on by default. You can turn GitLab Duo on or off:
{{< details >}}
{{< /details >}}
{{< history >}}
{{< /history >}}
Prerequisites:
To change GitLab Duo availability for a top-level group:
GitLab Duo availability changes for all subgroups and projects.
Prerequisites:
To change GitLab Duo availability for a group or subgroup:
GitLab Duo availability changes for all subgroups and projects.
Prerequisites:
To change GitLab Duo availability for a project:
Prerequisites:
To change GitLab Duo availability for an instance:
Prerequisites:
To change GitLab Duo availability for a group or subgroup:
GitLab Duo availability changes for all subgroups and projects.
Prerequisites:
To change GitLab Duo availability for a project:
GitLab Duo Core is included with Premium and Ultimate subscriptions.
If you were an existing customer with a Premium or Ultimate subscription before May 15, 2025, when you upgrade to GitLab 18.0 or later, to use GitLab Duo Core, you must turn it on.
{{< details >}}
{{< /details >}}
{{< history >}}
{{< /history >}}
Prerequisites:
To change GitLab Duo Core availability for a top-level group:
It might take up to 10 minutes for the change to take effect.
Prerequisites:
To change GitLab Duo Core availability for an instance:
GitLab Duo features that are experimental and beta are turned off by default. These features are subject to the Testing Agreement.
{{< details >}}
{{< /details >}}
{{< history >}}
{{< /history >}}
Prerequisites:
To turn on GitLab Duo experiment and beta features for a top-level group:
This setting cascades to all projects that belong to the group.
{{< tabs >}}
{{< tab title="In 17.4 and later" >}}
In GitLab 17.4 and later, follow these instructions to turn on GitLab Duo experiment and beta features for your GitLab Self-Managed instance.
Prerequisites:
To turn on GitLab Duo experiment and beta features for an instance:
{{< /tab >}}
{{< tab title="In 17.3 and earlier" >}}
Prerequisites:
To turn on GitLab Duo experiment and beta features for an instance:
In the upper-right corner, select Admin.
In the left sidebar, select Settings > GitLab Duo.
Expand Change configuration.
Under Feature preview, select Use experiment and beta GitLab Duo features.
Select Save changes.
For GitLab Duo Chat to work immediately, manually synchronize your subscription.
If you do not manually synchronize your subscription, it might take up to 24 hours to activate GitLab Duo Chat on your instance.
{{< /tab >}}
{{< /tabs >}}
When you turn Agent Platform on or off, you might encounter the following issues.
{{< details >}}
{{< /details >}}
On GitLab Self-Managed, Change configuration might not display. Change configuration appears only when your instance has one of the following:
Without these requirements, you cannot control the availability of GitLab Duo through the UI. To turn GitLab Duo off, use the Rails console or the API instead.
In a Rails console session, run the following command:
ApplicationSetting.current.update!(duo_features_enabled: false, lock_duo_features_enabled: true)
To verify the change, run the following command:
Gitlab::CurrentSettings.duo_features_enabled # => false
Gitlab::CurrentSettings.duo_never_on? # => true
Alternatively, send a PUT request to the application settings API with an
administrator token that has the api scope:
curl --request PUT \
--header "PRIVATE-TOKEN: <admin_token>" \
--data "duo_availability=never_on" \
"https://<your-gitlab-host>/api/v4/application_settings"
You might have to refresh your browser before the GitLab Duo panel disappears.