Practical overview
When it fits
Use it when a game is listed among supported titles and you want a self-hosted browser-automation workflow for claims and status monitoring.
Who it is for
- Users of supported Telegram mini-app games who want to automate recurring claims.
- Operators comfortable running a self-hosted Python application through Docker, Linux, or Windows WSL2.
Documented uses
- Automate claim actions in supported Telegram mini-games.
- Track game-account and claim session status.
- Build a virtual node through browser interaction in xNode’s mini-game.
Requirements & limits
The public repository identifies the project as open source under the MIT license.
- Check the documented supported-game list and launch commands before setting up a session.
- Docker is the README's quick-start route; standalone Linux installation is documented for Ubuntu-style systems, and Windows 10 or 11 instructions use WSL2.
- The README estimates around 450 MB RAM per session during setup and claims, compared with about 35 MB while idle; browser cache is estimated at 100–400 MB per session.
- The project describes browser interaction and says it does not use API hacks.
- A Telegram bot relay has separate setup instructions and is not required by the documented Docker launch sequence.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Start and check a Docker-based game session
Use the documented Docker route to start the application and view account status.
Before you start
- Docker Desktop or CLI Docker on a PC or VPS.
- A terminal and the project's Docker image.
Steps
Start the container with the command below.
docker run -d --name telegram-claim-bot --restart unless-stopped thebrumby/telegram-claim-botEnter it with the command below.
docker exec -it telegram-claim-bot /bin/bashLaunch a game using
./launch.sh.View account status and logs with
./launch.sh status.
Expected outcome
A running container with a launched game session, with a command for viewing account status and PM2 logs.
Guide limitations
- Consult the project's supported-game launch commands for game-specific options.
- The README notes that sessions use machine memory, CPU and disk space; active claim phases require more resources than idle sessions.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 6 October 2026
- Original website title
- thebrumby/HotWalletClaimer · Official homepage title · retained in its source language

