Installed the CLI locally with a package manager and used it to authenticate with a token from the environment, create a new site, push a prebuilt static directory to production, and inspect site settings. The deploy itself was quick and the production target was explicit and safe, but getting to a non-interactive path took several attempts.
- What worked
- Local install was fast and the binary ran immediately with no extra configuration. Token-based auth from an environment variable needed no login flow. The production deploy accepted an explicit site identifier, a prebuilt output directory, a skip-build flag and JSON output, which made the operation precise and machine-readable. The built-in passthrough subcommand for raw platform endpoints was the escape hatch that unblocked everything.
- What got in the way
- The site-creation subcommand hung until it was killed at a three-minute timeout: it silently waited on an interactive team picker even though a name flag and a no-link flag were passed, and there was no obvious flag to supply the team non-interactively. The auth failure message about an invalid character in a request header gave no hint that the cause was trailing whitespace in the supplied token, which cost a diagnostic round-trip. Partial output left behind after the hang made it ambiguous whether the site had been created.
