Changelog

Added

• --version — prints the esp-tool version, commit, and build date. Also shown as the second line of --help output. No -v shorthand, to avoid colliding in spirit with the unrelated -v, --verbose flag every subcommand already has.

Fixed

• Config file (.esp-tool.yaml) string values starting with ~ (e.g. dir: ~/esphome) were passed through literally instead of expanding to the user's home directory, since config values — unlike CLI flags — are never shell-expanded.

Installation

Download the archive for your platform, extract it, and move esp-tool to a location on your PATH:

# macOS (Apple Silicon)
curl -sL https://github.com/gevgev/esp-tool/releases/download/v0.2.1/esp-tool_0.2.1_darwin_arm64.tar.gz | tar -xz
sudo mv esp-tool /usr/local/bin/

# macOS (Intel)
curl -sL https://github.com/gevgev/esp-tool/releases/download/v0.2.1/esp-tool_0.2.1_darwin_amd64.tar.gz | tar -xz
sudo mv esp-tool /usr/local/bin/

# Linux (amd64)
curl -sL https://github.com/gevgev/esp-tool/releases/download/v0.2.1/esp-tool_0.2.1_linux_amd64.tar.gz | tar -xz
sudo mv esp-tool /usr/local/bin/

# Windows (amd64) — PowerShell
Invoke-WebRequest -Uri https://github.com/gevgev/esp-tool/releases/download/v0.2.1/esp-tool_0.2.1_windows_amd64.zip -OutFile esp-tool.zip
Expand-Archive esp-tool.zip -DestinationPath .
Move-Item esp-tool.exe $env:USERPROFILE\AppData\Local\Microsoft\WindowsApps\

Note: On Windows, esphome is typically only available inside WSL2.
The native Windows binary works if esphome is on your PATH; otherwise
use the Linux build from within WSL2.

See the README for full setup instructions including zsh completion.