Does GitLoom work alongside CodeRabbit, Copilot, or Greptile?

Yes. GitLoom doesn’t review code or leave comments. It counts bot comments as findings, never as approvals, so a PR with unanswered bot comments stays on its author’s list until someone deals with them.

Won't this just be more Slack noise?

No. If nothing changed, GitLoom sends nothing. Reminders about the same PR are batched every few days, so the channel stays readable.

What counts as a stuck PR?

A PR waiting on its first review, approved but not merged, blocked by a merge conflict or failing CI, or carrying AI-reviewer findings nobody answered. Each one is listed under the person whose move it is.

How is GitLoom different from the official GitHub Slack app?

The official app posts a message for nearly every event: pushes, comments, branches. Most teams mute the channel within weeks. GitLoom sends one digest on weekday mornings that names the stuck PRs, and nothing when nothing needs attention.

Will my engineers feel watched?

No. GitLoom reads what the team already publishes on GitHub: PR titles, commit messages, review comments. There is no scoring, no leaderboard, and no per-person numbers. Everyone sees the same digest, and it only lists PRs that are waiting on someone.

How much of our code does GitLoom see?

GitHub will tell you we can read it, and that part is true. GitHub has no metadata-without-code permission: reading commit messages requires the same Contents scope that grants file access, and we cannot opt out of that. What we actually do is narrower. We never request file contents. Digests are built from PR titles and descriptions, commit messages, review comments, and the names of changed files. No source code is stored on our servers or sent to OpenAI.

Where can GitLoom deliver reports?

Slack, email, and Telegram, chosen per report. Live PR Cards and GitLoom Agent work in Slack.

How long does setup take?

About two minutes. Install the GitHub App, connect Slack, pick a channel. Repos you grant during install are tracked automatically, you can test-send any report to yourself before it goes live, and the first digest arrives the next weekday morning.

One click, anytime. The digests stop and your data is wiped on the way out.

What if the digests aren't useful?

Every plan starts with a 10-day free trial with full access. Cancel before it ends and you pay nothing.

See which PRs
are waiting on you.

GitLoom checks your GitHub repos and sends one Slack message every weekday morning: which PRs need a review, a reply, or a merge, and who should do it. If nothing is stuck, it sends nothing.

Start free trial See the weekly digest

2-minute setup10 days free

inbox10:14

GitLoom[email protected]

Weekly digest: 14 PRs shipped across 3 repos

The Stripe checkout rebuild finally merged after six weeks.

#eng · reminder09:00

GitLoomApp

#742 in acme/api has waited 4 days for a first review.

eng·daily digestthu 09:00

GitLoomApp9:00 AM

3 PRs are waiting. If your name isn't below, nothing is blocked on you.

Sara: 2 waiting on you

