free-games-claimer documents a captcha it cannot solve
Automatically claims free games and DLCs on the Epic Games Store, Amazon Prime Gaming and GOG.
At a glance
- What is it?
- free-games-claimer drives a real Firefox browser through Playwright to claim store giveaways for Epic Games, Amazon Prime Gaming and GOG, and it ships as a container with a noVNC desktop for the first login. The parts worth reading before you run it are the ones the page admits: a captcha that still breaks the Docker path, credentials carried in environment variables, a remote desktop port published with no password, and a manifest version, 1.4.0, behind the newest tag, v1.8.
- Who is it for?
- free-games-claimer fits a self hoster with a spare machine or a home server who wants the Epic and Prime Gaming giveaways claimed without being awake when the claim window opens, and who is willing to complete a first login by hand in a remote browser. It does not fit anyone who would rather hand a store password to a script than to the store's own login page in a browser they can watch.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 10 days ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- vogler/free-games-claimer4,290 ★ · +70
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| vogler/free-games-claimer | 4.2k | 4.3k |
70 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
One script per store, and a manifest entry point that is not there
The runnable surface is one file per store. The tree carries epic-games.js, prime-gaming.js, gog.js, unrealengine.js, steam-games.js and aliexpress.js at the top level, next to an entrypoint shell script, a compose file and a source directory.
The page advertises four of those. Epic Games Store, Amazon Prime Gaming and GOG are the supported three, and Unreal Engine marketplace assets are listed as experimental with a link to the tracking issue, using the same login as Epic Games. A fifth store, Xbox games with Gold, appears in the page only as a commented out line pointing at its own issue.
So the tree holds two more scripts, one for Steam and one for AliExpress, and the default container command runs just three of the six. The package manifest adds a small inconsistency of its own: it declares index.js as the entry point, and no such file sits at the top level.
The per-store split is also how you narrow the work, since you can override the default command to run one store or several.
The Docker path currently trips a captcha, and the page says so
The primary install is a container image from the project's own registry, and the very next paragraph under it is a warning. The container currently presents a captcha challenge for Epic Games, and until the linked issue is fixed the page recommends running the epic-games script directly on the host without Docker.
That is an unusual admission to place directly under an install command. The same problem appears in the release history: the 1.6 release is named for fixing an unsolvable captcha in Docker, among other things, and the current text says the problem is still there.
The consequence for a user is a split deployment. Docker remains the convenient route for Prime Gaming and GOG, while the store most people care about, Epic Games, is the one the page steers you away from the container for.
So the honest summary of the install story is that there are two supported paths and neither is universally recommended.
Playwright Firefox, a fingerprint injector and a stealth plugin
The dependency list explains the approach. There is a Playwright build for Firefox rather than a full browser package, and beside it two libraries whose only job is to change how the browser presents itself: a fingerprint injector and a stealth plugin for Puppeteer Extra.
The rest of the list is ordinary automation plumbing: a low-level JSON database for the claimed game records, a dotenv loader, a prompt library for the terminal questions, a one time password library, and a colouring library for output.
That the one time password libraries sit next to per store OTP key variables is worth noticing. The page describes a first run where you type email, password and a one time code into the terminal, but the configuration also accepts an OTP key per store, which means the second factor can be computed from a stored secret instead of typed each time.
Data lands in the named volume: JSON files with claimed games, codes to redeem, and screenshots.
A remote desktop port published with no password by default
The container is built so you can watch the automation, which means it ships a virtual framebuffer, a VNC server and a browser based VNC client, and it publishes that client on a port:
docker run --rm -it -p 6080:6080 -v fgc:/fgc/data --pull=always ghcr.io/vogler/free-games-claimerThe page is direct about where to go: open the address on port 6080 in a browser to interact with the browser running inside the container, or connect a VNC client on port 5900 instead. The compose file publishes 6080 and leaves 5900 commented out, while the npm script for running the container publishes both.
Now the part to check before deploying. The configuration table has a remote desktop password variable whose default is empty, described as no password used by default. The same endpoint is where you type your store password on the first run, so leaving it unset publishes an unauthenticated view of that session to anything that can reach the port.
Setting it is one environment variable, and the compose file's own example shows where environment variables go.
Credentials, timeouts and browser geometry, all from the environment
Everything is configured through environment variables, and the table of defaults is the reference worth keeping.
A generic email and password pair exists and is overridden per store: separate Epic Games and Prime Gaming variables for email, password and one time key, plus a parental controls pin for Epic. The browser profile directory defaults to a path under the data volume, which is what lets you run more than one account by pointing it elsewhere.
Timing is explicit. Any page action gets 60 seconds, and login gets 180, with the note that it will wait twice because there are two ways to log in, the terminal prompt and the manual browser login. If it still waits after you are already logged in, the page says to restart and open an issue.
Two defaults deserve a second look. The browser visibility variable is listed with a default of 1, while the same row explains the browser is not shown when running outside Docker, so the table's default is really a Docker default. And a struck out paragraph describes a guided first run configuration assistant that would have saved settings to a file, which is not available.
Node 20 in the image, node 17 declared in the manifest
The container is built from Ubuntu Jammy rather than from a Playwright base image, with the Playwright option commented out at the top and a credit to Microsoft's own Dockerfile for the same idea. Node is installed from the NodeSource repository for the 20 release line, with the signing key fetched and dearmoured into the keyring directory rather than trusted blind.
The rest of the image is what a browser needs to start without a display: a virtual framebuffer, a VNC server, the noVNC client and its websocket bridge, an init process, a line ending converter, and pip for the notification tool. Then a long list of GTK, cairo, atk and dbus libraries, followed by an autoremove and a purge of the apt caches, the temporary directory and the documentation.
Two small steps at the end are easy to miss:
RUN ln -s /usr/share/novnc/vnc_auto.html /usr/share/novnc/index.html
RUN pip install appriseThe first makes the noVNC client answer on the root path so the published port works directly. The second installs the notification tool outside Node, which is why the non container instructions tell you to install it with pip as a separate step. The manifest itself declares support for node 17 or newer, so the runtime floor and the image are not the same number.
The manifest says 1.4.0 and the newest tag says v1.8
The package manifest declares version 1.4.0 with the AGPL, spelled as AGPL-3.0-only. The release history goes further: 1.6 in December 2023, 1.7 in March 2025 and 1.8 in May 2025, with the 1.6 release carrying a name that describes its contents, fixing an unsolvable captcha in Docker, adding Prime Gaming downloadable content and improving the development setup, while the two later releases carry only their tag as a name.
So the version string in the package cannot identify a build, and the container image is tagged with a moving name rather than a number. Anyone pinning this tool is pinning a commit, not a version.
The last push on the default branch is dated 2026-09-02, with 4,243 stars, 289 forks and 143 open issues behind it. The maintainer also links a SonarCloud project at the top of the page, and asks for pull requests in a single line under the store list.
Editorial conclusion
free-games-claimer fits a self hoster with a spare machine or a home server who wants the Epic and Prime Gaming giveaways claimed without being awake when the claim window opens, and who is willing to complete a first login by hand in a remote browser. It does not fit anyone who would rather hand a store password to a script than to the store's own login page in a browser they can watch. Before deploying it, check five things. Whether the captcha issue that the page flags is still open for the store you care about, because the recommended workaround is to abandon the container for that one script. Whether you set a remote desktop password before publishing the noVNC port, since the default is no password at all. Where your credentials end up, because email, password and one time password keys are read from environment variables and the browser profile lives in a named volume that keeps the session. Which stores you actually expect, since the default command runs only three of the six scripts in the tree. And which version you are running, because the manifest cannot tell you: it says 1.4.0 while the newest tag is v1.8.
Frequently asked questions
How do I run free-games-claimer?
The easy path is a container image that publishes port 6080 and keeps its data in a named volume called fgc, with the default command claiming games for the three supported stores in turn. For local development you install Node.js, clone the repository, run npm install and then run the script for the store you want.
Which stores does free-games-claimer support?
Epic Games Store, Amazon Prime Gaming and GOG are the supported ones, and Unreal Engine marketplace assets are listed as experimental using the same login as Epic Games. The repository tree also contains Steam and AliExpress scripts.
Does free-games-claimer need a visible browser?
No. Every script starts an automated Firefox instance that is hidden by default, and inside the container the browser lives in a virtual framebuffer that you can open in a browser on port 6080. Outside Docker you can set the SHOW variable to 1 to see the interface.
Where does free-games-claimer store my login details?
Credentials come from environment variables, with generic email and password values that Epic Games and Prime Gaming variables override, plus an OTP key per store for two factor accounts. The browser profile and the JSON records of claimed games live in the data volume mounted at the data path.
How do I update free-games-claimer?
The container is run with pull always, so a fresh run fetches the current image. For a local checkout the page says to pull the repository and run npm install again, and it notes that Playwright downloads its own Firefox build into a cache in your home directory during install.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/vogler-free-games-claimer)Star history chart for your README
[](https://hysenlabs.com/projects/vogler-free-games-claimer)Was this useful?