An AI coworker for GitLab, in Slack.

What Doozy can do in GitLab

Doozy reads projects, issues, merge requests and pipelines on gitlab.com, and opens issues or comments when you ask. Tools GitLab marks as destructive start off. GitLab's own server provides the tools, so what Doozy can do there is what GitLab offers and grows as they add to it. Each tool has a switch in Doozy.

• Search projects, issues, merge requests and code
• Read a merge request with its diffs, discussions and approvals
• Read pipelines, jobs and job logs
• Read files, branches, commits, tags and releases
• Open an issue or work item, and update one
• Comment on an issue or merge request

Things people ask

In a thread, after @Doozy. It answers in that thread, with what it did.

• You

  @Doozy why did the last pipeline on main fail? Show me the failing job's log.

• You

  @Doozy open a GitLab issue in `web` for this bug, labeled `bug`, and link it here.

• You

  @Doozy which merge requests have waited more than two days for review?

• You

  @Doozy every morning at 9, post yesterday's failed pipelines on the default branch.

How to connect GitLab

No keys to paste: GitLab asks you to approve Doozy, the way it does for any app, and you can revoke that there any time.

1. 1

   Add Doozy to your Slack and open the Integrations page in the web app.

2. 2

   Pick GitLab and click Connect. GitLab's own sign-in asks you to approve Doozy.

3. 3

   Choose which of its tools Doozy may use, and mention @Doozy in a thread.

What stays off, and what's always true

Doozy works like a teammate, so it doesn't stop to ask. You decide what it can reach.

More in Security and AI & Data Use.

Works well with

One ask often crosses tools: a Sentry error becomes a GitHub pull request and a Linear issue. Doozy uses whichever it needs.

• GitHubRead code, issues and CI, and open pull requests from branches of its own.
• SentryLook into errors, stack traces and releases.
• LinearFind, create and update issues, projects and cycles.
• SlackWhere Doozy works: mention it in a thread and the result comes back there.

Questions people ask before they connect GitLab

Does it work with self-managed GitLab?

Doozy connects to GitLab's MCP server on gitlab.com. For a self-managed or Dedicated instance, add that instance's own MCP address as a server.

Does GitLab need anything switched on first?

Yes. On gitlab.com, MCP server access has to be allowed for the top-level group. GitLab's MCP server is available on Free, Premium and Ultimate.

Can Doozy see our GitLab credentials?

No. Every task runs in its own isolated workspace, and credentials stay outside it: they're added to each call on its way out. Nothing it reads or writes there can expose a key.

Will it change things in GitLab without asking?

It works like a teammate, so it doesn't stop to ask, and you decide what it can reach. Tools that delete or overwrite start switched off, you can switch off any other, and every action it takes is on the audit log with who asked.

Who can connect it?

Owners and admins of your Doozy workspace. Members see what's connected and can't change it. Everyone in your Slack can ask Doozy once it's connected.

What does it cost?

Nothing extra. Every integration is included on every plan, and the 14-day trial needs no card.

Something else? Write to [email protected].