GitHub

GitHub App install · Live

Turn your repo into a teammate.

Install the Lumen GitHub App (or paste a PAT) and ask the agent to search code, triage PRs, inspect diffs, or leave review comments. Lumen can comment and request changes on PRs — it can never approve.

Install GitHub AppHow it worksLive
Auth
GitHub App install or PAT
Access
Read · Comment & request changes on PRs
Plan
Every plan
Freshness
Live — every call hits the GitHub REST API
Available on
Every plan

Examples

Questions teams actually ask.

The tools it pulls from are shown inline — every answer in Lumen cites the underlying records it read.

Engineering

What's the CI status on main, and which jobs are failing on the open PRs?

pullscheckspullRequests
Review

Read PR #412, flag anything that looks like a breaking API change, and leave a REQUEST_CHANGES review if you find one.

pullspullRequestDiffpullRequestFilespullRequestReview
Support

Where in the codebase do we handle the `billing.refund` webhook, and what's the most recent change to that file?

pullscodeSearchfileContentscommits
Product

Summarise the last 20 commits on main — what shipped this week?

pullscommits
Engineering

Which PRs have been open more than 5 days with no review activity?

pullspullRequestspullRequestComments
Security

Grep for any usage of `process.env.ANTHROPIC_API_KEY` outside of `lib/llm/`.

pullscodeSearch

Preview

See what the answer looks like.

Toggle the tools Lumen is allowed to use. The plan, answer, and cited sources update to match.

Tools
Read + PR comment
You

Review PR #412 and leave a comment if the migration looks unsafe.

Plan
  1. codebase.getPR — pull title, body, stats, review state
  2. codebase.getPRDiff — fetch unified diff (capped at 200 KB)
  3. codebase.getPRFiles — inspect migrations/0042_user_schema.sql in particular
  4. codebase.reviewPR — submit REQUEST_CHANGES with specific concerns
Answer

PR #412 adds a NOT NULL column to a 50M-row table with a default backfill. I've left a REQUEST_CHANGES review flagging two concerns: the backfill is non-atomic and the migration drops a covering index mid-transaction. Review: github.com/org/repo/pull/412#pullrequestreview-...

Sources
  • [1]codebase.getPR — PR #412, 3 files changed, 147 additions
  • [2]codebase.getPRDiff — 4.2 KB diff, fully inlined
  • [3]codebase.reviewPR — event=REQUEST_CHANGES, 1 review posted

Scope

What Lumen sees. What it can change.

Read is on by default. Every write is a separate toggle, capped per user, and logged.

Read

What Lumen reads

Every read is scoped to repositories you explicitly granted the App during install (or the `org` and `defaultRepo` configured on your PAT).

  • Code search and file contents

    Individual files capped at 100 KB; binary files are detected and skipped

  • Commits and commit history

    Last N commits per branch, with author, date, and SHA

  • Pull requests (list, detail, diff, files, comments)

    Diffs capped at 200 KB; per-file patches capped at 20 KB

  • CI check runs

    Aggregated status per branch (success / failure / pending / unknown)

  • Repository list

    For App installs, scoped to the repos you selected at install time

Write · opt-in

What Lumen can write

Two write actions, admin-opt-in. Both are scoped to pull request review — Lumen cannot merge, push, or change repo settings.

  • Comment on a pull request

    Posts a plain conversation comment with the agent's analysis

  • Submit a pull request review

    `event` is restricted to `COMMENT` or `REQUEST_CHANGES`. `APPROVE` is not supported — humans sign off merges

Every read and write is logged with user, operation, repo, PR number (if any), and the body text posted. Exportable as CSV.

Install

Connect in under a minute.

No keys, no call, no app marketplace fine print.

  1. Install
    01

    Install the Lumen GitHub App

    In Settings → Integrations → GitHub, click Install GitHub App. You'll land on GitHub's install page where you pick the repos Lumen can see. GitHub mints a short-lived installation token per request — Lumen never stores a long-lived secret.

  2. Or paste a PAT
    02

    Use a personal access token

    Prefer a PAT? Paste a classic or fine-grained token in the same panel and optionally set a default org and repo for shorthand calls. PATs are stored encrypted.

  3. Ask
    03

    Try a real engineering question

    Start with "What's red on CI right now?" or "What changed in the last 20 commits?" — the agent will pick the right operation and cite every row.

Questions

Frequently asked.

Why can't Lumen approve PRs?
Because a human should always sign off a merge. The agent's review options are `COMMENT` and `REQUEST_CHANGES` — there's no code path that sends `APPROVE`. This is an intentional design choice, not a scope limit.
App install vs PAT — which should I use?
The App is recommended. It gives you per-repo granularity at install time, rotates credentials automatically, and is easier to revoke. PATs are simpler for hobby projects or if your org blocks App installs.
Are private repos supported?
Yes, as long as the App install (or PAT) has access. Lumen never indexes code off-platform — every search and file read goes to GitHub in real time.
How does code search work?
Lumen calls GitHub's Code Search API directly. Syntax like `repo:owner/name language:ts path:lib` works as-is. Rate limits are GitHub's, not Lumen's.
What happens with very large diffs?
PR diffs are capped at ~200 KB; per-file patches at 20 KB. When a diff is truncated, Lumen surfaces that fact in the result so the agent knows not to hallucinate the rest.
Can Lumen react to webhook events?
Not today. Lumen is pull-based — the agent calls GitHub when you ask a question. Webhook-driven workflows ("review every new PR in #backend") are on the roadmap.
What about GitHub Enterprise Server?
Not officially supported yet. If this matters for you, email us.

Pairs with

Better together.

Install the App. Start reviewing.

GitHub App install, scoped to the repos you pick. PAT option if you prefer.

Install GitHub AppBack to all integrations