Connect repos from groups and subgroups, see merge requests and GitLab CI alongside everything else — and let your own AI agents work straight from the ticket, cloud or self-hosted.
From connecting a repo to merging an MR — GitLab is a first-class provider.
Link a GitLab repo to a board — in both the new-project and connect-existing-project flows. The integrations list stays in sync with your connection state.
Deeply nested project paths work too. Spedy accepts full GitLab subgroup paths when connecting a repo, so your org structure just maps over.
Not only gitlab.com — connect your own self-hosted GitLab. Spedy detects the instance from the clone URL and links MRs and pipelines accordingly.
GitLab merge requests show up in the same Pull Requests view as GitHub and Bitbucket — with state, branch, reviews and CI.
GitLab CI runs flow into the provider-agnostic Pipelines dashboard, grouped by status next to every other CI system.
Open the ticket in Claude Code, Codex or Cursor — branch name and GitLab repo are prefilled, so the agent starts in the right code.
Repos, merge requests, pipelines — and your agents in the middle of it.
Track and review MRs in the unified Pull Requests view, with live state and CI status.
Pipeline runs land in the Pipelines dashboard, grouped by status across every provider.
Full subgroup paths are supported, so deeply nested GitLab structures connect cleanly.
Connect gitlab.com or your own instance — Spedy adapts to the clone URL.
Connect a GitLab repo and hand the ticket to your agent: it gets the repo, a branch name and the context, opens the merge request — and that lands back on the ticket, linked. The same flow you get on GitHub.
20 minutes, no slides: create the board, attach a budget, the agent opens the PR. Then you decide.