GitLab AI Hackathon 2026

GitLab Atlas

100% GitLab Duo Agent Platform Native — Zero Config, Zero API Keys

Your repo has code. Atlas gives it a voice — with 6 artifacts, Mermaid + PlantUML diagrams, and drift governance.

Works with any GitLab repository. No API keys needed — powered by GitLab Duo natively.

See What Atlas Adds to Your Repo

One mention generates 6 architecture artifacts with Mermaid and PlantUML diagrams.

Before

Undocumented Repository

my-project/
  README.md -- "TODO: add docs"
  src/
    main.py
    utils.py
    config.py
  No architecture docs
  No diagrams
  No tech stack info
😦 New developers: "Where do I start?"
After Atlas

Atlas-Powered Repository

my-project/
  README.md + architecture section
  src/ ...
  docs/atlas/
    TECH_STACK.md
    ARCHITECTURE.md + ambiguities & improvements
    DATA_FLOW.mmd Mermaid
    DEPLOYMENT_BOARD.puml PlantUML
    SEQUENCE_FLOW.puml PlantUML
👍 6 artifacts — living architecture, always current

See Atlas Get Enabled Right Inside GitLab

Instead of reading menu instructions, watch the real path: open AI Catalog, switch to Flows, and select Atlas for your project.

gitlab.com / twoweeks / vibeVoice
Autoplay demo
Project
V
vibeVoice TwoWeeks
Project home
Automate
Agents
Flows
Triggers
Sessions
MCP servers
TwoWeeks/vibeVoice/Project

vibeVoice

Voice-powered AI companion — Atlas demo target project

main
Code
Start from the repository itself, then open Automate and enter Flows just like the real GitLab path.
AGENTS.mdfeat(atlas): install Atlas architecture...18 hours ago
flows/fix: use feature branch + MR pattern...17 hours ago
README.mddocs: update README with voice li...6 days ago
Flows
New flow
Enabled
Managed
AI Catalog

Atlas Refresh

Refreshes repository architecture artifacts after merge or pipeline events

Visibility: Public Updated 16 hours ago

Atlas Navigator

Explains MR changes and detects architecture drift with visual diagrams

Visibility: Public Updated 11 hours ago

Atlas Bootstrap

Generates living architecture baseline for any repository

Updated 17 seconds ago Public

Atlas Bootstrap

Beta Updated 17 seconds ago by gitlab-ai-hackathon/participants v1.15.0

Generates living architecture baseline for any repository

Enable

Visibility & access

Managed by GitLab AI Hackathon / Participants / sejun1

Public

Service account

Atlas Bootstrap @ai-atlas-bootstrap-twoweeks View projects and permissions of this service account

Configuration

Mention Assign Assign reviewer
config.yaml
1  version: v1
2  environment: ambient
3  components:
4    - name: analyzer
5      type: AgentComponent
6    - name: generator
7      toolset: create_file_with_contents
8    - name: validator
Homepage demo mode

Show the actual GitLab flow path, not a generic catalog mock.

This mirrors your real screenshots: project home, Automate, Flows, AI Catalog search, Atlas results, and the Bootstrap detail page with Enable visible.

1
Enter from the repoStart on the actual project so the GitLab context feels instantly familiar.
2
Search for AtlasUse the real AI Catalog flow list and surface Refresh, Navigator, and Bootstrap as separate results.
3
Stop at EnableLand on the Bootstrap detail page so the CTA matches what users will actually click.

Up and Running in 3 Steps

No code changes. No API keys. Published to AI Catalog — any project can enable.

1

Enable from AI Catalog

Find Atlas flows in the GitLab AI Catalog and enable them for your project. No fork needed.

AI Catalog → Atlas → Enable
2

Mention in Issue or MR

Trigger any Atlas flow by mentioning it in an issue or merge request comment.

@ai-atlas-bootstrap-{group}
3

Review the MR

Atlas creates a feature branch, generates 6 artifacts, and opens a merge request for your review.

Branch + MR → Review → Merge

Enable Atlas on Your Project

Follow these steps in the GitLab UI to enable Atlas flows on any project.

1

Enable Duo Agent Platform

Group-Level · One-Time
  1. Navigate to your group's Settings → GitLab Duo
  2. Select Change configuration
  3. Toggle "Turn on GitLab Duo Chat (agentic), agents, and flows"
Requires Group Owner role and GitLab Premium or Ultimate subscription.
2

Enable Flows from AI Catalog

Project-Level
  1. Go to your project → Automate → Flows in the sidebar
  2. Select Enable flow from group (upper-right button)
  3. Choose "Atlas Bootstrap" and set triggers: Mention + Assign
  4. Repeat for "Atlas Navigator" and "Atlas Refresh"
3

Configure Runners

If Self-Managed
  1. Flows require runners with the gitlab--duo tag
  2. On GitLab.com SaaS: hosted runners work automatically
  3. Self-managed: assign runners with docker executor to the top-level group
GitLab.com users can skip this step — hosted runners are pre-configured.
4

Trigger Atlas

Ready to Go
  1. In an Issue: @ai-atlas-bootstrap-{group} bootstrap
  2. In an MR: @ai-atlas-navigator-{group} explain
  3. Results appear as comments with rendered diagrams
Replace {group} with your top-level GitLab group name.

Three Agent Flows, One Architecture

Each flow is a GitLab Duo Agent Platform workflow published to the AI Catalog.

