Audit AI events

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated

Introduced in GitLab 19.1 as a beta with a feature flag named agent_artifacts_page. Disabled by default.
Enabled by default in GitLab 19.2.

[!warning] This feature is in beta. It is subject to change without notice. For more information, see GitLab Testing Agreement.

Use the AI audit event report for a unified, browsable record of GitLab Duo agent activity. Each agent session produces a comprehensive audit artifact that you can inspect.

View AI audit events

AI audit events are available on the Governance page as the Audit events tab.

Prerequisites:

You have the Owner role for the top-level group.

To view AI audit events for a group:

In the top bar, select Search or go to and find your top-level group.
Select Settings > GitLab Duo.
Select Change governance.
Select the Agent artifacts tab.

The tab displays a list of agent sessions. Each row shows:

The agent type (workflow definition).
The project the session ran in.
The number of audit events in the session.
The session start time.

Filter sessions

You can filter the session list to narrow results:

Project: Filter by project path, or exclude a specific project.
Date range: Filter sessions created after or before a specific date.
Triggered by: Filter by the user who triggered the session, or exclude a specific user.

View session details

To inspect the events within a session:

Select a session row to open the session details panel. The panel shows session metadata and a chronological list of audit events.
Select an individual event to view its full details, including entity and target information.

Enable AI audit event storage

Introduced in GitLab 19.2.

AI audit event storage is disabled by default. You must explicitly enable storage before agent session data is written to the database or ClickHouse. Disabling storage does not affect real-time streaming of AI audit events.

The setting cascades from instance to group to project:

When disabled and locked at the group level, projects in that group cannot override it.
When enabled and locked at the group level, all projects in that group have storage enabled and cannot disable it.

Prerequisites:

You must have the Owner role or the Security Manager role for the group or project.

Enable storage for a group

In the top bar, select Search or go to and find your group.
Select Settings > GitLab Duo.
Select Change configuration.
In the Data and privacy section, select Store AI audit events.
Select Save changes.

Enable storage for a project

In the top bar, select Search or go to and find your project.
Select Settings > General.
Expand the GitLab Duo section.
Turn on the Store AI audit events toggle.
Select Save changes.

If the setting is locked by a parent group, the control is disabled and cannot be changed at the project level.

Event attribution with composite identity

Introduced in GitLab 19.3.

When an agent session runs with a composite identity, which is the default identity for agent sessions, the AI audit events for the session are attributed to the service account. The author_id field contains the user ID of the service account, and the service account appears as the event author.

The event details field records the human user who started the session:

Field	Description
`human_author_id`	User ID of the human user
`human_author_name`	Name of the human user
`human_author_username`	Username of the human user

When a session is authenticated with a human user's own token, the human user is the event author and the human_author_* fields are not added.