Open a new terminal. The PATH change only applies to shells started after install. Close your terminal and open a fresh one, then run rali link. On Windows we also drop a launcher into a folder already on PATH, but it still needs a new terminal.

Check the exact filename — it's ps-one (install.ps1), not install.psi. Correct one-liner in PowerShell:

irm http://<host>:5173/install.ps1 | iex

You're mixing shells. The variable syntax differs:
• Command Prompt (cmd): %USERPROFILE%
• PowerShell: $env:USERPROFILE
Using $env:USERPROFILE in cmd makes it a literal folder name → ENOENT. Example (cmd):

code --install-extension "%USERPROFILE%\.adproviders\adproviders.vsix" --force

Install Node.js LTS from nodejs.org first. Match your CPU arch: on an ARM machine (incl. Windows-on-ARM VMs on Apple Silicon) install the arm64 build, not x64 — a mismatched Node can't load the native terminal module.

Harmless. On a fresh machine those are just where reporting a tool/editor isn't installed yet, and reg noting there was no prior cmd AutoRun. The install still completes — check for the PATH:, native-host:, and browser-ext: success lines.

It must reach the host serving the installer (same network). On a VM, set networking to Bridged or Shared/NAT, and confirm the host's IP in the command is current. Test by opening the dashboard URL in the machine's browser first.

Connect the device: run rali link (opens the browser to approve) or sign in on the dashboard. Until it's linked you'll see house ads and earn nothing.

Self-hosted setups: the auth Site URL and the SITE_URL that rali link uses are separate settings — both must point at your current host. If your host IP changed, update them (and the redirect allow-list). Normal hosted users don't hit this.

One device per account. A second machine says "already paired — remove the first"; a different account on a paired machine says "sign out first." Remove the current device on the Device page to move.

Fully restart the browser — it installs on next launch. Or load it manually: chrome://extensions → turn on Developer mode → Load unpacked → the chrome-ext folder inside your install dir (~/.adproviders/chrome-ext).

Open chrome://extensions → Developer mode → Update, or remove it and Load unpacked the folder above (which is always the latest).

That was a detection bug in older builds — update to the latest. The current build only reacts to real AI-answer text growth inside the reply area, never to typing, mouse-move, or the history sidebar.

Make sure the device is linked (rali link). Also, once you've seen 30 ads in 10 minutes it pauses on the browser (anti-abuse cap) and resumes automatically. To debug: chrome://extensions → the extension's service worker → Console → filter [adp] for heal: linked= and nextAd: REAL.

VS Code (or Cursor) wasn't installed when you ran the installer. Install the editor, then re-run the installer. Verify the CLI works: code --version.

Confirm the extension is installed: code --list-extensions should list adproviders.adproviders. Then Reload Window (Ctrl/Cmd+Shift+P → "Reload Window"). Signed out it shows "Earn while you code — sign in"; signed in it shows a real sponsored line (or nothing if there's no eligible ad — never a blank placeholder).

The in-chat ad only appears while an AI chat is actively generating a reply — a failed or idle chat has no "thinking" moment to fill. Make sure the AI assistant is signed in and actually responding. The injection is applied by the installer, so re-run it after installing/updating your AI chat extension.

Use the correct path variable for your shell (see the cmd/PowerShell note under Installing):

rem cmd:
code --install-extension "%USERPROFILE%\.adproviders\adproviders.vsix" --force

# PowerShell:
code --install-extension "$env:USERPROFILE\.adproviders\adproviders.vsix" --force

The terminal ad needs the native pseudo-terminal (node-pty). On an unusual CPU (e.g. 32-bit) it can't load, so we run the tool without the ad — the tool always works, you just won't see the line there. Make sure your Node arch matches your OS (arm64 vs x64).

The native helper lost its executable bit when copied. Re-run the installer (it re-applies it), or manually chmod +x the node-pty spawn-helper inside your install dir.

Older builds mis-resolved the real tool on Windows. Update & re-run the installer, then open a new terminal. The current build resolves the real executable in Node (preferring .cmd/.exe) and never recurses into its own shim.

House ads are the non-earning fallback shown when the device isn't linked or there's no matching campaign inventory right now. Link the device and try again; paid ads take over as soon as one is eligible.

Payout caps: max $10 per request, $10/day, $100/month (across all methods). You also set your payout country once (it can't be changed later), and UPI is India-only. Minimums: USDC $2, Virtual Visa $5, UPI $10.

Earning caps protect against abuse: browser tops out at 30 ads / 10 min, and overall earnings cap at $5/hour · $10/day · $100/30-day. These reset on rolling windows.