--rewget-no-fallback Fail fast on a block instead of escalating. The right choice in CI when you want a regression to surface loudly.
Home / Quickstart
Install rewget, alias it over wget, and download something that was blocking you. There is nothing else to configure — the three-stage fallback is on by default.
Pick your package manager. Linux and macOS are supported.
$ brew install neul-labs/tap/rewget $ npm install -g rewget $ uv tool install rewget # or: pip install rewget $ cargo install rewget There is also a one-line install script in the GitHub repo.
$ echo 'alias wget=rewget' >> ~/.zshrc
Now every wget in your scripts, Makefiles, and CI gets the fallback. On sites that never block, it is still just wget.
$ rewget https://protected.example/dataset.zip [stage 1: wget] 403 Forbidden → escalating [stage 2: rquest/chrome131] 200 OK dataset.zip 100%[============>] 128M 22.4MB/s [cached: protected.example → stage 2, 7d]
--rewget-no-fallback Fail fast on a block instead of escalating. The right choice in CI when you want a regression to surface loudly.
--rewget-list-profiles Print the installed browser fingerprint profiles (Chrome 131/130, Firefox 136/133, Safari 18, Edge 131).
--rewget-update-profiles Pull the latest Ed25519-signed profile set. Runs only when you invoke it — no silent fetches.
--rewget-fallback-codes Configure which HTTP status codes trigger escalation to stage 2 and 3 (defaults cover the usual 403 / 429 blocks).
Want the full picture first?