[POSSIBLE BUG] Potential false-positive bans triggered by PR review loops via Claude Code GitHub App

Resolved 💬 2 comments Opened Oct 25, 2025 by ffigueroa Closed Oct 25, 2025

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Using the Claude Code GitHub App for pull request reviews can unintentionally trigger permanent account bans on Claude Pro / MAX.

When developers use this official integration intensively — for example, by commenting @claude please fix the issues directly in PR threads — Claude automatically commits fixes and re-runs the review.
Each new commit triggers another review cycle, and if issues persist, the process can quickly enter a loop (Claude reviews → user command → new commit → Claude re-reviews).

Because all of these automated review actions originate from GitHub’s servers/IPs, the protection system may misclassify the repeated activity as scripted or bot-like behavior.
This results in false-positive bans, even though the workflow is fully legitimate and occurs entirely within the intended GitHub App feature flow.

What Should Happen?

Claude Code’s GitHub App should correctly recognize repeated PR review cycles — especially those initiated through @claude commands in PR comments — as legitimate user activity, since they’re triggered by human interaction and GitHub workflows, not by external automation.

Even when multiple reviews occur in a short time, the system should not flag or ban the user.
Instead, it should:
• Treat GitHub-triggered reviews as safe activity from an official integration.
• Apply rate limits or batching instead of permanent bans.
• Allow continuous use of the integration without triggering false positives.

Steps to Reproduce

  1. Install the Claude Code GitHub App from the official Claude Code interface.
  2. Enable the integration for one or more repositories to allow PR reviews.
  3. Open a pull request with minor issues or lint errors.
  4. Let Claude automatically review the PR and comment with suggestions.
  5. In the PR comments, reply with @claude please fix the issues.
  6. Claude commits fixes automatically, triggering a new review.
  7. If further issues remain, repeat step 5 — this creates a continuous loop of commits and re-reviews.
  8. After several loops in a short time, the user’s Claude Pro/MAX account becomes banned without warning.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.0.27

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Warp

Additional Information

This issue doesn’t seem to result from misuse but from a normal and intensive workflow using the official Claude Code GitHub App.

The loop is specifically triggered when users fix issues directly from PR comments using commands like @claude please fix the issues, which cause multiple review and commit events within minutes. All these actions originate from GitHub’s infrastructure, which may lead the safety system to misinterpret them as automated activity.

Repro evidence: I reproduced this twice on two separate accounts after enabling the GitHub App, and both were banned shortly after. On a third account, following the same PR-review workflow but without installing the GitHub App, I have not been banned (so far). This strongly suggests a detection false positive linked to the integration rather than a policy violation.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