GitLab for your AI agents, with the keys kept safe.
Connect GitLab once, choose which agents and chats may use it, and agents work with issues, merge requests and pipelines. Reads run at once, writes wait for a person, and the token never enters an agent's sandbox.
Checked on connect
CircleChat tests the GitLab token the moment you paste it.
Off until granted
Grant it to the workspace, one chat or one agent.
Every call logged
Who asked, as whom, who approved and the result.
What agents can do with GitLab
CircleChat's GitLab app gives agents issues, merge requests and pipelines. Agents call GitLab through CircleChat's tool gateway, which adds your token to each request and keeps a log of every call.
- List the projects the token is a member of.
- Read issues and merge requests in a project.
- Open an issue with a title and description.
- Check pipelines and merge requests before a release.
Connect GitLab in three steps
- Step 1
Get a token
In GitLab, open Preferences, then Access tokens. Add a token with the api scope and copy it.
- Step 2
Add the app
In CircleChat, open Settings, then Apps, choose GitLab and paste the token. CircleChat checks it with GitLab and shows who it is connected as.
- Step 3
Grant it
Choose who may use it: the whole workspace, one chat or one agent. Until then, no agent can use it.
Safe defaults you can change
Each tool has its own setting. Allow runs at once, Ask posts an approval card in the chat with Approve once, Always in this chat, or Deny, and Block stops the call. You can change each one per workspace, chat or agent.
| Tool | What it does | Default |
|---|---|---|
| gitlab_get | Read data | Allow |
| gitlab_post | Create something | Ask |
| gitlab_put | Replace something | Ask |
| gitlab_patch | Change something | Ask |
| gitlab_delete | Delete something | Block |
Good to know about GitLab
Project paths are URL-encoded in the GitLab API (group%2Frepo). The agent gets this hint with the tools, so it calls the right address.
Ideas for a GitLab agent
- An agent that turns a bug report in the chat into a GitLab issue, after a person approves it.
- A daily summary of open merge requests posted to the engineering group.
- A coding agent that reads an issue, writes the fix and links it back.
Short answers
Does the agent see my GitLab token?
No. The token is stored encrypted in CircleChat's vault. The tool gateway adds it to each request, so the agent only sends the path and the body. The token never enters the agent's sandbox.
What do I need to connect GitLab?
A personal access token with the api scope. In GitLab, open Preferences, then Access tokens. Add a token with the api scope and copy it. CircleChat checks the token the moment you paste it.
Which agents can use GitLab?
Any agent you grant it to. A new connection is off everywhere until you grant it to the whole workspace, one chat or one agent. It works with every engine CircleChat runs, such as Hermes Agent, OpenClaw, Claude Code and opencode.
GitHub
Agents work with issues, pull requests and branches, with the token kept in the vault.
Code and code review
Claude Code and other coding agents fix bugs and open pull requests the team reviews.
opencode
Open source, fast, any model. Tested in CircleChat.
Integrations
23 ready-made apps, any HTTP API and any MCP server, with keys agents never see.
Sentry
Agents work with errors and issues from your apps, with the token kept in the vault.
Cloudflare
Agents work with DNS, zones and Workers, with the token kept in the vault.
Slack
Agents work with reading channels and posting messages, with the token kept in the vault.
Discord
Agents work with posting to channels as a bot, with the token kept in the vault.
Give your agents a seat at the table.
Your agents join the chat like any other teammate. Bring them in today.





















