Automatically farm Twitch and Kick drops from your browser or a headless Docker setup.
翻译准备中
正在加载完整 README。 以下为已保存的摘录。
Farm Twitch and Kick drops automatically. Lurkloot finds eligible campaigns, watches the right channel, switches when needed, and claims your rewards—all through the browser session you already use.
Website · Install from the Chrome Web Store · Changelog查看完整 README ↗It is free, fully open source, and runs as a browser extension or, in beta, as a headless CLI with Docker.
Twitch
Kick
Each platform has its own switch, games, order, and channel list. Turn on one, or both.
You sign in to Twitch or Kick as usual, enable the platform, and leave Lurkloot running. It detects what you can still earn, picks a live channel that counts toward it, and switches on its own when the stream goes offline, the reward finishes, or a better target becomes available.
Most watching happens in the background, with no stream video and no video ads. If a watch cannot continue that way, Lurkloot opens a muted tab for that channel. That tab plays the stream, so a platform ad can run there.
The popup is one workspace for both platforms. The queue shows what is being farmed. Pin campaigns and drag them into order, rank favourite games, limit farming to chosen categories, block categories, exclude channels, and choose which reward Lurkloot prefers when several are available.
When no drop, extension, or other reward is eligible, the Watchlist takes over. Add the channels you want watched, and Lurkloot picks one that is live. On Kick, that watch time also counts toward your profile level and badges.
Fortnite collects sprites and phase rewards. NoPixel earns daily packs and can join giveaways. Both stay off until you enable them in the popup, and enabling one asks the browser for access to that extension's site. Drop campaigns are still watched first unless you change the order.
TwitchDropsMiner is the usual desktop alternative. Around it are forks, rewrites in Go or Rust, command-line tools, and websites you host yourself with Docker. Starting those means a language runtime, a terminal, or a server.
Lurkloot is easier to set up. It installs from the Chrome Web Store into the browser you already use, and it uses the session you are already signed in with. Twitch and Kick share one popup. A beta CLI and Docker image run the same engine on a server when you want that instead.
Farming starts on its own. Leave the browser running.
Firefox builds on GitHub Releases are best-effort and untested. Testers are welcome — please report what you find.
To try a pre-release Chrome build, see Installing a pre-release build.
The CLI and Docker image are in beta. Twitch drop claiming from the CLI alone is not fully verified yet. They run the same farming engine on a server, a NAS, or any machine that can run a container. There is no browser window and no stream video. The published image is multi-architecture (amd64 and arm64): ghcr.io/jamezrin/lurkloot-cli.
Sign in once, then leave the container running. For Twitch, sign in through a browser and paste back the address Twitch sends you to:
docker run --rm -it -v "$PWD/data:/data" \
ghcr.io/jamezrin/lurkloot-cli:latest auth twitch browser-login
That login sees every drop campaign. auth twitch device-login needs no browser, but Twitch only lets it see campaigns you have already started, so it finds the rest only on live channels of your chosen games. Kick login on the same image is auth kick device-login. Authentication, configuration, and the command that keeps farming in the background are in the CLI guide.
Fortnite and NoPixel run in the extension. The CLI farms Twitch and Kick.
lurkloot serve farms like the CLI's run and also serves the Lurkloot app, at an address you open in your browser. It has the same views as the extension popup, in a full window, with a page to sign in to Twitch and Kick. With Docker, use the compose file:
mkdir lurkloot && cd lurkloot
curl -fsSLO https://raw.githubusercontent.com/jamezrin/lurkloot/main/packages/cli/compose.yaml
echo "LURKLOOT_SERVE_TOKEN=$(openssl rand -hex 32)" > .env
docker compose up -d
Open http://127.0.0.1:8420 and enter the token from .env once per tab. The port is reachable from this machine only. Running it locally, opening it from another machine, and the security model are in the CLI guide.
The extension uses the Twitch and Kick sessions already in your browser. It does not ask for your password, and it does not send your activity to a Lurkloot server. There is no Lurkloot account and no telemetry. The only way session data leaves the extension is Settings → Export credentials, which you run yourself to set up the CLI. That writes a file on your machine. Details are in the privacy policy.
If something is wrong, open a bug report. Include your browser, the platform, and what you expected to happen. Leave out passwords, cookies, and session tokens.
Ideas belong in a feature request.
Lurkloot is maintained by one person, using the best frontier models and workflows written for this repository. The models write most of the code. The maintainer owns the architecture, the design, and the product decisions. An issue or a pull request has to come from a person who has read it, checked it, and can discuss it. Low-effort and fully automated submissions are not welcome.
Bug reports, translations, documentation, and code are welcome. Pick the guide for the change you have in mind:
| Guide | Use it for |
|---|---|
| Contributing | Repository setup, branch and commit conventions, and the checks a pull request should pass |
| Architecture | How the extension, farming engine, popup, and CLI fit together |
| Translations | Correcting a locale catalog |
| CLI guide | The headless runtime, auth, and Docker |
| Releasing | How versions are cut and published |
The source is licensed under the Apache License 2.0.
Lurkloot is an independent project. It is not affiliated with, endorsed by, or sponsored by Twitch, Kick, Epic Games, or NoPixel. Platform behavior and terms can change, and automating viewing may be restricted by those terms. Use Lurkloot at your own discretion.