Connect GitLab to Blue, and your pipeline of work meets the rest of your life.
GitLab knows the state of every merge request. What it cannot know is that you promised yourself a lighter week, or that the standup is in twenty minutes. Blue holds both sides.
Connect GitLab and Blue can read your projects mid-conversation: merge requests and their status, issues assigned to you, recent commits across the repos you care about. Reads happen on demand, inside your own account, and render as cards in the chat. GitLab is part of Pro, opt-in, and revocable at any time.
What Blue can see
Your merge requests, with status
Open, in review, waiting on you, waiting on someone else. Blue can lay out the queue when you are deciding what the afternoon is for.
Issues and the work assigned to you
What carries your name across projects, and how long it has been sitting there. Useful in planning, more useful in the honest conversation about whether the sprint was ever realistic.
The activity trail
Commits and project movement over the stretch you ask about, so questions like what happened since Tuesday get answered from the record instead of from memory under pressure.
Like every App Library app, GitLab is reach-on-demand: Blue reads it when your conversation calls for it, and does not watch your projects in the background. The continuously synced layer of Blue is the core stack, calendar, tasks, and knowledge base, which is already in working memory before you type. Your GitLab enters the picture at the right moments: before the standup, during the weekly review, whenever the work needs to be seen plainly.
Things you can say
Who this is for
Engineers in the GitLab flow
If your work lives in merge requests and issue boards, Blue brings that state into the same conversation that knows your energy and your calendar.
People juggling several projects
When your name is scattered across repos, the cost of asking what is on my plate is real. Blue collapses it into one question.
Anyone tired of tab-shuffling before meetings
The two minutes before standup should not be a scavenger hunt. A companion that reads the record on request gives you those minutes back.
Where it fits in a life
GitLab lands squarely in the Work dimension of Blue’s twelve-dimension frame. The interesting part is what surrounds it: because the weekly review is written from your actual week, a connected GitLab lets the sprint be reviewed next to sleep, energy, and everything else that decided how the sprint went.
Honest answers
What does connecting GitLab to Blue actually do?
It gives Blue the ability to read your GitLab mid-conversation: merge requests, issues, commits, project activity. You ask, Blue reaches in, and the answer appears as a card in the chat, drawn from the live record in your own account.
Is Blue watching my GitLab activity all the time?
No. The App Library model is reach-on-demand, and this page would rather teach that than blur it: Blue reads GitLab when the conversation calls for it. Continuous sync is how the core stack works, and only the core stack.
What tier includes the GitLab connection?
Integrations are part of Pro. The trial gives you 14 days of everything, no card, so a full sprint can pass through the conversation before you decide anything.
Can Blue merge, push, or comment on my behalf?
Blue works inside your own account, shows everything it does as a card, and never messages anyone for you, by design. The value here is the reading and the remembering: the state of the work, held inside the life that produces it.
Connect GitLab and see for yourself.
Integrations are Pro, and the trial covers everything. Start free, connect what you live in, decide later.
Start free →14 days of everything, no card.
Last reviewed July 23, 2026, against the shipping product.