Claude GitHub App: Code Review always reports 0 issues, @claude mentions get no response
Status Fixed / completed
Maintainer reply None cached
Activity 4 comments · opened Mar 12, 2026 · closed Mar 12, 2026
Description
We have the Claude GitHub App installed on our GitHub org with Code Review enabled. The integration appears partially functional — check runs are created — but Code Review never finds any issues and @claude mentions on PRs get no response.
This has been the case across ~8 PRs over the past few weeks.
Setup
- Claude GitHub App: Installed 3 weeks ago
- Permissions: Read access to actions/metadata, read+write access to checks, code, discussions, issues, PRs, and workflows
- Repository access: 6 selected repositories
- Code Review: Enabled (toggle on), set to "After every push" for the affected repo
- Avg Cost column shows $0.00 for the repo in question
Reproduction
- Created a test PR (auction-mobile#761) with intentionally buggy code including:
- Hardcoded API keys (
sk_live_...) and database credentials eval()usage- Memory leaks (missing
useEffectcleanup) - Off-by-one errors (
i <= array.length) ==instead of===- Unchecked
JSON.parse()on nullable values - Missing
keyprops in React list rendering - Blocking synchronous
sleep()withwhileloop - Passwords stored in AsyncStorage
- API keys passed in URL query strings
- No error handling on fetch calls
- The Claude Code Review check run completed in ~36s with:
``json``
{
"conclusion": "neutral",
"output": {
"summary": "No high-confidence issues detected in this change.",
"title": "Code review found no issues",
"annotations_count": 0
}
}
- Commented
@claude review this PRon the PR — no response at all.
What we expected
At minimum, hardcoded secrets and eval() should be flagged. And @claude mentions should get a response.
What we've verified
- App is installed with correct permissions (screenshot confirmed)
- Code Review is toggled on and set to "After every push"
- The repo is in the selected repositories list
- The check run IS being created (so GitHub → Anthropic communication works at some level)
- This is consistent across ~8 real PRs, not just the test PR
Questions
- Is $0.00 avg cost expected, or does it indicate the review isn't actually running?
- Is there an org-level configuration step we might be missing?
- Are webhook deliveries from GitHub reaching Anthropic's servers? (The check run appearing suggests yes, but @claude not responding suggests maybe not for all event types)
Environment
- GitHub org plan: Team
- Anthropic plan: Claude Pro (with Teams features)
- Affected repo: React Native / Expo mobile app (TypeScript)
Related issues
- #33206 — Code Review finds issues but posts zero comments
- #26227 — /install-github-app generates broken workflow
4 Comments
Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
@evanwinter what was the resolution for you?
@andrewchambers
TLDR: Re-doing this via Claude Code terminal session (
/install-github-app) instead of via the Claude desktop app.---
I had set this up initially via the Claude desktop app (Organization settings > Claude Code > Code Review). It was adding these status checks, but I could tell it wasn't actually doing anything.
<img width="961" height="182" alt="Image" src="https://github.com/user-attachments/assets/99de5f60-3cfb-49b8-a0b3-bdb9f2ebb8a4" />
<img width="899" height="174" alt="Image" src="https://github.com/user-attachments/assets/6d08e06b-54dc-4914-b9e7-10a57cb43774" />
I ended up going to a Claude Code terminal session, running
/install-github-app, and going through the whole setup there. Once I got the auth token set up with the right permissions, I was able to get the whole review pipeline set up — it created a PR to add two Github workflows to the repo in which I set it up.I'm thinking the
/install-github-appis the "old" way though, prior to this feature existing.It was really exciting seeing the check run w/out having to add new workflow files app that (a) needs to be maintained over time and (b) needs to be added to every codebase we want this to run in. It just didn't work...
My plan is to try this again in a bit, once the Code Review feature has had some time to mature.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.