The Terminal Spinner Is Now an Ad Slot

Published June 2026. A fast-moving topic; details current as of writing.

Here is a sentence that would have sounded like satire eighteen months ago: there is now a product that sells advertising space inside the little "thinking" spinner that Claude Code shows while it works, and it pays you half the revenue. It is called kickbacks.ai, it hit Hacker News this month, and it is worth paying attention to, not because it will necessarily win, but because it is the clearest signal yet of where AI monetization is heading: down, into every spare pixel and every spare second.

I build analytics tools, so I am professionally biased toward measuring things rather than moralizing about them. This is not a hit piece. kickbacks.ai is genuinely clever, genuinely a little dystopian, and genuinely instructive about a shift that affects anyone whose business touches AI traffic. Let me take it seriously, including the parts that do not work.

What it actually is

The pitch is "get paid for waiting." kickbacks.ai is a VS Code extension (the terminal CLI works too) that displays a small, clickable ad in the status line while Claude Code or Codex is busy generating. When your agent is thinking, that idle moment becomes an impression. The revenue splits 50/50 between the platform and you, the developer whose screen is hosting the ad.

On the advertiser side the mechanics are specific: a block buys 1,000 five-second impressions in the spinner, clicks are billed at fifty times the impression rate, and the highest bid serves first. As of this writing the platform just launched, has no real advertisers yet, is bootstrapping its own inventory to prime the pump, and has not opened payouts (earnings accrue, Stripe is coming). So it is early, and the chicken-and-egg problem every ad network faces is staring it down.

Why it is genuinely clever

Strip away the reflexive "ads, gross" reaction and there is a real idea here.

It monetizes dead time, not your attention-during-work. The spinner is, by definition, the moment you are not doing anything. Of all the places to put an ad, the forced wait is among the least intrusive, because the alternative is staring at a spinning glyph. That is a defensible design choice, not a cynical one.

It pays the human. The default deal of the ad-supported internet is "you are the product." kickbacks inverts it: the person hosting the ad gets half. For a generation of developers who resent surveillance capitalism, "you get paid" is a meaningfully different proposition, even if the amounts start tiny.

It found unowned inventory. Every square inch of the web is already sold. The Claude Code spinner is brand-new real estate that did not exist two years ago and that nobody had thought to monetize. Spotting unowned inventory early is how ad businesses are actually built.

That combination (idle moment + revenue share + greenfield inventory) is why it got attention instead of an eye-roll. It is a real idea, executed at the leading edge.

Why the skeptics are also right

Hacker News being Hacker News, the objections came fast, and most of them are fair.

A spinner is where you look away. The five seconds your agent is thinking is precisely when most developers tab to Slack or look at their phone. Impressions in a place people use to escape are low-quality impressions, and advertisers will figure that out.

"Get paid for waiting" rewards waiting. There is a quiet perverse incentive in monetizing latency: the longer the spinner spins, the more you earn. Nobody is going to slow their tools down for pennies, but a business model that profits from your tools being slow is philosophically upside down.

It adds an ad to your flow state. Developers guard focus jealously, and an ad in the editor, however small, is a focus tax some will refuse on principle regardless of the payout.

No advertisers yet is the whole game. An ad network with no advertisers is a clever demo, not a business, until it solves the cold-start problem that has killed a hundred ad startups. Bootstrapping your own inventory buys time; it does not prove demand.

I genuinely do not know if it works. The honest read is "interesting experiment, unproven model, real chance it is a footnote." But the footnote would still be pointing at something real.

The thing it actually signals

Zoom out and kickbacks.ai is one data point in a trend that is no longer subtle. In the last few months: OpenAI put ads inside ChatGPT answers ↗. Google reshaped AI Overviews and removed the signal that let you track clicks from them ↗. And now an indie project is selling the Claude Code spinner. Ads are colonizing AI from the top (the answer box that replaces search) all the way down to the loading state of your terminal.

This is not a moral panic, it is an economic inevitability. AI inference is expensive, subscriptions do not cover it for free users, and attention is the asset that always gets sold when the bill comes due. Every AI surface that has eyeballs will eventually have ads, or a revenue-share scheme, or both. The spinner is just the most on-the-nose example so far.

What it means if you run anything online

Here is the part that matters beyond the novelty, and it is where I will show my bias honestly: when ads are everywhere in AI, telling earned attention from paid attention becomes the whole problem.

A year ago, a visit from an AI tool was almost always earned (the model cited you on merit). Increasingly, AI-adjacent traffic is a blend of earned citations and paid placements, across surfaces that each monetize differently and report differently, when they report at all. If you treat "AI traffic" as one number, that number now quietly contains advertising you may or may not have bought, on platforms that increasingly hide the seam. The only durable defense is boring and unglamorous: measure what actually reaches you, first-party, and separate what you earned from what you paid for, in revenue terms ↗. That is the job no ad network will do for you, because no ad network is incentivized to.

I build a tool in that space (Datalenk), so take the conclusion with the appropriate grain of salt. But the conclusion stands without the tool: the more the AI layer fills up with ads, from the answer box to the spinner, the more valuable it becomes to own a clear, honest measure of what is actually working. kickbacks.ai is a fun, weird, instructive sign that the filling-up has only just begun.

FAQ

What is kickbacks.ai? A VS Code extension (and CLI) that shows a small clickable ad in the Claude Code or Codex "thinking" spinner and splits the revenue 50/50 with the developer. The pitch is "get paid for waiting." It launched recently and is still bootstrapping its advertiser inventory.

Does kickbacks.ai actually pay you? Earnings accrue per the 50/50 split, but as of writing payouts are not yet open and Stripe integration is described as coming. It is early, and it does not yet have real advertisers, so real-world payouts are unproven.

Is putting ads in a coding tool a good idea? It is a clever use of idle time and the revenue share is genuinely novel, but skeptics fairly note that spinner moments are when developers look away (low-quality impressions), that monetizing latency has a perverse incentive, and that an ad network with no advertisers has not yet proven demand.

Why does this matter beyond developers? It is a vivid signal that ads are spreading across every AI surface, from ChatGPT answers to Google AI Overviews to the terminal spinner. As paid and earned attention blend, measuring what actually drives revenue, first-party and separated by source, becomes the real challenge for anyone online.