neonctl neon-auth enable, status, and disable commands
Introduced 2026-06-08 · score 0.95
HOW TO USE IT
To manage Managed Better Auth on a branch, run `neon neon-auth enable`, `status`, or `disable`. The CLI resolves project and branch context when the corresponding flags are omitted, selecting a sole match or prompting when multiple options exist.
neon neon-auth enableneon neon-auth statusneon neon-auth disableWHY THIS HELPS
Manage Neon Auth for a project branch from the CLI.
REQUIREMENTS AND LIMITATIONS
- Version: v2.23.0
- --project-id: Identifies the project; if omitted, CLI uses context, auto-selects when only one option exists, or asks for the flag.
- --branch: Identifies the branch; if omitted, CLI uses context, auto-selects when only one option exists, or asks for the flag.
- --delete-data: For `disable`, permanently deletes Managed Better Auth data and schema. The docs do not state whether this flag has an explicit value.
- Prerequisite: Authenticate with the Neon CLI; an unauthenticated command launches browser authentication. Alternatively, pass an API key with `--api-key`.
- Prerequisite: The documented CLI installation requires Node.js 18.0 or higher when installing with npm.
- All operations are branch-scoped.
FIRST-PARTY EVIDENCE
- https://github.com/neondatabase/neonctl/releases/tag/v2.23.0
- https://github.com/neondatabase/neonctl/pull/458
- https://github.com/neondatabase/website/blob/main/content/docs/cli/neon-auth.md
- https://github.com/neondatabase/neonctl
Check the installed version and the source before using it. Entry JSON