Sanaf AI
Start free
Developer Tools

GitLab, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your GitLab account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Developer Tools
  • Signs in to your account
  • 53 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What GitLab is

A web-based DevOps lifecycle tool that provides a Git repository manager providing wiki, issue-tracking, and CI/CD pipeline features.

You sign in with your own GitLab account, the same way you already do. We never see or hold your password.

How a run works

One message in, the work done in GitLab.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in GitLab. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own GitLab account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

53 tools it already has

What it can do in GitLab

These are the ready-made tools your AI employee already has in GitLab. It is not limited to them, but it never has to be taught these.

  • Archive ProjectTool to archive a project. use when you need to mark a project read-only after finishing active development. call after confirming no further changes are required.
  • Create GitLab GroupTool to create a new group in gitlab. use when you need to establish a new group for projects or collaboration.
  • Create ProjectTool to create a new project in gitlab. implements post /projects endpoint.
  • Create Project IssueTool to create a new issue in a gitlab project. use when you need to report a bug, request a feature, or track a task within a specific project.
  • Create Repository BranchTool to create a new branch in a project. use when you need to create a new branch from an existing branch or a specific commit in a gitlab project.
  • Create Support PINTool to create a support pin for your authenticated user. use when gitlab support requests a pin to verify your identity.
  • Delete ProjectTool to delete a gitlab project by its id. use when you need to remove a project, either by marking it for later deletion or deleting it immediately.
  • Download Project AvatarTool to download a project’s avatar image. use when you need the raw avatar bytes after confirming the project exists.
  • Erase JobTool to erase the content of a specified job within a project. use when you need to remove job artifacts and logs.
  • Get Commit ReferencesTool to get all references (branches or tags) a commit is pushed to. use when you need to find out which branches or tags a specific commit belongs to in a gitlab project.
  • Get Commit SequenceTool to get the sequence number of a commit in a project by following parent links from the given commit. use when you need to determine the order of a commit in the project's hist
  • Get Group DetailsTool to retrieve information about a specific group by its id. use when you need to get details of a gitlab group.
  • Get Group MemberTool to retrieve details for a specific group member. use when you need to fetch membership information for a user in a group after you know both group id and user id.
  • Get GroupsGet groups
  • Get Job DetailsTool to retrieve details of a single job by its id within a specified project. use this when you need to fetch specific information about a particular ci/cd job.
  • Get Merge Request CommitsTool to get commits of a merge request. use when you need to retrieve all commits associated with a specific merge request.
  • Get Merge Request NotesTool to fetch comments on a merge request. use when you need to retrieve all notes for a specific merge request.
  • Get ProjectTool to get a single project by id or url-encoded path.
  • Get Project LanguagesTool to list programming languages used in a project with percentages. use when you need the project language breakdown.
  • Get Project MemberTool to retrieve details for a specific project member. use after confirming project and user ids to fetch membership information for a project member.
  • Get Project Member AllTool to retrieve details for a specific project member (including inherited and invited members). use when you need the effective membership info (including invitations and inherit
  • Get Project Merge RequestsTool to retrieve a list of merge requests for a specific project. use when you need to get all merge requests associated with a project, with options to filter by state, labels, mi
  • Get ProjectsTool to list all projects accessible to the authenticated user. supports filtering.
  • Get Repository BranchTool to retrieve information about a specific branch in a project. use when you need to get details for a single branch.
  • Get Repository BranchesRetrieves a list of repository branches for a project. use this when you need to get all branches or search for specific branches within a gitlab project.
  • Get Single CommitTool to get a specific commit identified by the commit hash or name of a branch or tag. use this when you need to retrieve detailed information about a single commit in a gitlab pr
  • Get Single PipelineTool to retrieve details of a single pipeline by its id within a specified project. use when you need to get information about a specific ci/cd pipeline.
  • Get UserTool to retrieve information about a specific user by their id. use when you need to fetch details for a single gitlab user.
  • Get User PreferencesTool to get the current user's preferences. use when you need to retrieve the user's diff display and ci identity jwt settings after authentication.
  • Get User StatusTool to get a user's status by id. use when you need to retrieve a gitlab user's current status message, emoji, and availability after identifying their user id.
  • Get User Support PINTool to get details of the current user's support pin. use when you need to retrieve the active support pin and its expiration for the authenticated user.
  • Get UsersTool to retrieve a list of users from gitlab. use this when you need to find user information, search for specific users, or filter users based on various criteria like activity st
  • Import project membersTool to import members from one project to another. use when migrating members between projects.
  • List All Group MembersTool to list all members of a group including direct, inherited, and invited members. use when you need a comprehensive membership list beyond direct members.
  • List All Project MembersTool to list all members of a project (direct, inherited, invited). use when you need the effective membership list including inherited and invited members.
  • List Billable Group MembersTool to list billable members of a top-level group (including its subgroups and projects). use when generating billing reports; requires owner role on the group.
  • List Group MembersTool to list direct members of a group. use when you need to retrieve or filter a group's direct membership.
  • List Merge Request DiffsTool to list all diff versions of a merge request. use when you need to inspect changes across different diff versions after creating or updating a merge request.
  • List Pending Group MembersTool to list pending members of a group and its subgroups and projects. use when you need to review users awaiting approval or invited without an account. call after confirming the
  • List Pipeline JobsTool to retrieve a list of jobs for a specified pipeline within a project. use this when you need to inspect the status or details of jobs associated with a particular ci/cd pipeli
  • List Project GroupsTool to list ancestor groups of a project. use when you need to retrieve all groups a project belongs to or is shared with.
  • List Project Invited GroupsTool to list groups invited to a project. use when auditing which groups have access to a project.
  • List Project PipelinesTool to retrieve a list of pipelines for a specified project. use when you need to get information about ci/cd pipelines, such as their status, source, or creation/update times.
  • List Project Repository TagsTool to retrieve a list of repository tags for a specified project. use when you need to get all tags associated with a project in gitlab.
  • List Project Shareable GroupsTool to list groups that can be shared with a project. use before sharing a project to fetch eligible groups.
  • List Project Transfer LocationsTool to list namespaces available for project transfer. use when you need to determine which groups a project can be transferred into.
  • List project usersTool to list users of a project. use after you have a project id and want to retrieve its users.
  • List Repository CommitsTool to get a list of repository commits in a project. use when you need to retrieve commit history for a specific project, branch, or time range.
  • List User ProjectsTool to list projects owned by a specific user. use after obtaining target user identity to fetch owned projects.
  • Set User StatusTool to set the current user's status. use when you need to update availability or convey current mood on gitlab.
  • Share Project With GroupTool to share a project with a group. use when you need to grant a group specific access level to a project.
  • Start Housekeeping TaskTool to start the housekeeping task for a project. use when you need to trigger manual maintenance or pruning on a repository.
  • Update User PreferencesTool to update the current user's preferences. use when adjusting default diff viewing and ci identity settings.
Access, and who is in charge of it

You stay the boss of your GitLab account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own GitLab account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in GitLab is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in GitLab and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about GitLab

Can an AI employee really work inside GitLab?
Yes. It signs in to your own GitLab account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of GitLab?
No. Nothing moves and nothing is replaced. Your records stay in GitLab, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my GitLab account?
You sign in with your own GitLab account, the same way you already do. We never see or hold your password. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in GitLab?
It has 53 ready-made tools in GitLab today, among them Archive Project, Create GitLab Group and Create Project. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use GitLab and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in GitLab and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in GitLab?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in GitLab is written down with what it did and when.