GitLab, without leaving the thread.
Ask what is blocking the release, read the diff, retry the pipeline. Cedric proposes each change in GitLab and waits for your yes.
$50 in free credits when you sign up. No card needed.
- The state of the work lives in GitLab; the questions about it are asked in the channel.
- Ask in plain words: open merge requests waiting on review, the issues labeled bug on one milestone, what failed on main this morning.
- Cedric reads a merge request's changes and discussions, leaves the comment, and can merge or close it on your yes.
- Pipelines and jobs can be checked for a branch or a merge request, and retried or cancelled from the thread.
- Cedric sees only what your account can access, and merging, committing or closing work is confirmed before it runs.
What can a GitLab AI agent do?
Most of what a team asks about GitLab is where something stands. A GitLab AI agent searches and browses projects, groups and repository files, reads a file's contents on a specific branch, and reads commit history and diffs. It checks pipeline and job status for a branch or a merge request, so "is main green" gets an answer with the failing job named. It also reads snippets, todos and the activity worth noticing across the projects you can access.
Then it moves the work, with a proposal first. Cedric creates, updates, comments on, labels, assigns and closes issues. It opens merge requests, reviews their changes and discussions, leaves comments, and merges or closes them. It creates branches and commits file changes, and retries or cancels pipeline runs. That is what lets AI project management reach the code: the decision in the thread becomes the issue, the label and the assignee without a tab switch.
The rest of the project is reachable too: milestones, labels, wiki pages and releases, plus project members, access levels and invitations. Everything is limited to what your account can access, and GitLab's rate limits apply as they would to any client. Writes that change shared work, merging, committing or closing, are confirmed before they run.
Release morning
Two merge requests, one red pipeline, one retry.
Aisha Rahman9:14 AM
@Cedric what's still open for the 3.2 milestone, and why is the pipeline red on the billing MR? Retry it if it's just the flaky test.
CedricAPP9:15 AM
Milestone 3.2: 2 merge requests open. !412 "Billing: proration on plan change" (Jonas, 2 approvals, pipeline failed) and !418 "Invoice PDF footer" (Mei, waiting on review, pipeline passed). On !412 the failed job is test:integration, the same timeout in billing_spec.rb:88 that failed and passed on retry twice this week; no other job failed. Proposed: retry the pipeline on !412. If it passes, !412 has its approvals and can be merged; I will ask separately for that.
Looked up
Projects, groups, files on a branch, commit history and diffs, and the issues and merge requests across everything you can access.
Reviewed
A merge request's changes and discussions read in the thread, with the comment drafted and the merge or close on your yes.
Checked
Pipeline and job status for a branch or a merge request, with a retry or a cancel proposed when a run fails.
Connect GitLab in a minute
No setup project, no workflow builder, no field mapping. The flow is the same for every tool Cedric connects to.
- 01
Install Cedric where your team talks
One click. It joins your Slack like any other member, and everyone shares the same Cedric.
- 02
Connect GitLab from the dashboard
Open the Integrations page and sign in with GitLab on its own screen. Cedric never sees or stores your password, and you can revoke the connection in one click at any time.
A fresh connection can look but not touch: read-only until you say otherwise.
- 03
Ask in plain words
Back in the channel, try it: "what is still open for this milestone?". You describe the outcome; Cedric picks the GitLab actions the ask needs. There is nothing to configure.
Connect for the whole workspace so the team shares it, or keep the connection personal. Two accounts are fine too; each gets a short name.
- 04
Let it become routine
Schedule the recurring version of the ask, and let Cedric fold GitLab into bigger jobs that cross your other tools. Anything that would leave your workspace still comes back as a preview to approve first.
Better in company
A bug that starts in a customer email ends in GitLab: pair it with Gmail and Cedric reads the report, files the issue with the details, and drafts the reply when the fix merges. If the roadmap lives in Linear, it reads both and says which is behind.
Release notes belong in Notion: ask for what merged since the last tag and Cedric drafts the page from the merge requests and commits. A Google Sheets tab can hold the pipeline pass rate week by week.
Where the limits are
GitLab is a catalog connection, not a built-in playbook. Cedric works from what the GitLab connection can read and do; ask in plain words and it says what it can reach there, and what it cannot.
Your access is the ceiling. Cedric sees and changes only what your GitLab account can, and GitLab's rate limits apply, so a search across many groups is paged rather than pulled at once.
Merging, committing and closing are confirmed. Each write that changes shared work is proposed with the target named, the merge request, the branch or the issue, and waits for your yes.
Cedric sees what the GitLab connection grants and nothing more. Access is scoped, logged, and revocable from the dashboard, effective immediately.
Nothing sends itself. An email, a post, a change to a record: anything with consequences comes back as a preview for a human yes. That is the design, not a beta caveat.
FAQ
Yes. GitLab is one of the 3,200+ apps in Cedric's catalog: connect it once from the dashboard, on GitLab's own sign-in screen, and ask in plain words. There is no built-in playbook for it, so Cedric works from what the connection can read and do, and tells you when something is out of reach.
Yes, on your yes. It reads the changes, the discussions and the pipeline status, tells you whether the approvals are in, and proposes the merge; nothing merges until you approve.
It can create a branch and commit file changes, and it reads file contents on any branch first. Every commit is proposed with the branch and the change named, so a fix drafted in the thread lands where you say it should.
Connect it for the whole workspace and everyone shares it, with one person authorising once. A connection you would rather not share, a personal inbox for instance, can stay personal to you.
Yes, and it starts that way: a fresh connection can look but not touch until you say otherwise. Even with write access granted, anything that changes or sends waits for an approval.
Every workspace starts with $50 in credits, free, no card. Each task consumes credits in proportion to the work involved. See pricing for the plans.
Connect GitLab in a minute.
Ask what is open on the current milestone, then let it retry the next red pipeline.
100K credits ($50) on sign up. No card needed.