01
GET THE SHAPE
OF THE CHANGE.
A walkthrough brings the changed files, review status, and findings into one readable place.
✦ BUILT TO SPOT IT — READ THE DIFF. NAME THE RISK. SHOW THE FIX.
YOUR CODE. SHARP EYES. YOUR PUP.
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.
LESS GUESSING. MORE “GOT IT.”
GET THE SHAPE
02
FIND THE LINE
THAT NEEDS A LOOK.
Inline findings keep the observation close to the code. The useful part is the reason and the next step.
03
REVIEW ON
YOUR TERMS.
Request another review, run a full review, or pause and resume reviews through commands in GitHub.
02 / IN THE PULL REQUEST
SPOT IT. EXPLAIN IT. FIX FORWARD.
-
01
Read the change
Start with the behavior and the surrounding context.
-
02
Name the consequence
Make the reason for the finding easy to follow.
-
03
Give a next step
Suggest a concrete way to move the review forward.
Code Pup Example · PR #142
CHANGES REQUESTED
src/parse.ts
12 const raw = req.query.date;
13 const parsed = Date.parse(raw);
14 return schedule(parsed);
15 }Illustrative review / not a real pull request
03 / WHY CODE PUP
A DIFFERENT KIND OF REVIEW BUDDY.
FOR DEVELOPERS WHO WANT PRACTICAL FEEDBACK AND CONTROL.
01
Your model relationship
Bring the key. See the model bill. BYOK separates Code Pup service access from usage billed by your model provider.
BYOK
02
Your review conversation
Keep feedback where work happens. Walkthroughs and inline findings belong beside the pull request.
IN-PR
03
Your kind of tool
Serious about code. Still a pup. Sharp, specific, constructive — personality makes it memorable, observation makes it useful.
POV04 / BRING YOUR OWN KEY
TWO CLEAR PARTS. ONE PUP.
BYOK MEANS “BRING YOUR OWN KEY.”
01 / CODE PUP
THE MEMBERSHIP.
Code Pup service access and its review workflow, under the membership’s scope and limits.
Membership terms apply
02 / YOUR MODEL PROVIDER
THE MODEL USAGE.
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 / PUP MIND CENTER
CHOOSE THE MIND. BRING THE KEY.
LABELS, NOT LOGOS. YOUR KEY, YOUR PROVIDER, YOUR BILL.
SELECT THE PUP'S MIND
MIND READOUT
DEEP PUP
● engaged — sniffing every line twice
YOUR PROVIDER KEY · BYOK
Demo only — the key never leaves this page. In production, Code Pup validates server-side and your provider bills the usage.
06 / CODE PUP × RAYCAST
YOUR PUP. YOUR KEYS. YOUR FLOW.
YOUR COMPANION. ONE SHORTCUT AWAY. ⌘ SPACE
A look at the commands. Your reviews load in Raycast. Use ↑ ↓ to browse, Enter to run.
GET CODE PUP FOR RAYCAST ↓
Direct-install extension for macOS. Raycast and GitHub CLI required.
Code Pup reads your pull requests through the credentials you already trust.
Follow the Raycast setup ↗ — the import takes a few seconds, no build step required.
review PR #142 ↵
Code Pup — Walkthrough ready. 4 files changed,
2 findings, 1 worth your eyes:
validate before parsing in src/parse.ts:14. Want
the full review? ↵
Ask for a walkthrough, request the next review, or check status — without leaving the command bar.
07 / COMPANIONS & INTEGRATIONS
SAME PUP. EVERY SURFACE.
TELEGRAM · DISCORD · SLACK · CODE PUP MCP
the pup replies where your team lives
Code Pupbot · online
⋮
PR #142 · auth refresh — walkthrough ready.
4 files changed · 2 findings · 1 worth your eyes.
4 files changed · 2 findings · 1 worth your eyes.
src/parse.ts:14 — an empty value reaches the parser.
Validate at the boundary and return a clear error.
14:02 ✓✓
re-review latest push
On it. I’ll bark when the fresh findings land. ■
View findings ↗Request full review
# reviews
Code Pup
APP
▲ 3■ 2
# pull-requests
Code Pup APP
2:14 PM
Walkthrough for PR #142 is ready — 4 files, 2 findings.
Changes requested
Validate input at the boundary before parsing.
View findingsRequest re-reviewPause reviews
/review 142/walkthrough/status/pause reviews
CODE PUP MCP
One protocol, every agent. Plug the pup into Claude Code, Cursor, or any MCP-aware client — your reviews become tools the agent can call.
pr_statusget_walkthroughget_findingsrequest_reviewpause_reviewsreview_digest
Read the MCP docs ↗
{
"mcpServers": {
"code-pup": {
"command": "npx",
"args": ["-y", "@codepup/mcp@latest"],
"env": {
"CODE_PUP_TOKEN": "••••••••••••"
}
}
}
}
SMALL PUP. CLEAR SIGNAL. — STATUS MARKS
Review complete does not mean approved — match every mark to confirmed facts.
08 / A FEW GOOD QUESTIONS
BEFORE THE FIRST BARK.
What happens after I install the App?
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.
Is the BYOK membership available now?
Not yet. Provider keys are configured by the service operator today. Customer key onboarding and membership enrollment are planned.
Does membership include model usage?
The membership model separates service access from model usage. Your model provider bills usage separately under your own account.
What is shared with a model provider?
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.
Does a completed review mean approval?
No. Review completion and approval are different states. Read the findings, checked scope, and relevant limits before deciding what to merge.
Where can I find the Code Pup identity?
The brandbook covers the original identity, colors, mascot, and status marks, with downloadable assets.
FIND YOUR REVIEW COMPANION
GOOD CODE. SHARP PUP.
Install GitHub App ↗
Selected repositories need activation after installation.