We scan this tool’s changelog a few times a day and keep the changes that would alter your agent’s next action: 9 since June 2026, each linked to its source.
neonctlWhen scaffolding a repository from a Neon template, run `neonctl bootstrap <target> --template <id>`; use `.` for the current directory. The target must be empty unless you pass `--force`.
neonctl bootstrap <target> --template <id>When the artifact is at most 104857600 bytes, upload it to an existing bucket with `neonctl bucket object put <bucket>/<key> --file <path> [--content-type <ct>]`; the CLI obtains a presigned PUT URL and streams the file. The v2.25.0 release notes document the upload feature and 100 MB cap.
neonctl bucket object put <bucket>/<key> --file <path> [--content-type <ct>]When linking an existing project with multiple branches, run `neonctl link` and select a branch; single-branch projects are pinned automatically. After `link` or `checkout` pins a branch, it pulls Neon environment variables by default; pass `--no-env-pull` to skip the pull, or run `neonctl env pull` to refresh them.
neonctl linkWhen reconciling a branch from a repository policy, define the policy in `neon.ts`; run `neon config status` to inspect it, `neon config plan` to preview changes, and `neon config apply` (or `neon deploy`) to apply them.
neon config status [--project-id <id>] [--branch <id|name>] [--config <path>]When adding, removing, or changing functions while `neon dev` runs in config mode, edit `neon.ts`; the CLI reconciles functions by slug, hot-adding and removing servers and restarting only functions whose configuration changed. This applies only when running from `neon.ts`, not in single-`--source` mode.
neon devWhen you need a local dotenv file populated with a Neon branch’s variables, run `neonctl env pull` from a directory with Neon context. It writes to `.env` if present, otherwise `.env.local`, and preserves other lines.
neonctl env pullTo 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 enableWhen switching a repository’s Neon context to a branch, run `neonctl checkout <id|name>`; it resolves the branch for the active project and updates `.neon` so subsequent commands use it. In CI or without a TTY, pass the branch explicitly.
neonctl checkout <id|name>When you need subsequent `neonctl` commands in a directory or its subdirectories to use a Neon project context, run `neonctl link` there. Use interactive prompts, the documented flags or `--params` for scripts, or `--agent` for the JSON follow-up flow; the command writes `.neon` with organization, project, and default branch context.
neonctl link