Rebates vs Kickbacks.
Both pay you to show sponsored lines in Claude Code and Codex. The difference is what happens to your code. Rebates never reads it in the default flow, redacts any opt-in context on your machine, and turns off in one command — with a byte-for-byte restore.
The comparison, honestly.
Every Rebates row is a claim we stand behind. Every Kickbacks row is either what their site says or a plain “Not stated” where it is silent — we do not mark them down for what they simply have not published.
| Feature | Rebates | Kickbacks |
|---|---|---|
| Where the line shows | Sponsored footer in Claude Code + Codex | Ads in editor / CLI loading spinners |
| Supported tools | Claude Code, Codex (Cursor + Gemini CLI coming) | Claude Code, Codex (extension + terminal) |
| How you earn | A flat credit for every visible impression | 50% revenue share, plus clicks (50× impression rate) |
| Reads your code? | No — the default flow never reads code, files, or transcripts | Not stated on kickbacks.ai |
| On-device redaction | Secrets, emails, paths, URLs, code stripped before any opt-in summary | Not stated on kickbacks.ai |
| Contextual ads | Opt-in and disclosed — decline and still earn | Not stated on kickbacks.ai |
| Turn it off | `rebate off` restores settings byte-for-byte | Not stated on kickbacks.ai |
| Install | One-command installer (asks consent, backs up settings) | Download + install a VSIX extension |
Compared against kickbacks.ai as of July 2026. Both products are new and change often — check their site for the latest, and always read a terminal tool’s own docs before you install it.
Privacy and control, on by default.
The three things developers ask first about any terminal-ad tool — and where Rebates gives a straight answer.
It never reads your code
The default sponsored footer needs nothing about what you are writing. No uploads, no filesystem scans.
Off in one command
`rebate off` disables the integration and restores your Claude Code and Codex settings byte-for-byte.
Paid per impression
A flat credit each time the line is shown — no click-chasing, no earnings that swing with advertiser bids.
Questions people ask before switching.
Is Kickbacks legit?
Kickbacks is a real product that pays developers a 50% revenue share for ads shown in editor and CLI loading states in Claude Code and Codex. Whether it is right for you comes down to what you are comfortable running in your terminal — so check how any tool handles your code, what it discloses, and how you turn it off. Rebates publishes all three up front.
What is the difference between Rebates and Kickbacks?
Both pay you to show sponsored lines in Claude Code and Codex. Rebates leads with privacy and control: it never reads your code in the default flow, redacts any opt-in contextual summary on your machine, and turns off in one command with a byte-for-byte settings restore. Kickbacks pays a 50% revenue share plus clicks; as of July 2026 its site does not publish a code-privacy or uninstall statement.
Which one pays more?
They use different models, so it depends on your sessions and the sponsors in rotation. Kickbacks pays a 50% revenue share plus per-click bonuses, which swings with advertiser bids and clicks. Rebates credits a flat amount for every impression that is shown, so your earnings do not depend on anyone clicking.
Can I switch from Kickbacks to Rebates?
Yes. Run the Rebates installer and use `rebate plan` to preview every change before it is applied, then remove the other tool per its own uninstall instructions. Rebates backs up your settings byte-for-byte, so you can always get back to where you started.
Try the privacy-first one.
Install in one command, preview with rebate plan, and keep your code to yourself.
curl -fsSL https://rebates.ai/install | bash