​
Quickstart

1

Install

curl -fsSL https://selltraces.com/install/rebate | bash
Downloads the prebuilt binary for your platform (macOS, Linux, or Windows via Git Bash), installs it to ~/.selltraces/bin, and wires up your PATH.
2

Turn it on

rebate
The interactive onboarding detects Claude Code, explains exactly what will change, asks for consent, backs up your settings byte-for-byte, fetches the first ad, and shows the sponsored line before it finishes.For CI or scripted installs, skip the prompts:
rebate --yes
3

Open a new Claude Code session

claude
The sponsored line appears in the status bar, and the ad text replaces the thinking spinner verbs. Claude Code reads spinnerVerbs once at session boot, so a fresh session is required to see it the first time.
4

Watch earnings accrue

Onboarding prints your live earnings URL. You can always find it again with:
rebate status
The earnings page (https://selltraces.com/earn/<device-id>) is live and requires no login. See Earnings for how impressions credit and how to claim the device to your account.
5

Visit a sponsor (optional)

The status-bar link is clickable in terminals that render hyperlinks; from any terminal you can use the installed slash command inside Claude Code:
/ad
or open the current sponsor from your shell:
rebate open
6

Turn it off anytime

rebate off
This restores ~/.claude/settings.json from the byte-exact backup and removes the /ad command. Claude Code is exactly as it was.

​
Requirements

  • Claude Code installed (the onboarding checks for ~/.claude and points you to claude.com/claude-code if it is missing).
  • curl and unzip for the installer. The CLI itself is a self-contained binary; no Node or package manager needed.
Pin a specific release by passing its tag: 
curl -fsSL https://selltraces.com/install/rebate | bash -s -- @selltraces/rebate-cli@0.1.0

​
If something else owns your status line

If another tool already controls Claude Code’s status line, onboarding warns you and asks before taking over. rebate off restores the previous owner exactly, because the backup is taken before the first write.