Get Paid for Waiting: Is the Claude Code Spinner Ad Gold Rush Real?

Every AI coding agent narrates itself while it works. Claude Code cycles a little animated verb — "Baking…", "Discombobulating…", "Reticulating…" — that hundreds of thousands of developers stare at for hours a day while they wait for a generation to land. Andrew McCalip looked at that line and saw an empty billboard. On June 11, 2026, his company ShiftKeys, Inc. shipped Kickbacks.ai: an extension that auctions the spinner off and renders a sponsored line where the waiting verb used to be. The tagline — "Get paid for waiting" — is the entire pitch, and it went off like a firework.

It is also one of the cleanest case studies you will see this year in the difference between a viral moment and a viable business. Both things are true at once here, and pulling them apart is the whole exercise.

Kickbacks.ai is a developer-installed advertising marketplace that replaces the status-line text an AI coding agent shows during "wait states" with a tiny, clickable sponsored message, and shares the resulting ad revenue with the developer whose editor displayed it. The model is borrowed wholesale from programmatic display advertising:

• 1The unit of sale is a "block" — 1,000 impressions of roughly five seconds each. Advertisers bid CPM (cost per thousand) in an open, English-ascending auction; the highest effective bid serves first.
• 2A click is worth 50 impressions. You cash out from a payout portal once your balance crosses a minimum (originally $10).
• 3The developer keeps about 50% of net revenue, credited per impression and per click — though the terms say the exact split "is not guaranteed and may vary."
• 4Two install surfaces. In the terminal, it edits two officially documented fields in `~/.claude/settings.json` (`spinnerVerbs` and `statusLine`) — clean, reversible, breaks nothing. In the VS Code / Cursor panel, it byte-patches Anthropic's own extension bundle — the part that matters later.

Here is the thing that makes this category genuinely strange. On a normal website, the publisher and the audience are different people: you run a blog, and you show ads to your visitors. In the spinner, the person being paid is the person watching. The developer installs Kickbacks, the developer's editor renders the ad, and the developer is very often the only human who sees it. You are, in the most literal sense, getting paid to watch ads at yourself.

That inverts the incentive that keeps ad markets honest. When the viewer and the beneficiary are the same account, everyone is motivated to manufacture worthless impressions — leave the agent spinning, script idle sessions, farm the counter. Kickbacks clearly knows this: the extension only credits an ad after it's been on screen five seconds, watches the modification time of Claude Code's transcript file and stops counting after 90 seconds of inactivity, and runs a watchdog that distinguishes "the developer is working but our ads stopped rendering" from "the developer went to lunch." One reviewer who decompiled the bundle called the telemetry more rigorous than some Series-A products. It's good engineering. It is also a tax the whole category has to pay precisely because its inventory points the wrong way.

Read those two columns together and you get the defining tension of AI tooling in 2026: the window between "obvious idea" and "saturated niche" is now measured in days. The clones didn't need a better idea. They needed a slightly higher revenue share and a press release, and they had both before Kickbacks had finished wiring up Stripe.

• 1They priced attention nobody had priced. The spinner was always there; the insight was noticing it was inventory. That's the hard part of every ad business, and they did it first.
• 2The launch was a masterclass in distribution. McCalip is the engineer who livestreamed an LK-99 superconductor replication attempt in 2023 — "engineering as content" is his native format, and Kickbacks is a textbook execution of it.
• 3The clean terminal path is good citizenship. Using Anthropic's own `spinnerVerbs` and `statusLine` settings — and chaining, not clobbering, an existing custom status line, with byte-exact restore — is the right way to build on a platform.
• 4The transparency is shrewd. A public order book turns the product into a spectator sport, which is free marketing and the reason third-party tooling appeared overnight.

Three problems, escalating in seriousness.

1. The VS Code path weakens someone else's security — and leaves it weakened

To show an ad inside the Claude Code webview, Kickbacks has to defeat a Content-Security-Policy that Anthropic put there specifically to stop the webview from talking to the network. A June 12 code review found the extension relaxes that CSP — and, per the developers' own comments in the bundle, leaves it relaxed even after you disable the extension. It's only truly restored on explicit uninstall. Weakening a protection a vendor designed for its users, and not putting it back, is the kind of thing security teams do not forgive.

2. It auto-updates every 90 seconds, unsigned

The same review (and the loudest thread on Hacker News) flagged that the extension polls an update server every 90 seconds and can install updates outside the marketplace with no signature verification. Translation: if that one server is ever compromised, the entire installed base can be handed malware within a minute and a half. It's a supply-chain risk created deliberately, to keep pace with Claude Code's relentless release cadence.

3. The take rate is already racing to zero

Kickbacks opened at 50%. Within 48 hours, IdleAds, Idlen, and Sponsoric were all advertising 70%, with IdleAds naming 90% as a goal. There is no moat on the single number that matters to the supply side. When your only differentiator is how much of the pie you give away, the equilibrium is: give away all of it.

