BP BuilderPerks Sponsored devtool perks for AI coding sessions

Terminal-first for Codex and AI coding workflows

Sponsored devtool perks for AI coding sessions.

Content-blind, terminal-first, no surprise popups. Ads off anytime. 

npx -y builderperks@latest proof
See exactly what's sent
  • Prompts, code, paths, and command output are not sent.
  • Runs in the terminal. Browser overlay is optional.
  • Rotates through approved devtool offers, curated partner inventory, and smartlink backfill.

One command

Run proof first. Install only after it makes sense.

Run one command in your terminal. You'll see a single labeled sponsor line. Run builderperks ads off and it's gone.

1. Install npx -y builderperks@latest install codex --verify sets up a local profile on your machine. Nothing leaves it but broad stack keywords.
2. See one sponsor line A single labeled line appears in your terminal. No popups, no browser tab, no spinner takeover.
3. Off anytime builderperks ads off disables sponsored lines and keeps the utility commands.
Copy and run Get a shareable proof block 
npx -y builderperks@latest proof

The proof command is the fastest trust check. For real Codex use, run npx -y builderperks@latest install codex --verify. We send only broad stack keywords (like typescript,postgres) — never your prompts, code, file paths, command output, or secrets. Turn sponsored lines off anytime with builderperks ads off.

See exactly what's sent

Content-blind, by design.

BuilderPerks runs locally and sends one short list of broad stack keywords to pick a relevant perk. Nothing about what you're actually working on ever leaves your machine.

What we send Broad stack keywords A short list like typescript,postgres,agents so the perk is relevant. That's the whole payload.
What never leaves your machine Your prompts, code, file paths, command output, and secrets None of it is read, logged, or sent. Render history stays local in ~/.builderperks/impressions.jsonl.

Turn sponsored lines off anytime with builderperks ads off and keep the utility commands. Full details are in the privacy policy.

Straight answers

FAQ

Is this spyware?

No. It's content-blind. We send a short list of broad stack keywords (like typescript,postgres) to pick a relevant perk — never your prompts, code, file paths, command output, or secrets. None of that is read or sent.

Can I turn it off?

Yes, instantly. Run builderperks ads off and the sponsor line is gone. The utility commands keep working. No account, no support ticket, no waiting.

Do I get paid?

Not yet. You bank an estimated credit tally as you build, but settlement is in beta — it's a real running estimate, not settled cash and not a paycheck. We'll be explicit when that changes.

Will it slow my session?

No. It's one quiet line in your terminal. There's no browser popup, no spinner takeover, and it fails quietly if the network is down, so it never blocks a prompt or your shell.

Beta launch — first 25 builder spots

Be one of the first 25 builders.

BuilderPerks is running a founder-led beta. The first 25 builders shape what ships next. Install takes one command. Turn it off anytime. 

npx -y builderperks@latest install codex --verify

Terminal-first. Content-blind. No account required. Off anytime with builderperks ads off.

Founder challenge — capped beta bounty

Get paid to test whether the trust story works.

First 25 real AI-coding builders can claim a fixed beta feedback bounty. This is not ad revenue, passive income, or a payout promise. It is a capped launch incentive for proof, install, and feedback.

Step 1 $5 proof bounty Run the proof command and send a screenshot showing whether the trust story is obvious. 
npx -y builderperks@latest proof
Step 2 +$10 second-session feedback Install for Codex, run it for a second session, then send support proof and one honest objection. 
npx -y builderperks@latest install codex --verify
npx -y builderperks@latest support-proof
Cap First 25 builders only Maximum launch-bounty exposure is $375. Credits remain estimated during beta settlement. View live scoreboard
Score multiplier Screenshot + objection wins Best claim is a public proof screenshot plus one honest line about what felt trustworthy or sketchy. Open challenge manifest

To claim, reply or email a screenshot plus the command output summary. Do not send prompts, source code, command output from your own project, secrets, or private repo details.