Local setup
A developer is setting up the Neon CLI locally for the first time.
Neon · Command
Authenticates the Neon CLI through a browser, which is the recommended interactive method. A personal API key is the documented alternative for non-interactive use.
The command starts browser-based authentication for the Neon CLI. After authorization, the CLI can access the user's Neon account without requiring an API key on each command.
neon authAuthenticates the CLI session with the user's Neon account; the documentation does not specify a command output value.
neon auth to start the browser authentication flow.NEON_API_KEY environment variable to avoid repeating it.neon authAuthenticates the Neon CLI through a browser.
A developer is setting up the Neon CLI locally for the first time.
A user wants to authorize CLI access without manually entering an API key for every command.
A script or CI job cannot open a browser.
Run neon auth. It uses browser-based authentication and opens a browser window for account authorization.
Follow-up: How would you authenticate in CI? Use a personal Neon API key, typically supplied through the environment or command configuration rather than browser interaction.
The documented command is neon auth; the current CLI documentation uses neon as the executable name.
Follow-up: How can a command use an API key without repeating it? Set the NEON_API_KEY environment variable.
A personal Neon API key is the alternative documented for authentication. It can be created in the Neon Console and passed to CLI commands.
Follow-up: What is the recommended interactive method? Browser-based web authentication is recommended in the quickstart.
neonNEON_API_KEYneon projects list --api-key