THE LEAK
You wait on your agent all day. That wait pays you nothing.
Every prompt, your AI thinks for 10–90 seconds and you watch the bar. That attention has a buyer. Right now you're giving it away for free.
Open-source · Signed · Zero dependencies
Get paid while your AI thinks — without compromising your machine.
Lumaline renders one clearly-labeled, clickable sponsored line in Claude Code's status bar and pays you a share of the revenue. No bundle patching. No silent updates. No security trade-offs.
claude-code — ~/work/api
$ claude
› Refactor the auth middleware to use the new token verifier
analyzing src/auth/* … 23 files
drafting changes …
✳ Building…·1m 12s·sponsoredDeploy faster with Vercel →
Real status line. Real label. One impression — counted only when you're actually there.
Why Lumaline exists
Five thoughts, in order.
THE INSTINCT
And your gut says: not in my terminal.
Good instinct. Your dev machine is sacred. Almost every way to monetize it means letting code you didn't write touch the place you actually work.
YOU ALREADY SAW IT
Kickbacks.ai paid people — by quietly breaking their machines.
It patched Anthropic's bundle, weakened CSP, and auto-updated in the background without asking. The idea was right. The method betrayed the people who trusted it.
THE REFRAME
The danger was never the money. It was the method.
Ads in a status line aren't a threat. Bundle patching is. Silent updates are. Unsigned code is. Strip those out and all that's left is one labeled line — and a payout.
SO YOU GET BOTH
A machine you still trust. And a check for attention you were wasting anyway.
You're not paid despite the security — you're paid because of it. Every ad is signed before it renders, every second of attention is verified before it counts. The risk is gone and the money is real.
How it works
Four pieces. Nothing else.
01
Sanctioned surface
Uses only Claude Code's official statusLine mechanism. Nothing patched, nothing injected.
02
Signed content
Every ad is ed25519-signed. The client refuses anything unsigned or forged.
03
Honest billing
A server-verified dwell window + per-second heartbeat hash-chain. Impressions count only after a full, real-activity dwell — never during idle.
04
You get paid
Transparent, publisher-favored 60/40 revenue split. Gross revenue always visible.
Trust guardrails
Every objection, answered in code.
Will it touch my Claude config?
Only when you run
lumaline install. Never on npm install.Can I undo it?
lumaline uninstall restores your old status line. Backup kept.Could a forged ad get through?
ed25519-signed. The client refuses anything unsigned.
What's it pulling into my machine?
Zero runtime dependencies. Nothing transitive to audit.
Will I actually get paid fairly?
Honest billing: impressions count only after a real, verified dwell.
Do I have to trust your word?
Open-source, with a local audit log of every payload. Verify it yourself.
For developers
Earn passive income during AI wait-time.
- — Install in one reversible command
- — Clearly-labeled, non-intrusive
- — You keep 60% of gross
- — Opt out anytime
npm install -g lumaline lumaline install # explicit, reversible
Economics
Transparent, publisher-favored economics.
CPVA (cost per verified attention-second) and CPC via tokenized click-redirect. A 60/40 split in the developer's favor. Gross revenue always visible, with clawback and invalid-traffic detection so advertisers only pay for real attention.
Be first when Lumaline opens.
Developers earn. Advertisers reach. Everyone can read the code.
Open-source. Star us on GitHub →