PolderLabs
Contact

Talk directly with an engineer.

Studio
Amsterdam, NL
Visit the contact page
EN
Talk to an engineer

Note · 23 September 2026· 2 min read

How to give AI coding agents useful GitLab context

How oflow turns GitLab work into useful context for coding agents while keeping changes reviewable.

Imagine asking a coding assistant to pick up a task. It can read code, but it may not know which issue matters today, what “done” means, or whether it should change anything in GitLab. That missing context is where a helpful assistant can become a confusing one.

We built oflow to make that handoff less mysterious. It is an open-source command-line tool that reads planning information from GitLab and gives coding agents a compact view of the work. The point is not to let an agent run a team. It is to help one start with the right facts.

A map of the work

A project has more than code. It has issues, acceptance criteria, owners, milestones, merge requests and pipelines. oflow gathers those pieces into focused reports. An agent can see the current story and its related evidence without repeatedly downloading an entire project history. A local SQLite cache makes repeated reads practical.

For a person, the benefit is familiar: less time reconstructing the story behind a task. For an agent, it is also a boundary. A smaller, explicit context is easier to inspect than an enormous prompt full of stale notes.

The important part is the pause before a change

Reading a task and changing a remote system are different jobs. oflow separates them. Supported GitLab changes follow a plan, approval, application and verification flow, with local audit records. Its current write scope covers bounded planning operations such as issues, notes, labels and milestones. It does not grant an agent a general licence to push code or deploy software.

That distinction matters even if you never use an AI assistant. It makes the moment of permission visible: what is about to change, and what evidence will show that it changed as intended?

What this opens up

The near-term opportunity is not a “fully autonomous team.” It is a better working relationship between people, their project tools and the software that helps them build. A developer can hand off a well-scoped issue, inspect the proposed action and keep GitLab as the source of truth.

You can find oflow alongside our other open-source work.

oflow is public and still evolving. The repository documents what works today and what remains on the roadmap. If your team works in GitLab and is experimenting with coding agents, the code and setup instructions are available on GitHub.

PolderLabs

Let’s talk.

A technical question or an idea? Talk directly with an engineer.

Send an emailinfo@polderlabs.ioTell us about your projectOpen the contact form