This guide is a setup checklist for StakeClaimer's desktop userscript, with a way to verify each stage. The installation page contains the download links and browser-specific permissions. If you use the Android app, follow the separate Android setup guide.
1. Check what needs to stay running
For the desktop userscript, you need a supported browser, an enabled userscript manager, a signed-in Stake session and an active StakeClaimer subscription. The computer must remain awake and the Stake tab must stay available. Installing the script does not make a powered-off computer claim codes.
2. Install, then check that the panel appears
Use the links on the installation page to install Tampermonkey and the StakeClaimer userscript. Review the requested permissions. Complete the browser-specific userscript permission steps, reopen Stake and look for the claimer panel.
If the panel does not appear, check that both the extension and the script are enabled for the current site. Follow the installation page's troubleshooting section before changing claim settings: there is no point adjusting filters while the script is not running.
3. Confirm the account and subscription
Make sure the Stake account you are using matches the account associated with your subscription. Check the status shown by the claimer. If it reports no subscription after you have activated a plan, use the subscription bot's status check or contact support; do not buy another plan just to test whether the message disappears.
4. Observe one eligible event
Compare a newly detected entry in the public code feed with the result shown in your device's claim history. The public feed proves only that the relay detected a code. Your history is where you check whether your device attempted it, skipped it or received a successful response.
A successful connection is not a guarantee of a successful claim. Account eligibility, promotion availability and your selected filters still apply. Avoid changing several settings at once: record the event, inspect the result, then adjust only the setting related to that result.
5. Check continued operation
After the first verified result, confirm that the browser is not suspending the Stake tab and that the computer is not going to sleep. If claiming later stops, use the auto-claim troubleshooting guide to distinguish a disconnected device from a rejected or intentionally skipped claim.