A very reasonable idea, but isn’t everyone else in a different Claude instance or doing some old fashioned manual work while waiting on a task to finish?
the sponsored status line during Claude Code wait states is a clever attention arbitrage but the value to advertisers depends entirely on who's watching. a developer waiting for an agent run is staring at a terminal or has switched tabs entirely. curious what the actual attention model looks like and whether there's any data on how often developers are actively watching the status line versus doing something else while the agent runs
So we have reached the part of the timeline where waiting is monetised. Honestly? Respect. I’ll be the girl farming compile times.
Love the concept. I spend hours with Claude Code daily and the wait states during long refactoring sessions are real — nice to know there's finally a way to make that dead time productive.
The status line integration is smart because it's non-intrusive. I've tried similar ad-based developer tools before but they always felt like context switches. This one stays in the flow.
Quick question: does the status line script only read the JSON payload, or does it also have access to the editor context (file names, project paths)? That would matter a lot for the privacy-conscious crowd.
Either way, great launch 👏
The hook is clever: agent wait time is basically the new compile time.
The trust boundary is the product, though. For developers under NDA, the key question is what leaves the machine when the status line refreshes. Is the ad request limited to anonymous impression metadata, or can things like workspace path, repo name, model, current directory, or session context ever be sent upstream?
A public “exact payload we collect” page would probably help adoption more than any growth copy here.
Great idea, but it currently only supports Stripe payouts, which are not available in some countries. I’m also experiencing some issues with logging in.
I wish it supported PayPal or direct bank payouts as well, and that the login issues were fixed.
By the way, the idea is really good, and I genuinely like the product.
"Get paid to wait" is such a fun hook — turning agent dead time into revenue is genuinely clever. Congrats on the launch! How do you keep the sponsored status line feeling useful rather than just another ad?
The dead time angle is smart — waiting for Claude to compile is basically the new coffee break. My only concern is the same as others raised here: what data exactly gets sent to your servers during those sessions? A clear answer to that in the docs would probably convert a lot of fence-sitters. Rooting for you either way, clever niche.
Just curious what ‘personal’ data are they gonna collect to make the ads ‘personalised’
The wait state being monetizable is a clever reframe. You're paying for that idle time regardless, so turning it into a revenue split actually fits how agent workflows already feel. Curious how you keep the sponsored line from getting visually noisy when someone's mid-task.
I've had this running for a few days and it seems that after the first day the earnings are severely nerfed? The first day I ran this for a couple of hours which made 5.40 USD for 514 events, which was pretty promising. A few days later I've ran this for a whole day, and I earned 0.43 USD over 1587 events, which seems like the app is just going to make it harder for me to earn the closer I get to the 10 USD cash out threshold. I don't know if the extension has worked for anyone since I haven't seen anyone cash out yet, and even though its "free money" the extension requires constant baby sitting, asking me to reload the window or sign in again and again. Are you guys having an incident or something or do the earnings just tank after the first day?
This is a fantastic idea. I ran CodeFund (previously Code Sponsor) a handful of years back in an effort to fund OSS. Advertisers would pay top dollar knowing that they were getting their products in front of their exact target market.
Running an advertising company is difficult, especially when it comes to these types of audiences. As much as I hope this project succeeds, it's going to be a huge challenge if you plan on the developer retaining privacy.
For reference, see ethicalads.io and how they manage to balance privacy with advertising data.
Great idea, but it seems I have to auth the vscode extension via Google even if I have registered with some other email address. So I am not able to use it except with email addresses that are not tied to any Google account?
Oh, also my Claude Code CLI is running on an external host (dedicated Debian machine), I am connected via SSH from my vscode at home. I get a lot of timeout and other messages.
After 3 times reloading the window and signing in Kickback is now "green"!
Clever and slightly surreal market: monetizing agent wait states. I like the 50/50 revenue share. How are you thinking about keeping sponsored status lines useful to developers rather than just another ad surface?
It made me think.. why isnt it a thing like in all software products?? For instance we can put Ads in the free space of every OS toolbar
Honestly love the cheekiness of this, "get paid to wait" is a great hook :)
One thing I'm curious about on the technical side: since the integration lives in the status line, it gets the JSON payload Claude Code passes on every refresh (model, current working dir, session info...). To serve and attribute ads you presumably phone home pretty often.
So my real question is around privacy: what exactly does the status line script send to your servers? Do project paths / workspace dirs ever leave the machine, or is it stripped down to an anonymous impression ping? For folks working under NDA or on sensitive code, that's the make or break detail.
Not a gotcha, genuinely rooting for the idea, just think being upfront about the data flow would build a lot of trust here. Congrats on the launch!
This is a hilariously brilliant idea. Watching Claude Code spin or waiting for massive agent loops to finish is the new "waiting for code to compile". Flipping that dead time into an ad-supported revenue stream is incredibly clever.
Out of curiosity, how does the integration work under the hood? Is it injected as a custom terminal reporter or an environment wrapper? Looking forward to trying this out!
This seems like a troll idea, but SUPRISIGLY good.
I think the next piece of validation is "what does a dev do when they're waiting for Claude".
Because a lot of people I know (eg. me) just start doomscrolling or clicking around testing bugs on their product or whatever they're building.
Good luck Gabe, congrats!
This is a funny but surprisingly logical idea. Developers already spend a lot of time watching agents think, so turning that dead time into something opt-in and revenue-sharing makes sense.
About Kickbacks.ai on Product Hunt
“Get paid to wait for Claude Code to finish”
Kickbacks.ai launched on Product Hunt on June 15th, 2026 and earned 286 upvotes and 21 comments, placing #4 on the daily leaderboard. Kickbacks.ai helps developers get paid for AI-agent wait states. Advertisers bid for a tiny sponsored status line; users get 50% of ad revenue.
Kickbacks.ai was featured in Advertising (29.7k followers), Artificial Intelligence (472.9k followers) and Development (6k followers) on Product Hunt. Together, these topics include over 112.8k products, making this a competitive space to launch in.
Who hunted Kickbacks.ai?
Kickbacks.ai was hunted by Gabe Perez. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Kickbacks.ai stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Gabe Perez