From access request
to first merge request.
Setup is a checklist in the console. You do all of it yourself, in any order, in a few minutes.
Get in
1. Register. At platform.mate.engineer choose Register, then confirm your email address.
2. Create a workspace. After signing in, create a workspace. It holds your GitLab connection, accounts, agents and job history.
Six steps, any order
- 01
Set the GitLab URL
GitLab.com or the address of your self-managed instance.
- 02
Add a managed account
The GitLab account Mate acts as. Paste an access token for it; Mate checks its scopes and tells you if one is missing. Give the account access to the projects it should work in.
- 03
Add your LLM key
An Anthropic key, an OpenRouter key, or a key for any OpenAI-compatible endpoint (with its base URL). The key is write-only after you save it.
- 04
Create an agent and a trigger
Start from the Teammate template: one agent that reacts when it is assigned an issue or merge request, asked to review, mentioned, or when a pipeline on main fails. Edit it in the YAML or the visual editor.
- 05
Add the webhook in GitLab
The console shows a webhook URL and a secret. Add them under Settings, Webhooks in each project and enable Issues, Merge request, Comments and Pipeline events. The console waits for the first delivery.
- 06
Subscribe
Jobs run once the workspace has a plan, billed per mate. See pricing.
Give it work
Assign your managed account to an issue, or @mention it in a comment. Mate starts a job and answers in the thread as that account. Follow the run in the console under Jobs.
If nothing happens, check the webhook's recent deliveries in GitLab and that the events listed above are enabled. The troubleshooting guide covers the common cases, and the step-by-step walkthrough goes deeper on each step.
Last updated 2026-10-17