Get the shape
of the change.
A walkthrough brings the changed files, review status, and findings into one readable place.
Code review, with a point of view
A sharp eye on the diff. Clear feedback for the human. Meet the review companion with a little more bite.
Install the App, then have your selected repositories activated by the service operator.

01 / Meet Code Pup
A review should move the work forward.Make a pull request easier to understand, inspect, and act on. Code Pup puts the walkthrough, findings, and review commands in the conversation.
A walkthrough brings the changed files, review status, and findings into one readable place.
Inline findings keep the observation close to the code. The useful part is the reason and the next step.
Request another review, run a full review, or pause and resume reviews through commands in GitHub.
02 / In the pull request
The pup brings personality. The finding brings evidence.Good feedback tells you what can happen and what to do about it. Code Pup’s voice stays direct, constructive, and close to the diff.
Illustrative review / not a real pull request

Verdict
In this example, an empty value reaches a parser that expects a date. Validate at the boundary so a malformed request returns a clear error.
A little character. A readable status. Useful feedback in real text.
03 / Why Code Pup
Your workflow deserves an intentional choice.For developers who want practical review feedback, a recognizable companion, and control over how review fits their workflow.
Our upcoming BYOK membership separates Code Pup service access from usage billed by your model provider.
Walkthroughs and inline findings belong beside the pull request. Make the review easier to read and the follow-up easier to discuss.
Sharp, specific, and constructive. Personality can make a tool memorable; the quality of the observation makes it useful.
04 / Bring your own key
Membership previewBYOK means “bring your own key.”
You use your own account with a supported model provider. Code Pup membership and model usage are separate parts of the cost.
01 / Code Pup
Code Pup service access and its review workflow, under the membership’s scope and limits.
Membership terms apply02 / Your model provider
Usage billed separately by your provider under your own account, rates, and limits.
Provider terms applyPricing, customer key setup, and enrollment details will be published before launch.
05 / A few good questions
Installation grants the App access to the repositories you select. Those exact repositories also need activation by the service operator before Code Pup can review them.
Not yet. Provider keys are configured by the service operator today. Customer key onboarding and membership enrollment are planned.
The membership model separates service access from model usage. Your model provider bills usage separately under your own account.
The reviewed diff and configured context are sent to the selected external model provider. Keys are configured server side today. Evaluate the selected provider’s data and retention policies for your code.
No. Review completion and approval are different states. Read the findings, checked scope, and relevant limits before deciding what to merge.
The brandbook covers the original identity, colors, mascot, and status marks, with downloadable assets.
Find your review companion
Bring a sharp, constructive review companion into the pull-request conversation.
Install GitHub App Selected repositories need activation after installation.