How to Connect GitLab to Lookout Private Beta

Connecting GitLab to Lookout allows the agent to explore repositories, propose merge requests, and review incoming changes — for both gitlab.com and self-hosted instances.

Connect GitLab

Only admins can connect GitLab. Once connected, any member can use the repository tools in chat.

See Roles and Permissions for more details.

Connect GitLab from Settings > SCM with a per-workspace access token.

Note that:

• A workspace can hold several connections (one per GitLab instance), so the same project path can exist on multiple instances without collision.
• Each connection stores its own encrypted token.
• Lookout supports both gitlab.com and self-hosted instances.

How it works

Once a GitLab connection is set up, the agent:

• Explores repositories: Browses files, lists commits, searches code, and views merge-request diffs.
• Proposes changes: Authors commits and opens merge requests for review.
• Automates merge-request review: When a merge request is opened or updated, Lookout reviews the diff for breaking data-contract changes and posts its findings as comments. See PR and MR Review for more details.

GitLab integration currently supports chat exploration, agent-proposed merge requests, and automated merge-request review.

Measurement Plan instrumentation — where an approved plan is implemented as pull requests by a background agent — is currently supported for GitHub repositories only.

The agent’s changes always arrive as merge requests — proposals that sit in your normal review process. A human reviews and merges before anything lands.

How changes are attributed

Changes proposed by Lookout are identifiable in your GitLab history:

• Commits carry a Co-authored-by: trailer attributing the change to Lookout.
• Merge requests are labeled created-by::rudder-ai.