A few weeks ago a tool called Kickbacks showed up here doing roughly this: put a sponsored line in Claude Code s spinner, get paid for the wait. The idea stuck with me. The implementation worried me — it edited settings.json and ran a local HTTP server, and the security replies were right to flag it.So I built the version I d actually be willing to run myself, and the trust model is the whole point:- It s a normal VS Code extension. Updates come through the Marketplace s signed channel — no custom auto-updater, no background process polling for code to execute. - It doesn t patch your editor. It uses Claude Code s documented spinnerVerbs/statusLine config, backs up your settings first, and restores them on uninstall. - The client can t fake earnings. Every impression is a server-signed Ed25519 token; idempotency keys make duplicates no-ops; a double-entry ledger backs every cent. - It never reads your code. One line, wait-state only, never the model s context. Exactly what crosses the wire: https://www.codecash.dev/transparencyThe parts that aren t done, said plainly — because this is exactly where the category burns people:- The money is small: ~$0.0055/impression. A heavy day is a couple of dollars, not a salary. I won t pretend otherwise. - Payouts go live June 22. Until then earnings are credited and visible but you can t withdraw yet. - Inventory is house ads right now. I don t have a third-party advertiser yet, so I m not going to show you a placeholder and call it a customer.I think the honest question is whether anyone will ever pay for a spinner slot — that s the load-bearing assumption and I don t have proof yet. But if agentic coding is going to monetize our attention regardless, I d rather devs could opt in, keep half, and kill it in one click, without it ever touching the code.Posting under my real name, it s my commercial product. Tear the trust model apart — that s the part I most want stress-tested.