ACTIVATED HUMAN
App Library
App Library · Pro

Connect GitHub to Blue, and the work you shipped can speak for itself.

The feeling of a work week and the record of it are often two different stories. GitHub holds the record. Blue can read it inside the conversation where the feeling lives.

The short answer

Connect GitHub and Blue can read your repositories mid-conversation: recent commits, open pull requests, the issues carrying your name. Ask what you shipped this week and the answer arrives as a card, drawn from the actual record. GitHub is part of Pro, opt-in, scoped to your own account, and revocable at any time.

What Blue can see

What you actually shipped

Commits and merged pull requests over any stretch you ask about. When the week felt unproductive, the log frequently disagrees, and Blue can show you.

What is open and waiting

Pull requests waiting on review, issues assigned to you, the branch you abandoned on Tuesday. Blue can pull the open loops into a planning conversation before they become surprises.

The work inside the life

Blue also knows the deadline pressure, the sleep, the thing you said about wanting more deep work. The commit history lands in that context, which is where it starts meaning something.

GitHub is reach-on-demand, like every App Library connection: Blue reads your repositories when the conversation calls for it, rather than watching your activity in the background. Blue’s core stack works differently, with calendar, tasks, and knowledge base continuously synced into working memory. Your code enters the conversation at the moments it belongs: a weekly review, a standup you are about to walk into, an honest look at where the energy went.

Things you can say

Mid-conversation
what did I ship yesterday?which pull requests are waiting on me?what issues have my name on them?how did this week compare to last week, commit-wise?bring my GitHub week into the review
A Friday, for example

It’s Friday and the week feels like it evaporated. You say so, and Blue asks whether it actually did. You are not sure, so Blue reaches into GitHub: eleven commits, two pull requests merged, one still waiting on review since Wednesday. The record says the week was real, and the waiting review explains the itch you could not name. Blue also knows Thursday was eaten by meetings, because your calendar lives in its working memory. So the conversation lands somewhere useful: the work happened, the bottleneck is one reviewer, and Monday starts with a ping to them instead of a vague sense of being behind.

Who this is for

Developers who lose the week

If Friday regularly arrives with no memory of what got done, a companion that can read the commit log turns vague guilt into an actual record.

Side-project builders

The project that lives in evenings and weekends survives on momentum. Blue can see the gap since your last commit and ask about it kindly, inside the life that caused the gap.

Leads holding many threads

Open pull requests, stale issues, the repo you have not looked at in a month: Blue can gather the loose ends into one conversation when you are planning, not after something slips.

Where it fits in a life

GitHub feeds the Work dimension most directly, and Creativity whenever the repository is the personal kind. Because Blue writes your weekly review from what actually happened, a connected GitHub means the shipping record shows up there alongside the calendar and the conversations, and the review gets harder to argue with.

Honest answers

What does connecting GitHub to Blue actually do?

It lets Blue read your GitHub inside a conversation: commits, pull requests, issues, and repository activity. You ask what shipped or what is stuck, and Blue pulls the answer from the real record, rendered as a card in the chat.

Does Blue monitor my repos in the background?

No. GitHub is an App Library connection, and those are reach-on-demand: Blue reads when the conversation calls for it. The continuously synced layer is the core stack, calendar, tasks, and knowledge base. Teaching that difference straight is part of the deal.

Can Blue see private repositories?

Blue works within your own account and the access you grant when you connect. The connection is opt-in, scoped to the job, and revocable at any time, and every read Blue performs is visible as a card in the conversation.

Which tier do I need for the GitHub connection?

Integrations are Pro, GitHub included. The trial is 14 days of everything, no card, which is enough time to run a real work week with your shipping record in the conversation.

Will Blue write code or open pull requests for me?

That is not the job. Blue is a companion for the life around the work: it reads the record, holds it next to your energy and your plans, and helps you decide what matters. Your editor and your CI remain your own.

Connect GitHub 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.

Keep going

Last reviewed July 23, 2026, against the shipping product.