GitLab 18.10 brings AI, passkeys and planning
GitLab 18.10 adds agentic AI, passkeys, work items list and saved views. See why the release matters for teams tracking GitLab 18.8 and 18.10.
GitLab 18.10 brings AI, passkeys and planning
GitLab 18.10 is a release that speaks to three pressures we see in many teams across Central Europe and the UK: security, speed, and planning discipline. The headline features are easy to spot, but the real story is how they fit together. GitLab Duo Agent Platform expands to more teams, passkeys reduce sign-in friction, and the new work items list with saved views makes agile planning less repetitive.
For organisations watching searches such as GitLab 18.8 or GitLab credits, this release is also a useful reminder that the platform is moving quickly. People often arrive with a single question about a version number, then discover that the bigger opportunity is to simplify how developers, security specialists, and product owners work together.
What stands out in 18.10
The release notes on about.gitlab.com show a broad set of improvements, but three deserve special attention.
First, agentic AI is becoming more practical. Free GitLab.com teams can purchase GitLab Credits and start using GitLab Duo Agent Platform without having to jump straight into a larger subscription commitment. That lowers the threshold for experimentation and helps smaller teams understand where AI is genuinely useful.
Second, passkeys are a meaningful usability and security upgrade. Passwordless sign-in is not just a trendy feature; it reduces common authentication pain points and can help organisations strengthen access control without making everyday logins more annoying.
Third, the work items list and saved views improve agile planning by letting teams manage different item types in one place and preserve the views they rely on. If you have ever rebuilt the same filters every Monday morning, this change will feel immediately useful.
Why this matters for delivery teams
Many companies have adopted GitLab for source code and CI/CD, but the platform now reaches further into planning, security, and AI-assisted workflows. That matters because the cost of switching between tools is still one of the biggest hidden productivity drains.
This is also where our local consulting practice at gitlab.consulting/en-gb can help. We often see teams start with one feature request, such as better planning views, and then uncover broader needs around governance, rollout strategy, and adoption support.
If your team is comparing versions, the release is worth reading alongside the wider GitLab 18.10 launch material. It gives a better picture of how GitLab is positioning itself as a platform for software delivery rather than just a DevOps toolbox.
Suggested next steps
A practical next step is to review three areas at once: authentication, planning, and AI governance. Ask whether passkeys fit your identity strategy, whether the work items list replaces manual status tracking, and whether the team has a sensible policy for using AI features.
If you want help with GitLab consulting, training, or licence procurement in the Czech Republic, Slovakia, Croatia, Serbia, Slovenia, North Macedonia, or the United Kingdom, get in touch via our contact form and we will help you plan the right next move.
Tags:GitLab 18.10agentic AIpasskeyswork itemssaved views
Other languages:ČeštinaSlovenčinaHrvatskiSrpski (Latinica)