WaitPerk — A little perk while your agent works

3 min read Original article ↗

A little perk while your agent works

Your terminal can pay for its own tokens.Get paid while Claude thinks.

WaitPerk puts one tasteful sponsor line in your Claude Code status bar. Sponsors pay for qualified renders, and half of every dollar goes to you.

62,671 qualified renders · $312.39 earned by developers — real totals from the same ledger that pays out. Small because we're new; never simulated.

claude-code — zsh

› Open https://waitperk.com/get-started to get your signed, account-linked installer

✓ WaitPerk installed — settings backed up

› claude "refactor the webhook handler"

Qualified renders0

Your 50% share$0.0000

QUALIFIED RENDER RECEIPTS50% DEVELOPER SHAREONE-COMMAND UNINSTALLPRIVACY-FIRST BY DESIGN

How it works

The whole idea, in three steps.

Useful enough to keep. Quiet enough to forget. Reversible enough to trust.

01

Paste one command

The open client installs itself through Claude Code's documented status-line interface. It backs up your Claude settings before it changes anything.

Install WaitPerk
02

Keep coding — a quiet sponsor appears

A sponsor-flavored verb and a clearly labeled status line ride in your Claude Code terminal, only while your agent is working. That's the whole placement.

03

Reverse it anytime, see every receipt

One command restores your settings. The ledger records deduplicated render receipts so your 50% revenue share is easy to inspect.

The placement

Your ad, right in the Claude Code terminal.

A sponsor-flavored verb and a clearly labeled status line — exactly what a developer sees while Claude is working. Clearly marked, only visible during a run, and gone with a single uninstall command.

Trust is the product

Your work is not ad-targeting data.

WaitPerk never opens or reads transcript files and never stores or transmits prompts, code, responses, filenames, or repository contents.

Used locally

Model + context

Displayed in your HUD and not sent with sponsor receipts.

Sent to WaitPerk

Opaque receipt IDs

Device token, campaign delivery ID, client version, and a hashed turn key. Nothing else leaves your machine.

Never collected

Your actual work

No prompts, files, code, paths, repositories, responses, or transcript contents.

The obvious question

Is this allowed?

Fair question for anything that touches your Claude Code setup. Here is exactly what WaitPerk does, so you can judge for yourself.

The surface

Documented settings

Claude Code officially supports custom status lines, hooks, and spinner verbs — they are user-facing settings with their own docs. WaitPerk is a status-line program you choose to install, the same surface any custom status line uses.

What it touches

Your own config, backed up

One file: ~/.claude/settings.json, edited with your consent after taking a backup. No other vendor's files, no binaries, nothing system-wide. One command uninstalls and restores your settings exactly.

What it talks to

Only waitperk.com

The client never calls, proxies, or intercepts Anthropic's servers and never reads your prompts or code. It reports opaque view receipts to WaitPerk and nothing else.

Independence

Not an Anthropic product

WaitPerk is independent and unaffiliated — the status line is yours to configure, and sponsors rent that space from you, not from Anthropic. Early pre-launch builds also experimented with a reversible VS Code panel ad; that surface was retired on Jul 12 and old installs cleaned it up automatically.

Founding cohort

Help shape the respectful developer ad.

Join as an early developer or a founding advertiser and get first access as WaitPerk grows.