What you need
Challenger Bot runs on Windows 10 or 11 only — there's no Mac or Linux build.
You'll need a Twitch account for the channel you stream from, and two Windows
utilities the bot automates through: AutoHotkey (drives the
keyboard and mouse commands) and VoiceMacro (drives the voice
trigger-word feature used by !Word). Both are free downloads and
the setup wizard links you to them directly when it needs them.
1. Download and run Challenger Bot
Grab the standalone Windows build and run it — there's nothing to compile and no Python environment to configure. On first launch, Challenger Bot opens its setup wizard directly in your default browser.
2. Complete the browser setup wizard
The wizard walks you through four steps: entering your Twitch app credentials, authorizing via Twitch OAuth, selecting your channel, and launching the bot. You don't hand-edit any configuration file — the wizard writes everything for you, including the OAuth tokens it receives from Twitch.
3. Authorize your Twitch channel
Clicking through the OAuth step in the wizard sends you to Twitch's own authorization page. Approve the request there, and Twitch redirects you back to the wizard with an access token already in hand — the bot never sees your Twitch password.
4. Run your first command
Once the wizard finishes, the bot is live in your channel's chat. Have a viewer (or a second account) type one of the commands from the command reference — by default, ten chat messages total need to land before the first challenge threshold unlocks and something actually fires.
Troubleshooting
Nothing happens when chat types a command. Check that the message threshold has actually been hit — commands don't fire on the first message, they need the configured threshold (10 by default) before unlocking.
Keyboard/mouse commands don't do anything. Confirm AutoHotkey is installed and running — Challenger Bot triggers AutoHotkey scripts for several commands rather than injecting key presses itself, so if AutoHotkey isn't running, those specific commands are silently inert.
!Word doesn't speak or change the trigger word.
VoiceMacro needs to be installed and configured with a valid path — the bot
restarts VoiceMacro as part of this command, so if VoiceMacro isn't installed
at all, the command has nothing to restart.
The OAuth step fails or times out. Make sure you're approving the authorization request from the same Twitch account that owns the channel you want the bot to run in — authorizing from a moderator or viewer account instead of the broadcaster account is the most common cause of this failing silently.