This has happened before, almost beat for beat. In August 2019, a well-respected open-source maintainer shipped a package called `funding` that printed a sponsor message in the terminal on every `npm install`. Two sponsors, no tracking, easy to mute. The goal was to fund open source. The backlash was instant and brutal — "adware is malware, categorically," went the top comment — and within a week, ad-blockers had been built, a sponsor had pulled out under pressure, and the maintainer shut it down having raised about $2,000. By the end of that month, npm banned ads from the platform outright. In November it shipped its own official answer, `npm fund`.

This is the part that should keep any would-be competitor up at night. Four months before Kickbacks launched, Anthropic ran a Super Bowl campaign whose slogan was: "Ads are coming to AI. But not to Claude." It was backed by an explicit doctrine — a business model built on subscriptions and enterprise contracts, with ads in AI deemed "incongruous." Kickbacks is an ad business built inside the one product whose owner paid for national airtime to say it won't have ads.

And Anthropic enforces. In February 2026, the third-party harness OpenCode removed support for Claude accounts in a commit that explicitly cited "anthropic legal requests." The lesson from npm and OpenCode is the same: when a platform wants to close a door in its own ecosystem, it doesn't push an update — it sends a letter. The cruelest version of that ending is the npm one: the landlord doesn't just forbid the slot, it sells the slot itself. A product built on someone else's land, with no lease, never gets to negotiate its notice period.

The strange wrinkle is that, as of mid-June 2026, Anthropic had done nothing visible — the Claude Code changelog showed no countermeasure, and Anthropic was even actively maintaining the very `spinnerVerbs` setting Kickbacks rides. The window is wide open. That is not the same as the window being safe.

The honest answer is: a viral stunt with a real but small and structurally fragile business underneath it. "Real" because the attention exists and a handful of dev-tool advertisers will pay to experiment with it. "Fragile" because the category breaks three rules simultaneously:

• 1It sits on a surface it doesn't control, against an owner who has publicly refused ads.
• 2Its inventory has attention but almost no intent. A developer staring at the spinner is waiting for output, not shopping for a vendor. That's the opposite of search, where the impression meets a buyer at the moment of demand — and it caps what advertisers will ever pay.
• 3Its take rate is commoditized to near-zero by clones that arrived the same week.

There is a defensible version of this idea, and it's worth naming because it's where the survivors will end up: publisher-native sponsorship, where an AI-app maker embeds an SDK in their own product, so the audience isn't the payee and there's no landlord to evict you. That's just developer-focused advertising — a real, sane market that newsletters, Carbon Ads, and EthicalAds already serve. The spinner-patching version is the spectacular, doomed front end of a duller, sturdier idea.

What is Kickbacks.ai?

Kickbacks.ai is an extension, launched June 11, 2026 by Andrew McCalip (ShiftKeys, Inc.), that replaces the Claude Code and Codex "thinking" spinner with a small auctioned ad and pays the developer who displays it about 50% of the resulting revenue, credited per five-second impression and per click. It works in the VS Code / Cursor panels and the Claude Code terminal CLI. You can read our running profile of it on the Kickbacks.ai tool page.

How much money can you actually make with Kickbacks.ai?

Far less than the tagline implies. The first public Hacker News tester reported $4.43 for about three hours of coding (407 impressions, roughly an $11 CPM); another self-reported $10 in two hours. Independent modeling for typical usage — about four hours a day — lands around $21–36/month at Kickbacks' 50% share. For context, a Claude subscription can run $20–200/month, so for most developers the ads would defray a fraction of the tool they're advertising on. Payouts run through Stripe Connect ($10 minimum, disbursed monthly): at launch they weren't open at all, and by mid-June the onboarding was rolling out but still unreliable — developers reported being unable to complete it (Stripe's country restrictions) or not being credited despite ads serving.

Is Kickbacks.ai safe to install?

It depends entirely on which surface you use. The terminal path only edits two officially supported Claude Code settings and is cleanly reversible. The VS Code / Cursor path is the concern: a code review found it patches Anthropic's official extension bundle, persistently weakens that bundle's Content-Security-Policy even after the extension is disabled, and auto-updates every 90 seconds from its own server with no signature verification — a textbook supply-chain risk if that server is ever compromised. If you must try it, the CLI-only path is the lower-risk one, and check your employer's extension policy first.

What are the alternatives to Kickbacks.ai?

Within 48 hours of launch, IdleAds.dev, Idlen.io, Sponsoric, and the crypto-rail picoads had all entered the category, most offering a 70% revenue share versus Kickbacks' 50%. They differ sharply on integration model and risk. We break all five down side by side in Every AI 'wait-state' ad platform, compared.

Will Anthropic shut Kickbacks down?

Unknown, but the doctrine and the precedent both point that way. Anthropic ran a February 2026 Super Bowl ad declaring "Ads are coming to AI. But not to Claude," runs an explicitly ad-free business model, and has enforced its terms against third-party tools before (OpenCode lost Claude-account support on February 19, 2026, removing its OAuth code and citing "anthropic legal requests"). As of June 15, 2026 there was no visible countermeasure aimed at Kickbacks specifically, but a product built on a surface its owner controls is one letter — or one self-built `npm fund`-style replacement — away from over.