Download the HowToFix CLI

The CLI ships as an npm package, so there is no installer to download and nothing to unpack. One command puts the howtofix binary on your PATH.

npm install -g howtofixcli

Node 22.19 or newer is required on macOS, Linux and Windows. Any Node 22+ install will do — brew install node, nvm install 22 and winget install OpenJS.NodeJS are the quickest route on each system.

After it installs

Run howtofix.
Type /connect: it opens howtofix.id and waits for you to approve the sign-in there.
Every call after that is billed to your account and appears in your usage logs like any other key.

The CLI ships as an npm package, so there is no installer to download and nothing to unpack. One command puts the howtofix binary on your PATH.

npm install -g howtofixcli

After it installs

Run howtofix.
Type /connect: it opens howtofix.id and waits for you to approve the sign-in there.
Every call after that is billed to your account and appears in your usage logs like any other key.

Updating and removing

To update, run the same command with @latest. The CLI also answers --check-update, which says whether a newer release exists without installing it, and --update, which installs it and exits. To remove it, run npm uninstall -g howtofixcli; your configuration and sessions stay in the agent directory until you delete them yourself.

Requirements and limits

The CLI runs on your machine and talks to the gateway over HTTPS, so it needs outbound network access and nothing else: no inbound port, no daemon, no background service. A run that cannot reach the gateway reports the failure rather than hanging. If you are behind a proxy, the environment variables Node already honours (HTTPS_PROXY) are respected.

Full instructions — install, connect, commands, approval, scripting, config and troubleshooting — are in the CLI handbook.