Skip to content

Mate documentation

Assign an issue. Mate does the work.

Mate is a GitLab-native agent orchestrator. You add a managed GitLab account to your project, assign it to an issue or MR, ask it for a review, mention it in a comment, or let it watch for failed pipelines — and Mate spawns an LLM-driven agent in an isolated container. The agent reads the context, pushes branches, opens merge requests, creates and updates issues and reports back as GitLab comments, within the permissions you grant. It never holds your GitLab credentials.

Mate is currently in closed beta. A limited number of workspaces are admitted from the waitlist as capacity becomes available. If you do not have an invitation, sign in at platform.mate.engineer and try to create a workspace; if the cap is reached you will be placed in the queue.

Set up your first mate

A step-by-step walkthrough: create a workspace, then work through the setup checklist (GitLab URL, managed account, LLM key, agent and trigger, webhook, subscription) and trigger your first job.

Start the walkthrough →

Reference

Concepts, trigger configuration, permissions, models, security, pricing, and troubleshooting.

Browse the reference →

  • A managed account is a real GitLab user you register with Mate. Every action the agent takes appears under that user’s name.
  • You trigger the agent by assigning the account to an issue or MR, requesting its review, mentioning it in a comment, or letting it watch for pipeline failures. Triggers are configured for the whole workspace in the console, or per repository in .mate.yml.
  • Billing is per mate: each paid mate is one concurrent job slot. Without a subscription Mate runs no jobs.
  • Each trigger spawns a job: an isolated container with the agent runtime, a short-lived clone token, and scoped GitLab permissions. The container is destroyed after the job finishes.
  • The agent works through a permission-gated GitLab tool service: reading, commenting, pushing branches, opening and merging MRs, updating issues and touching CI, as far as you grant. Approving MRs (approve_mr) is opt-in and off by default. A mate can also create issues and assign or @-mention itself to continue work; that starts a new job.

These docs cover the hosted Mate service (running on platform.mate.engineer). The on-prem edition — for running Mate on your own hardware — has separate installation and operations documentation that is delivered together with the on-prem release.