gitlab·Jan 14, 2026Original article

Introduction to GitLab Duo Agent Platform (opens in new tab)

GitLab Duo Agent Platform introduces an AI orchestration layer designed to move beyond simple code generation into full software development lifecycle (SDLC) automation. By utilizing specialized agents and asynchronous flows, the platform enables teams to delegate complex tasks like code reviews and pipeline fixes to AI "team members" who possess full context of the project. This transition from linear workflows to multi-agent collaboration allows developers to maintain oversight through detailed session logs while focusing on high-level innovation. ### Core Functionality and SDLC Context * The platform acts as an orchestration layer that enables asynchronous collaboration between human developers and specialized AI agents. * It utilizes deep SDLC context, pulling data from issues, epics, merge requests, CI/CD logs, wikis, and security scans to inform AI actions. * Automation is designed to understand and adhere to specific organizational standards, practices, and compliance requirements. ### Agent Interaction and Interface Methods * **GitLab Duo Agentic Chat:** Provides a real-time, synchronous interface via a persistent panel in both the GitLab Web UI and supported IDEs. * **Triggered Foundational Flows:** Users can invoke pre-built GitLab workflows, such as "Fix CI/CD Pipeline" or "Convert Jenkins to GitLab CI/CD," directly within the platform. * **Custom and External Flows:** Automated workflows can be triggered asynchronously by @mentioning agents or assigning reviewers in issue and merge request comments. * **External Agent Support:** The platform supports third-party models like Claude Code and OpenAI Codex, executing them on GitLab platform compute via runner execution. ### Distinguishing Agents from Flows * **Agents:** These are specialized assistants defined by unique system prompts and toolsets; they are best suited for interactive tasks and instant feedback within the chat interface. * **Flows:** These are autonomous, multi-step workflows designed for complex background tasks, such as multi-file refactoring or event-driven automation. * **Execution Environment:** While agents are interactive, flows run asynchronously on platform compute, triggered by specific GitLab events or user assignments. ### Platform Management and Transparency * **AI Catalog:** A centralized library for discovering, creating, and sharing custom agents and flows across an entire organization. * **Automate Hub:** A management center used to configure triggers, monitor active flows, and manage agent permissions. * *Sessions:** Every interaction creates a session log that provides a transparent "decision trail," including agent reasoning, tool calls, and pipeline execution status. * **Model Selection:** Starting with GitLab 18.4, users can select specific foundational models for their conversations within the Web UI to better suit the task at hand. Teams looking to implement the GitLab Duo Agent Platform should begin by utilizing foundational flows for common tasks like pipeline debugging before moving toward custom agent creation. Reviewing the transparency logs in the "Sessions" view is highly recommended to refine agent prompts and ensure that automated actions align with internal development standards.

Asynchronous CollaborationGitlab Duo Agent PlatformDeveloper ToolsEvent Driven Automation+4

figma·Feb 22, 2023·2 min readCurated summary

Can design make work, work? | Figma Blog

The post argues that people managers should redesign their work rather than accept today’s overloaded, meeting-heavy norms. By reclaiming time, making feedback visible earlier, and creating better asynchronous collaboration practices, managers can help teams work with more focus and flexibility. The central recommendation is to question existing routines and deliberately build a more effective future of work. ## Reclaim Time by Reducing Meetings - Shopify began 2023 by eliminating recurring meetings with more than three participants, later restoring only the most essential ones. - The goal was to protect uninterrupted time for independent work, especially in a fully remote organization spanning multiple time zones. - Asynchronous collaboration through tools such as Figma and FigJam allows people to contribute when they are available. - Managers should examine how they actually spend their days and compare that with what leadership expects them to do. - Collaboration tools, visual planning, and brainstorming can replace some meetings—or make remaining meetings more focused on relationships, shared values, and team culture. ## Make Feedback Cycles More Manageable - Sharing early drafts helps prevent late-stage “swoop and poop” feedback from stakeholders. - Posting screenshots or work-in-progress material in FigJam lets colleagues annotate, add sticky notes, and react with emojis without interrupting the team’s workflow. - Early visibility creates a manageable feedback loop rather than requiring the team to respond to every comment immediately. - Visual brainstorming also documents decisions and makes collaboration easier to revisit. - Teams benefit from repeatable processes, but they also need structured opportunities to identify what is not working. - At Super, anonymous suggestions during monthly retrospectives led to operational improvements, including a new bug-reporting system and short weekly sessions for testing new features. Managers can improve team performance by removing unnecessary meetings, shifting more work asynchronously, and inviting feedback early and continuously. The broader lesson is to treat management practices as redesignable systems rather than fixed workplace traditions.

Read original(opens in new tab)

Asynchronous CollaborationFigmaFigjamRemote Work+2