GitLab 19.5 brings more control over AI coding agents
In brief
According to InfoQ, GitLab released version 19.5 on 15 October. The release makes the GitLab MCP server generally available, so compatible tools such as Claude Code and Cursor can reach GitLab's tool catalogue. GitLab also adds controls so teams can see which agents are used, by whom, and against which projects.
Source : InfoQ - « GitLab 19.5 Makes Agentic Development a Governed Part of the DevOps Platform »
What it changes for an SME
If you do not use GitLab for software development, nothing changes for you. If your developers already use it with AI assistants, version 19.5 is mainly about risk and control, according to GitLab: you can limit which functions agents can reach, record who used which agent on which project and when, and stream those traces to a SIEM. Auto mode, disabled by default, can save developers time but also reduces human approval of each action. The generally available Secrets Manager ties credentials to existing permissions and generates audit events.
What you can do
- Ask your team whether it already uses Cursor, Claude Code or Codex with GitLab.
- If you are on GitLab 19.5, have someone check which tools agents can call and who can enable auto mode.
- Confirm that agent sessions and secret use leave audit trails you can review.
Let's talk about the time you could save.
In 20 minutes, we find where AI could save you time or money. Free, no commitment.