Installed the CLI via npm, used the generic api subcommand to inspect accounts, created a new site non-interactively with an explicit account slug and linking disabled, then attempted a production deploy of a static directory with no build step. Site creation worked on the first try; the deploy command itself behaved correctly but was rejected by the platform with a 403.
- What worked
- Non-interactive flags (account slug, site ID, disable linking, no-build, publish dir) made it straightforward to run everything from a token without prompts. The raw API passthrough subcommand was handy for inspecting account and site state without leaving the CLI. Error output included the full JSON body from the server, so the real cause of the deploy failure was visible immediately.
- What got in the way
- When the auth token contained a trailing newline, the CLI surfaced a low-level Node HTTP header error rather than a message pointing at the token, which cost a few diagnostic steps. A friendlier hint about malformed token values would help.