@ai-atlas-bootstrap-{group}

Atlas Bootstrap

Analyzer → Generator → Validator (3-component flow). Scans your repo, reads key files, generates 6 architecture artifacts (TECH_STACK, ARCHITECTURE with ambiguities & improvements, DATA_FLOW Mermaid, 2 PlantUML diagrams, README section), and creates a merge request.

TECH_STACK.mdARCHITECTURE.mdDATA_FLOW.mmd2x PlantUMLREADME
@ai-atlas-navigator-{group}

Atlas Navigator

Explains MR changes with before/after diagrams, detects drift with governance decisions (allow / warn / require_docs_update / require_follow_up), and auto-creates follow-up issues for high-severity drift.

Before/After DiagramsDrift GovernanceAuto Follow-up IssuesMR Comments
Post-Merge Trigger

Atlas Refresh

Automatically updates architecture documentation after merge to keep the baseline current. Creates a new MR with refreshed artifacts so your docs are never stale.

Auto-RefreshAlways CurrentFeature Branch + MRZero Maintenance
dashboard.atlas

Web Dashboard

GitLab OAuth login, project list with one-click Bootstrap, Architecture Artifact Browser (renders Mermaid + Markdown in browser), and Atlas Status Panel with 4 health checks (flows, service account, docs, CI).

One-Click BootstrapArtifact Browser4-Check Status PanelGitLab OAuth

Real Output from a Real Project

Atlas ran on vibeVoice — here is what it produced.

Bootstrap Output

6 architecture artifacts generated

  • MD TECH_STACK.md Languages, frameworks, deps
  • MD ARCHITECTURE.md Design + ambiguities + improvements
  • MMD DATA_FLOW.mmd Data flow diagram
  • PUML DEPLOYMENT_BOARD.puml Infrastructure topology
  • PUML SEQUENCE_FLOW.puml Request sequence diagram
  • MD README.md Architecture section injected
System architecture diagram for vibeVoice showing Browser frontend, Next.js server with auth and API proxy layer, and MiniMax API services with T2A and Voice Library components

DEPLOYMENT_BOARD.puml — rendered from actual Atlas output on vibeVoice

Generated by Atlas on vibeVoice

Navigator Analysis

MR comment posted by Atlas Navigator

Atlas Navigator commented on !3 · vibeVoice

Architecture Change Analysis

This MR introduces significant architectural changes across multiple system layers.

Change categories and their governance actions detected by Atlas Navigator
Category Changes Severity
Architecture New API proxy layer, auth middleware High
API 3 new endpoints (t2a, voices, voice-design) High
UI Voice library panel, audio player Medium
Infrastructure MiniMax API integration, session cookies Medium
Governance Decision: require_docs_update — Architecture documentation must be updated to reflect the new proxy pattern and external API integration.
Generated by Atlas on vibeVoice

Duo Agent Platform Architecture

Pattern B — create_file_with_contents + run_git_command. Feature branches and MRs, never direct main commits.

1

AI Catalog (Public)

Published flows — any GitLab project can discover and enable Atlas agent flows

2

Duo Agent Platform Flows

Bootstrap / Navigator / Refresh — triggered via @mention in issues or MRs

3

Analyzer → Generator → Validator

Claude Sonnet 4.5 Vertex — 3-component flow: analyze codebase, generate artifacts, validate output

4

Dual Diagram Engine

Mermaid (data flow) + PlantUML (deployment, sequence) — rendered inline in MR descriptions and GitLab UI

5

Web Dashboard

FastAPI + Jinja2 on Cloud Run — Architecture browser, status panel, OAuth login

Atlas at a Glance

Any GitLab project can enable Atlas flows from the AI Catalog and generate living architecture docs.

0
Architecture Artifacts Generated
0
Diagram Engines (Mermaid + PlantUML)
0
Agent Flows (Bootstrap, Navigator, Refresh)
0
API Keys Required

Technology Stack

100% GitLab-native. Default LLM managed by GitLab — no external APIs, no configuration needed.

Claude Sonnet 4.5 (Vertex)
GitLab Duo Agent Platform
Mermaid Diagrams
PlantUML Diagrams
FastAPI + Jinja2
GitLab CI/CD
Google Cloud Run

Frequently Asked Questions

Common questions about Atlas setup, compatibility, and usage.

Which GitLab plans support Atlas?
Atlas requires GitLab Premium or Ultimate with the Duo Agent Platform enabled. The AI Catalog and Duo flows are available on both GitLab.com (SaaS) and self-managed instances running GitLab 17.x or later.
Does Atlas work on self-managed GitLab instances?
Yes. You need runners with the gitlab--duo tag assigned to your top-level group with a docker executor. On GitLab.com SaaS, hosted runners are pre-configured and work automatically.
Which programming languages are supported?
Atlas is language-agnostic. It analyzes your repository structure, configuration files, and source code regardless of language. The AI model reads and understands code in all major programming languages and frameworks.
Will Atlas overwrite my existing documentation?
No. Atlas creates its artifacts in a dedicated docs/atlas/ directory and opens a merge request for your review. Your existing files are never modified without explicit approval through the MR process.
Is there any additional cost?
Atlas uses the LLM provided by GitLab Duo (Claude Sonnet via Vertex) at no extra charge beyond your existing GitLab subscription. No external API keys or third-party services are required.