# free-pi (FreePi) smoke check, 2026-10-20

Environment: Linux sandbox, Node v22.23.3 (installed locally via the `node@22` npm package; the box's system Node 20.19.2 is refused by free-pi-cli: "needs Node with zstd support (Node >= 22.15, or >= 23.8)"). Isolated HOME, `FREEPI_NO_AUTO_UPDATE=1`, stdin closed.

Commands and output (free-pi-cli 0.4.7 from npm):

```
$ free-pi-cli --version
free-pi-cli 0.4.7

$ free-pi-cli --help
free-pi — free AI coding in your terminal; ads pay for the inference.

Usage:
  free-pi-cli                 start the coding agent (first run: consent + GitHub sign-in)
  free-pi-cli --session <id>  resume a previous session
  free-pi-cli logout          remove the stored sign-in token; the next run signs in again
  free-pi-cli mcp <command>   add, remove, list, or sign in to your own MCP servers
                              (free-pi-cli mcp --help for details)
  free-pi-cli --version       print the CLI version
  free-pi-cli --help          show this help

Environment:
  FREEPI_BASE_URL        override the backend base URL (default https://api.freepi.ai)
  FREEPI_NO_AUTO_UPDATE  disable in-place self-update for this run
  FREEPI_NO_GRAVITY_PIXEL=1  do not run Gravity's ad-measurement pixel
```

Not run: the fixed cli-agent tasks (T1-T3). A session needs the consent screen plus a GitHub device-code sign-in in a browser, and accepting the consent lets free-pi save and train on session traces, which we did not accept on a test account. No score is given until the suite runs.