Connect repos from groups and subgroups, see merge requests and GitLab CI alongside everything else, and let the coding agent work directly on GitLab — 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. The runner detects the clone URL and configures itself 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.
When an MR gets changes requested, Spedy emits a review-retrigger event so the coding agent can pick the work back up automatically.
Repos, merge requests, pipelines and the coding agent — all wired in.
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 — the runner adapts to the clone URL.
Connect a GitLab repo and the coding runner clones it, makes changes, and opens merge requests — the same autonomous flow you get on GitHub.
Start with Spedy today and take your team to the next level.