One path, in order. Karoo 2 or 3, a Polar H10, a USB cable, and your own Claude. Sign up below, then follow the steps down the page.
Seven steps. Screens are shown where we have them; three Karoo photos are still to come, and for those the words are exact.
The form above. Codes are sent by hand, by email, from robert.chuvala@gmail.com. One code registers one Karoo; if you reinstall, reply to the email and ask for another.
Longer version with every screen.

Open veloVigil → Settings. It asks once. Karoo 2: Location. Karoo 3: Nearby devices + Location. Tap Allow.
This is the step that was missing before 0.2.4. Without it the H10 scan never runs and every ride records a heart rate of 0. If you see no prompt: Karoo Settings → Apps → veloVigil → Permissions.
Same Settings screen: paste the code into Invite Code, tap Register with Invite Code. Your Rider ID (rider_…) appears right there. Write it down; it is your dashboard address.
Two pairings at once give you a fight over one strap: double readings, or 30–40 bpm nonsense. One pairing, through veloVigil.
This is the step nobody could see. The H10 asks the Karoo for an encrypted link; the Karoo's own sensor list never needs it, but veloVigil goes through Android, and Android puts the question in a notification shade a Karoo never shows you. Unanswered, it times out, the link drops, and every ride records a heart rate of 0 — the 0.2.x bug. If you missed it, the request comes back every ~40 seconds until you accept it. veloVigil Settings says H10 PAIRING REQUEST WAITING while it's up.

Start a ride like normal. Ten minutes is enough for a first check. veloVigil uploads every 5–10 seconds while it has signal and buffers when it doesn't.
Your dashboard: velovigil-fleet.robert-chuvala.workers.dev/dashboard/<your Rider ID>. The ride should appear with a heart rate that isn't 0. If it is 0, go back to steps 3, 5 and 6.

Paste, don't link. Claude's web tool can't reach the API from claude.ai, so a link fails and the paste works. Nothing goes to us.
Prompts that work well · What's in the export

Stuck? Reply to your invite email with a photo of the screen. That's the support channel; it's read.