Kickbacks.ai Puts Ads in Your AI Spinner: The Hype, the Product, and How to Try It

Kickbacks.ai is a VS Code extension that sells the “thinking…” status line in Claude Code and Codex as ad space, and pays you up to half the revenue when ads run on your machine. It turns the dead seconds your AI tools spend processing into a tiny income stream, and that idea has developers split between “clever” and “please no.”

What is Kickbacks actually doing?

It targets a sliver of screen real estate nobody uses: the single-line status message that shows while an AI coding tool is working. Instead of a generic spinner verb, Kickbacks injects a sponsored message. Advertisers bid for that attention through an English-ascending auction, and because the audience is highly technical developers, that attention is worth paying for.

There are four ad surfaces in total: the spinner overlay, a thinking-shimmer, the status-bar line, and the CLI spinner verb. Impressions earn a base rate, and a click is worth 50 times an impression. Your earnings, daily, monthly, and lifetime, show live in the VS Code status bar.

Why are developers arguing about it?

Because it crosses a line some people consider sacred: ads inside the tool you write code in. The optimistic read is that this space was wasted, the revenue share is generous at up to 50%, and nobody is forced to install it. The skeptical read is that normalizing ads in developer tooling is a slippery slope, and that selling your own attention back to you for pennies is a strange trade.

Both reactions are fair. What makes the project interesting is that it’s honest about the mechanics, with a server-controlled killswitch and screen-time verification baked in, rather than hiding how the money moves.

How do you try Kickbacks?

Installing it takes about a minute:

1. Open the VS Code Marketplace, search “Kickbacks,” and install the extension.
2. Click “Kickbacks: Sign in” in the status bar.
3. Authenticate with your Google account. The token is stored in your OS keychain.
4. Earnings start automatically, and you’ll see them tick up in the status bar.

It supports local, Remote-SSH, devcontainer, and code-server setups, so a remote dev box works the same as a laptop.

How do you build it from source?

The repo is source-available (proprietary license, not open source), and the codebase is mostly TypeScript. If you want to inspect or package it yourself, the commands are standard:

• npm install to pull dependencies
• npm run build to produce the esbuild output
• npm test to run the vitest safety validation
• npm run package to generate the .vsix you can install directly

The source is organized by concern: src/adapters/ holds the tool-specific injection logic, src/auth/ handles sign-in and tokens, src/metrics/ tracks impressions and clicks, src/viewTracking/ verifies the ad was actually on screen, and src/killswitch/ is the remote safety shutoff.

Is it worth installing?

If you run Claude Code or Codex all day and don’t mind a sponsored line where a spinner verb used to be, it’s a low-effort experiment, and you can uninstall in seconds if it annoys you. If ads in your editor are a hard no, this isn’t going to change your mind, and that’s a perfectly reasonable position. The honest answer is that the payout per developer is small; the reason to try it is curiosity about where this model goes, not the income.

FAQ

How much can you earn? Impressions pay a small base rate and clicks pay 50 times that, with up to a 50% revenue share. For most solo developers it’s pocket change, not a salary.

Is the source code open? It’s source-available under a proprietary license, so you can read and build it, but it isn’t open source.

Which tools does it support? It injects into Claude Code and Codex spinners, and runs across local, Remote-SSH, devcontainer, and code-server environments.