Neon CLI commands automate branch-first Postgres development

Three new CLI commands (link, checkout, env pull) eliminate manual branch and connection string management by coupling database branching to your git workflow.

June 18, 2026

Summary

Cuts boilerplate for isolated per-feature databases and keeps env variables in sync with active branch, critical for both local dev and agent-driven feature loops. Removes the friction that makes branch-first development feel optional.

Why it matters

Implementation verdict

Replaces manual neonctl set-context + env variable juggling. Requires nothing extra—works with existing Neon Serverless Postgres setup. Opt-in env pull via @neondatabase/env package if you skip .env files. Ready now for CLI, neonctl dev coming later. Worth adopting if you're already on Neon; transforms it from possible to frictionless.

Sources

1.neonctl link connects your local dev workspace to a Neon project, the same way vercel link does for your Vercel project
2.neonctl env pull fetches the current branch's Neon environment variables into your existing .env file, or .env.local if you don't have one
3.env pull is optional. You can opt out and we give you alternative ways to inject your Neon env variables for local dev
4.An agent can run neonctl checkout between tasks to give itself a fresh, isolated database per feature with no shared state to corrupt

Dev Signal

Get briefs like this in your inbox — free, 3x a week.

100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.

Read the full issue →All briefs