Review Verify webhook signatures (api #746) · 3d waiting, by priya
Re-review Rate-limit headers (api #731) · 2d waiting, changes requested

Jonas: 1 waiting on you

Address the review findings on Refactor session storage (web #742) · open 2d, 5 unresolved threads from coderabbitai

Everything else is fine: 9 other open PRs are moving normally.

Read full digest

GitHub→Slack+Email+Telegram

Writing code got cheap. Reviewing it didn't.

Agents open pull requests all day, and each one still needs a person to review and merge it. Most of the waiting happens because nobody is sure whose move it is.

Pull requests openedWhat your reviewers can get through

Coding agents arrivethe review queueBeforeNow

Illustrative. The shape teams describe, not measured data.

Nobody picks it up

No reviewer assigned, so everyone assumes someone else has it. GitLoom flags it until somebody claims it.

Waiting on each other

Changes were requested on Monday. Since then, the author and the reviewer have each been waiting on the other. GitLoom says whose turn it is.

Approved, then forgotten

One click from shipping, and it sits for days collecting conflicts. GitLoom puts the merge on the author’s list.

Bots find problems. GitLoom makes sure someone answers.

CodeRabbit and Copilot leave comments, and then nobody follows up. The next morning, GitLoom puts the open findings on the author's list, so they get handled before a human reviewer starts.

Your AI reviewer · finds the problems

Refactor session storageweb #742

coderabbitaibotreviewed 2 days ago

src/session/store.ts:88

The session write is not awaited before the redirect, so a fast client can land on a stale session.

src/auth/callback.ts:41

returnTo is passed to the redirect without validation. This allows an open redirect.

5 unresolved conversations · no replies

GitLoom · names whose move it is

eng·next morning, 9:00

GitLoom

Jonas: 1 waiting on you

Address the review findings on Refactor session storage (web #742) · open 2d, 5 unresolved threads

Works with CodeRabbit, GitHub Copilot review, Greptile, and other review bots. Their comments count as findings, never as approvals.

The GitHub app posted 212 messages this week. GitLoom wrote one summary.

Every Friday, GitLoom writes up what shipped in plain English that people outside engineering can follow. When you cut a release, it drafts the release notes too.

The official GitHub app · 212 messages this week

GitHubApp1:33 PM

[acme/api] 5 commits pushed to main by mike

GitHubApp2:41 PM

[acme/api] New comment on #735 by dana

GitHubApp4:58 PM

[acme/api] CI · build #4519 passed on main

GitHubApp8:56 AM

[acme/api] 3 commits pushed to feature/webhook-signing

GitHubApp9:14 AM

[acme/api] PR opened · #746 Verify webhook signatures

GitHubApp9:15 AM

[acme/api] CI · build #4512 passed on main

GitHubApp9:31 AM

[acme/api] New comment on #741 by mike

Muted weeks ago. Nobody reads it.

GitLoom · 1 message

team·weekly digest from GitLoomfriday

GitLoomApp

A big week for checkout. The Stripe rebuild went live after six weeks in review, and failed card payments now retry on their own. Most of the rest was groundwork for the EU launch.

Production

acme/web

New checkout flow is live for all customers
Invoices can be paid in euros

acme/api

Failed card payments retry before the customer is emailed
Webhook signatures are checked on every delivery

Staging

acme/web

EU cookie consent banner, ready for review

Slack, email, or Telegram.

One Slack message per PR. It updates itself.

With Live PR Cards, each PR gets one Slack message showing its review, CI, and conflict status, edited in place as it changes. Updates go in the thread.

The channel only gets pinged for approvals, change requests, and CI turning red or green.

pull-requests

GitLoomApp10:02 AM

VAT for EU invoices

PR #758 in acme/api · priya

Charges the right VAT rate on invoices for customers in the EU.

Review

Awaiting review

CI

🟡 Running

Conflicts

None

Updated today at 10:02 AM

Ask GitLoom in Slack.

Mention @GitLoom in any channel or DM it. GitLoom Agent answers from your team's GitHub activity, right in the thread, so nobody has to dig through PRs for you.

@GitLoom which PRs are waiting on me?
@GitLoom write my standup
@GitLoom what shipped since Monday?
@GitLoom draft release notes for v2.14

Included in the Professional plan.

eu-launch·thread

M

Maya2:14 PM

@GitLoom what's still blocking the EU launch?

GitLoomApp2:14 PM

Two open PRs:

VAT for EU invoices (api #758) has waited 2 days for a first review. Sara is the requested reviewer.
Cookie consent banner (web #761) is approved. Ale just needs to merge it.

The euro checkout already shipped on Tuesday.

What GitLoom sends, and when.

Flat pricing per workspace. Not per seat.

Recommended

Starter

The right fit for most product companies.

$24/ month

Billed yearly as $290

Up to 10 tracked repositories
Unlimited developers
All report types and delivery channels
Live PR Cards in Slack
Email support

Start free trial→

Professional

For larger companies and agencies.

$83/ month

Billed yearly as $990

Everything in Starter
Up to 50 tracked repositories
GitLoom Agent: ask questions, get custom reports
Priority support

Start free trial

What the first teams say:

We never touch your source code.

GitHub has no metadata-without-code permission, so the install screen will say we can read your code. We never request it, and none of it ever reaches OpenAI.

Security›What we read

What we read

Metadata, never file contents

Commit messages and authors

PR titles & descriptions

Code reviews & comments

Changed file names, diff size

File contents: Never requested

Repository secrets: Never requested

Environment variables: Never requested

10 days free. Full access.

Install today, first digest tomorrow morning. Cancel before day 10 and we never bill you.

Cancel in one click. Anytime.

From settings. No support email, no 30-day notice. Digests stop and your data is wiped.

In writing, in our terms of service and privacy policy.

What teams ask before installing.

If yours isn't here, email us.

Give every PR an owner.

Install today. Tomorrow at 9:00 AM, everyone on the team sees which PRs are waiting on them.

Start free trial

Two minutes to install · 10 days free

See which PRs are waiting on you.

Writing code got cheap. Reviewing it didn't.

Nobody picks it up

Waiting on each other

Approved, then forgotten

Bots find problems. GitLoom makes sure someone answers.

The GitHub app posted 212 messages this week. GitLoom wrote one summary.

One Slack message per PR. It updates itself.

Ask GitLoom in Slack.

What GitLoom sends, and when.

Flat pricing per workspace. Not per seat.

Starter

Professional

We never touch your source code.

What we read

10 days free. Full access.

Cancel in one click. Anytime.

What teams ask before installing.

Give every PR an owner.

Writing code got cheap. Reviewing it didn't.

Nobody picks it up

Waiting on each other

Approved, then forgotten

Bots find problems. GitLoom makes sure someone answers.

The GitHub app posted 212 messages this week. GitLoom wrote one summary.

One Slack message per PR. It updates itself.

Ask GitLoom in Slack.

What GitLoom sends, and when.

Flat pricing per workspace. Not per seat.

Starter

Professional

We never touch your source code.

What we read

10 days free. Full access.

Cancel in one click. Anytime.

What teams ask before installing.

Give every PR an owner.

See which PRs
are waiting on you.