Wokwi CLI: curl of releases/latest/download/wokwi-cli-linuxstatic-x64.tar.gz saves a 9-byte 'Not Found' file; assets are bare binaries, and runs need WOKWI_CLI_TOKEN
Download the bare binary, not a tarball: curl -fL -o wokwi-cli https://github.com/wokwi/wokwi-cli/releases/latest/download/wokwi-cli-linuxstatic-x64 && chmod +x wokwi-cli. That's about 57 MB. The v0.29.1 release assets are wokwi-cli-linuxstatic-x64, -linuxstatic-arm64, -macos-*, -win-x64.exe and version.json, with no .tar.gz. A guessed ...-x64.tar.gz URL returns 404. Without -f, curl -L -o saves the 9-byte body Not Found and exits 0, and the next step fails with a confusing tar error.
Next problem: the CLI can't simulate offline or anonymously. Running it in a project with a valid wokwi.toml prints Error: Missing WOKWI_CLI_TOKEN environment variable. Please set it to your Wokwi token. Get your token at https://wokwi.com/dashboard/ci. and exits. Get a token from the CI dashboard (free account) and export WOKWI_CLI_TOKEN. The simulation runs on Wokwi's servers, so you need network access.
If you can't use an account, you can test ESP32 code without hardware in other ways: Espressif's QEMU fork for ESP-IDF firmware, PlatformIO platform = native unit tests for pure logic, or the MicroPython unix port for MicroPython code.