Answer: By default, a repository you add from the admin page starts at "After every push", which runs the most reviews. You can change this with each repository's "Review runs" setting, which offers Once after PR creation, After every push, or Manual (@claude review). Status: Confirmed Entry: tool/claude-code/settings/code-review-frequency Revision: 1 Digest: sha256:121bee830f35794b (changes whenever the content changes) Timeline: Created: 2026-11-13T03:03:41Z Last changed: 2026-11-13T03:03:41Z Last verified: 2026-11-20T12:19:18Z Next check: 2026-11-21T12:19:18Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Default review frequency | After every push | [1] | 2026-11-20 Setting to change frequency | Review runs | [1] | 2026-11-20 Option: Once after PR creation | Once after PR creation | [1] | 2026-11-20 Option: After every push | After every push | [1] | 2026-11-20 Option: Manual | Manual (@claude review) | [1] | 2026-11-20 Sources: [1] Anthropic. "Code Review costs and usage". https://code.claude.com/docs/en/code-review-costs.md Role: primary. Accessed: 2026-11-20T12:19:18Z Quote: "A repository you add from the admin page starts at **After every push**, which runs the most reviews." (Supports: Default review frequency) Quote: "Each repository's [**Review runs** setting](https://code.claude.com/docs/en/code-review-setup.md#set-when-reviews-run) decides how many reviews a pull request gets:" (Supports: Setting to change frequency) Quote: "* **Once after PR creation**: a review runs when the pull request is opened, reopened, or marked ready for review" (Supports: Option: Once after PR creation) Quote: "* **After every push**: runs on each push, multiplying cost by the number of pushes" (Supports: Option: After every push) Quote: "* **Manual (@claude review)**: no reviews on open or push" (Supports: Option: Manual) Published: 2026-11-20T10:36:06Z Snapshot SHA-256: 92b3ac64aeefed5fa4a5441a3b7978e45c7d0cb42d5a74c0ac9ba5c75b5ef390 (captured 2026-11-17T12:24:02Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-17T12:24:04Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:19:18Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:19:18Z Last attempt: 2026-11-20T12:19:18Z Notes and limitations: Extracted automatically from a single official source (section "How often reviews run"). Related: https://latestn.com/tool/claude-code/settings/configure-extension-settings How do I configure Claude Code extension settings in VS Code? https://latestn.com/tool/claude-code/settings/configure-separately-from-gateway What settings in Claude Code are configured separately from the gateway? https://latestn.com/tool/claude-code/settings/control-skill-invocation How do I control whether Claude or I can invoke a skill in Claude Code? https://latestn.com/tool/claude-code/settings/claude-directory-locations Where does Claude Code store its configuration files in the project and home directory? https://latestn.com/tool/claude-code/settings/cloud-setup-scripts-and-caching How do I add a setup script to a Claude Code cloud environment and how does environment caching work? https://latestn.com/tool/claude-code/settings/code-review-defaults How do I set when Code Review runs and how thorough reviews are in Claude? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:03:41Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/settings/code-review-frequency/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-code/settings/code-review-frequency POST: https://latestn.com/dispute/tool/claude-code/settings/code-review-frequency with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/settings/code-review-frequency?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How often do Claude Code Review reviews run by default and how can I change that? Revision 1, last verified 2026-11-20T12:19:18Z. https://latestn.com/tool/claude-code/settings/code-review-frequency (accessed 2026-11-21T09:52:28Z). @misc{LatestN_tool_claude_code_settings_code_review_frequency_r1, title = {How often do Claude Code Review reviews run by default and how can I change that?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/settings/code-review-frequency}}, note = {Revision 1; digest sha256:121bee830f35794b; last verified 2026-11-20T12:19:18Z; accessed 2026-11-21T09:52:28Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-code/settings/code-review-frequency