--- title: "neondatabase/agent-skills" description: "Agent Skills for Neon Severless Postgres" source: https://github.com/neondatabase/agent-skills ref: main license: Apache-2.0 licenseName: "Apache License 2.0" canonical: https://skillsdocs.com/neondatabase/agent-skills base: https://github.com/neondatabase/agent-skills/blob/main/ provenance: mixed chapters: 9 inlined: 9 withheld: 0 words: 17986 updated: 2026-09-23T15:14:52Z generator: "Skills Docs" --- > **neondatabase/agent-skills** — every Agent Skill in this repository, inlined verbatim. > > Canonical HTML: https://skillsdocs.com/neondatabase/agent-skills > Per-skill Markdown: https://skillsdocs.com/neondatabase/agent-skills/.md > Machine manifest: https://skillsdocs.com/neondatabase/agent-skills/.well-known/agent-skills/index.json > JSON: https://skillsdocs.com/api/v1/books/neondatabase/agent-skills > Install: `npx skills add neondatabase/agent-skills` > Upstream: https://github.com/neondatabase/agent-skills @ `main` > Licence: Apache-2.0 > > Content is mirrored from GitHub and © its authors, served unmodified. Takedown: https://github.com/DreambaseAI/skillsdocs/issues/new?labels=takedown&title=Takedown+request # neondatabase/agent-skills Agent Skills for Neon Severless Postgres - **Skills:** 9 - **Authorship:** mixed — 1 of 9 are credited — skills in use here, not published from here - **Inlined:** 9 (licence detected) - **Words:** 17,986 - **Reading time:** 83 min - **Stars:** 90 ## Table of contents 1. [neon-ai-gateway](https://skillsdocs.com/neondatabase/agent-skills/neon-ai-gateway.md) — One API and one credential for frontier and open-source LLMs, built into your Neon branch and powered by Databricks. Use when a user wants to call an LLM, add… 2. [neon-auth](https://skillsdocs.com/neondatabase/agent-skills/neon-auth.md) — Add authentication to a new app. Use for "add auth", "add login", Neon Auth (Managed Better Auth), identity routing, sign-up, sign-in, password reset, email OT… 3. [neon-functions](https://skillsdocs.com/neondatabase/agent-skills/neon-functions.md) — Long-running, serverless Node.js HTTP functions deployed onto your Neon branch, with DATABASE_URL injected automatically and compute that runs next to your dat… 4. [neon-object-storage](https://skillsdocs.com/neondatabase/agent-skills/neon-object-storage.md) — S3-compatible object storage that branches with your Neon project, so files and the database stay in sync across every branch. Use when a user wants object sto… 5. [neon-postgres-branches](https://skillsdocs.com/neondatabase/agent-skills/neon-postgres-branches.md) — Choose and create the right Neon branch type for testing and development. Use when users ask about Neon branching, migration testing with real data, isolated t… 6. [neon-postgres-egress-optimizer](https://skillsdocs.com/neondatabase/agent-skills/neon-postgres-egress-optimizer.md) — Diagnose and fix excessive Postgres egress (network data transfer) in a codebase. Use when a user mentions high database bills, unexpected data transfer costs,… 7. [neon-postgres](https://skillsdocs.com/neondatabase/agent-skills/neon-postgres.md) — Guides and best practices for working with Lakebase Postgres on Neon: connections, pooled vs direct, schema migrations, branching, autoscaling, scale-to-zero,… 8. [neon](https://skillsdocs.com/neondatabase/agent-skills/neon.md) — Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, and the AI Gateway. Start here to choos… 9. [score-eval](https://skillsdocs.com/neondatabase/agent-skills/score-eval.md) — No description. ## Front matter _The repository README, verbatim except that relative links are resolved against https://github.com/neondatabase/agent-skills/blob/main/._ Neon Logo fallback # Agent Skills A collection of [Agent Skills](https://agentskills.io/) and agent integrations for Neon — a complete set of cloud backend primitives built around Lakebase Postgres, for developers, startups, and agent platforms, from Databricks. ## What are Agent Skills? Skills are folders of instructions, scripts, and resources that agents can discover and use to do things more accurately and efficiently. Once installed, skills are automatically invoked by the agent upon detection of relevant tasks. It all starts with the `SKILL.md` file in the skill's directory. It's the entry point and allows agents to progressively discover information as needed. ## Available Skills ### Neon [![neon](https://shieldcn.dev/skills/installs/neondatabase/agent-skills/neon.svg?variant=branded&size=xs&label=neon)](https://skills.sh/neondatabase/agent-skills/neon) An overview of Neon for apps and agents — Lakebase Postgres, Auth, Data API, Object Storage, Compute Functions, and the AI Gateway — and how to get started. Includes Claimable Neon for use with no Neon account. ### Neon Postgres [![neon-postgres](https://shieldcn.dev/skills/installs/neondatabase/agent-skills/neon-postgres.svg?variant=branded&size=xs&label=neon-postgres)](https://skills.sh/neondatabase/agent-skills/neon-postgres) A comprehensive index of documentation and best practices for Lakebase Postgres on Neon, to set your agents up for success. ### Neon Auth [![neon-auth](https://shieldcn.dev/skills/installs/neondatabase/agent-skills/neon-auth.svg?variant=branded&size=xs&label=neon-auth)](https://skills.sh/neondatabase/agent-skills/neon-auth) Neon Auth (Managed Better Auth) for login, users, and sessions that branch with the database, including which Better Auth plugins are supported and when to run self-managed Better Auth on Neon instead. ### Neon Postgres Agent Platforms [![neon-postgres-agent-platforms](https://shieldcn.dev/skills/installs/neondatabase/neon-for-agent-platforms/neon-postgres-agent-platforms.svg?variant=branded&size=xs&label=neon-postgres-agent-platforms)](https://skills.sh/neondatabase/neon-for-agent-platforms/neon-postgres-agent-platforms) For agent platforms, codegen tools, and multi-tenant SaaS products that provision and run Lakebase Postgres, Object Storage, Functions, Managed Better Auth, and/or AI Gateway access for their users. Includes a companion skill and samples in [neondatabase/neon-for-agent-platforms](https://github.com/neondatabase/neon-for-agent-platforms). ### Neon Postgres Branches [![neon-postgres-branches](https://shieldcn.dev/skills/installs/neondatabase/agent-skills/neon-postgres-branches.svg?variant=branded&size=xs&label=neon-postgres-branches)](https://skills.sh/neondatabase/agent-skills/neon-postgres-branches) Choose and create the right Neon branch type for migration testing and isolated development workflows, including schema-only branches for sensitive data and reset-from-parent workflows to quickly realign child branches. ### Neon Postgres Egress Optimizer [![neon-postgres-egress-optimizer](https://shieldcn.dev/skills/installs/neondatabase/agent-skills/neon-postgres-egress-optimizer.svg?variant=branded&size=xs&label=neon-postgres-egress-optimizer)](https://skills.sh/neondatabase/agent-skills/neon-postgres-egress-optimizer) Diagnose and fix excessive Postgres egress (network data transfer) in a codebase. Use when investigating high database bills, unexpected data transfer costs, or query overfetching. ### Neon Object Storage [![neon-object-storage](https://shieldcn.dev/skills/installs/neondatabase/agent-skills/neon-object-storage.svg?variant=branded&size=xs&label=neon-object-storage)](https://skills.sh/neondatabase/agent-skills/neon-object-storage) S3-compatible object storage that branches with your Neon project, so files and database rows stay in sync across dev, preview, and production environments. ### Neon AI Gateway [![neon-ai-gateway](https://shieldcn.dev/skills/installs/neondatabase/agent-skills/neon-ai-gateway.svg?variant=branded&size=xs&label=neon-ai-gateway)](https://skills.sh/neondatabase/agent-skills/neon-ai-gateway) One API and one Neon credential for frontier and open-source LLMs from multiple providers, built into your branch and compatible with the OpenAI, Anthropic, and Vercel AI SDKs. ### Neon Functions [![neon-functions](https://shieldcn.dev/skills/installs/neondatabase/agent-skills/neon-functions.svg?variant=branded&size=xs&label=neon-functions)](https://skills.sh/neondatabase/agent-skills/neon-functions) Long-running, serverless Node.js HTTP functions deployed onto your Neon branch, with `DATABASE_URL` injected automatically and compute that runs next to your data. ## Installation ```bash npx skills add neondatabase/agent-skills ``` ### Agent Plugin The repository root is a portable [Agent Plugins v1](https://agent-plugins.org/specification) package, so any conforming client can install it straight from this repo. The root [`plugin.json`](https://github.com/neondatabase/agent-skills/blob/main/plugin.json) declares the plugin, [`mcp.json`](https://github.com/neondatabase/agent-skills/blob/main/mcp.json) declares the [Neon MCP Server](https://mcp.neon.tech), and the skills are the directories under `skills/`. The Claude Code and Cursor packaging under `plugins/` remains available for clients that expect those formats. ### Claude Code Plugin You can also install the skills as a Claude Code plugin, which bundles the Neon agent skills and the [Neon MCP Server](https://mcp.neon.tech) for natural language database management: ``` /plugin marketplace add neondatabase/agent-skills /plugin install neon-postgres@neon ``` After installation, you'll be prompted to authenticate with Neon via OAuth when you first use MCP tools. The top-level `skills/` directory remains the source of truth. Plugin folders ship real copies of the skill directories they expose, regenerated with `npm run sync:plugins` — see [CONTRIBUTING.md](https://github.com/neondatabase/agent-skills/blob/main/CONTRIBUTING.md) for details. ### Cursor Plugin This repository also includes Cursor plugin packaging with the same scope as the Claude plugin (the Neon agent skills and the Neon MCP Server). Run this command in chat: ```text /add-plugin neon-postgres ``` ### Kimi Code Plugin Kimi Code CLI reads its own manifest at [`kimi.plugin.json`](https://github.com/neondatabase/agent-skills/blob/main/kimi.plugin.json), which points at the skills under `skills/` and declares the [Neon MCP Server](https://mcp.neon.tech). Install it from this repo in chat: ```text /plugins install https://github.com/neondatabase/agent-skills ``` Plugin changes apply to new sessions, so run `/new` afterward. ### Pi You can also install the skills in [Pi](https://pi.dev) from npm: ```bash pi install npm:@neon/skills ``` Or straight from this repo: ```bash pi install git:github.com/neondatabase/agent-skills ``` ## Usage Example prompts: ``` Get started with Neon ``` ``` Recommend a connection method for this project ``` ``` Set up Drizzle ORM with Neon ``` ``` Set up Neon Auth for my Next.js app ``` ``` Query the database using neon-js ``` ``` Create a new Neon branch using the API ``` ``` Use the serverless driver for edge functions ``` ``` Give me a quick temporary Postgres database ``` ``` Why is my Neon bill so high? ``` --- ## Part: Skills --- ## 1. neon-ai-gateway - **Source:** https://github.com/neondatabase/agent-skills/blob/main/skills/neon-ai-gateway/SKILL.md - **Raw:** https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon-ai-gateway/SKILL.md - **Markdown:** https://skillsdocs.com/neondatabase/agent-skills/neon-ai-gateway.md - **Licence:** Apache-2.0 — https://spdx.org/licenses/Apache-2.0.html --- name: neon-ai-gateway description: >- One API and one credential for frontier and open-source LLMs, built into your Neon branch and powered by Databricks. Use when a user wants to call an LLM, add AI/chat/an agent to their app, route between model providers (OpenAI, Anthropic, Google/Gemini, Meta, Alibaba, and more), or avoid juggling separate provider API keys and accounts — especially when they already use Neon and want AI requests to branch with their project. Works with the OpenAI SDK, Anthropic SDK, google-genai, the Vercel AI SDK, and Mastra by changing only the base URL. Triggers include "call an LLM", "add AI to my app", "chat completion", "model routing", "LLM proxy/gateway", "one API for all models", "use Claude/GPT/Gemini", "AI SDK", "Mastra agent", "Neon AI Gateway", and "log/rate-limit AI calls". metadata: parent: neon source: https://github.com/neondatabase/agent-skills/tree/main/skills/neon-ai-gateway --- **FIRST**: Use the parent `neon` skill for a Neon overview, getting started with Neon, Neon development best practices, and more. If the `neon` skill is not installed, fetch it from https://neon.com/docs/ai/skills/neon/SKILL.md or install it with: ```bash neon skills -s neon -y ``` # Neon AI Gateway Currently available in `aws-us-east-2`, `aws-us-east-1`, `aws-eu-central-1`, and `aws-ap-southeast-1`. The Neon AI Gateway is the LLM inference layer built into your Neon branch: one API and one Neon credential give you access to frontier and open-source models from many providers (Anthropic, OpenAI, Google, Meta, and more), all hosted and powered by Databricks. The catalog shifts over time, so treat `/v1/models` and the [models.dev Neon page](https://models.dev/providers/neon) as the source of truth rather than a fixed provider list. Your existing OpenAI/Anthropic/Gemini SDK works by changing only the base URL. Use this skill to help the user send model calls through the gateway, wire it into the AI SDK or Mastra, and switch providers without rewiring code. Deliver a working inference request, a configured agent, or a precise answer from the official Neon docs. ## When to Use Reach for the AI Gateway whenever an app or agent needs to call an LLM and the user would rather not manage model providers themselves: - **One credential instead of many provider accounts.** A single Neon credential reaches the entire model catalog across every provider Databricks hosts. No separate OpenAI / Anthropic / Google billing, keys, or signups to provision and rotate. - **Switch models without rewiring.** The unified endpoint is OpenAI-compatible and works with every model in the catalog — change one `model` field to move between Claude, GPT, and Gemini. Standard SDKs (OpenAI, Anthropic, google-genai) work with just a base-URL change. - **AI follows your branches.** Each branch has its own gateway endpoint, scoped with the same lineage as your database. AI requests from a preview/feature branch are isolated to that branch — the same isolation your data already gets — which makes preview, CI, and agent environments self-contained. - **No extra infrastructure, and it's already next to your data.** The gateway lives inside your Neon project (and is injected into Neon Functions automatically), runs on the same Databricks infrastructure that serves trillions of tokens a month, and supports streaming (SSE) out of the box. If the user already has a deep, single-provider integration and no interest in Neon branching or multi-model routing, a direct provider SDK is fine — but the moment they want one credential, model portability, or branch-scoped AI, this is the reason to use it. ## What It Does - **One API for all models** — Frontier and open-source models behind a single endpoint, addressed by their catalog ID (e.g. `claude-sonnet-4-6`, `gpt-5-mini`, `gemini-3-flash`). - **Standard SDKs, one URL change** — OpenAI SDK and AI SDK (OpenAI-compatible MLflow/Responses routes), Anthropic SDK (native Messages), google-genai (native Gemini). - **Branch-scoped** — Each branch gets its own gateway host; the Neon credential authorizes requests for that branch and its descendants. - **Streaming** — Server-sent events work on all endpoints with no extra configuration. ## Availability Check these preconditions before setting anything up: The AI Gateway is currently available in `aws-us-east-2`, `aws-us-east-1`, `aws-eu-central-1`, and `aws-ap-southeast-1`. Foundation model access requires a paid Neon plan. Confirm the user's project is in one of these regions. ### Enabling the gateway: plan and model-catalog gating The AI Gateway is credential-gated rather than a provisioning step, but two plan limits gate it — one blocks provisioning, the other only trims the catalog — and the CLI surfaces each: - **Free plan → provisioning is blocked.** `neon config apply` / `deploy` and `neon checkout` **refuse** to enable the gateway on a Free plan (the gateway can't serve requests there), with a friendly "upgrade to a paid plan, or remove `aiGateway`" error. A dry-run `neon config plan` and `neon env pull` don't provision, so they only **warn**. So: to use the gateway the project's account must be on a paid Neon plan. - **Paid plan with a reduced model catalog.** On a paid plan the gateway provisions and serves, but an account can start with a trimmed catalog — some flagship models (e.g. Anthropic Opus, OpenAI Codex / `*-pro`) are missing from `GET /v1/models`. This is expected; `neon env pull` (and the env pull bundled into `apply` / `deploy` / `checkout`) warns and links the user to their branch's AI Gateway page in the Neon Console (`https://console.neon.tech/app/projects//branches//ai-gateway`) to request access to more models. Verify what's actually available for the branch by reading `/v1/models` (see the models section below) rather than assuming the full catalog. When helping a user debug "the gateway isn't working" or "a model is missing", use `/v1/models` plus the account's plan to distinguish these two cases — a Free plan blocks provisioning entirely, while a reduced catalog on a paid plan just needs a model-access request. ## Setup The gateway is part of `neon.ts` (see the `neon` skill for the branch-first workflow and `neon.ts` basics). Enable it with `aiGateway`: ```typescript // neon.ts import { defineConfig } from "@neon/config/v1"; export default defineConfig({ aiGateway: true, }); ``` ```bash neon deploy # provisions the gateway on the linked branch ``` ## Neon Infrastructure as Code (`neon.ts`) The `aiGateway` toggle above is part of `neon.ts`, Neon's infrastructure-as-code file — one TypeScript file declares the gateway alongside every other branch service, in version control (see the `neon` skill for the full reference). Reconcile it against a branch the Terraform way: ```bash neon config status # print the branch's live config (is the gateway on?) neon config plan # dry-run diff of what apply would change neon config apply # enable the gateway on the branch (neon deploy is an alias) ``` The gateway is **branch-scoped**: each branch gets its own gateway host. When a `neon.ts` is present, `neon checkout` applies the policy as it _creates_ a branch, so a fresh preview/CI branch comes up with the gateway already enabled. Checking out an _existing_ branch doesn't reconcile it — run `neon deploy` to apply changes. Provisioning (`config apply` / `deploy`), `link`, and `checkout` also pull the branch's gateway credentials into your local `.env.local`, so local runs hit the same branch gateway as the deployed function (no manual `env pull` needed). ## Environment Variables When `aiGateway` is enabled, Neon injects the gateway credentials as **Neon-branded** env vars. Inside a deployed Neon Function these are injected automatically; locally, `neon env pull` writes them to `.env`/`.env.local` (or use `neon-env run -- ` to inject at runtime without a file): | Variable | Meaning | | -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | | `NEON_AI_GATEWAY_TOKEN` | Gateway bearer token (a Neon credential, `nt_live_...`) | | `NEON_AI_GATEWAY_BASE_URL` | **Bare branch gateway host** (`scheme://host`, **no path** — no `/ai-gateway`): `https://-api.ai..aws.neon.tech` | > Neon injects **only** these two vars — it does **not** set `OPENAI_API_KEY` / `OPENAI_BASE_URL`. The `@neon/ai-sdk-provider` and Mastra's `neon/` read `NEON_AI_GATEWAY_*` directly (zero config); for the plain OpenAI SDK / `@ai-sdk/openai`, build the client's `apiKey` + `baseURL` from them (shown below), or set your own `OPENAI_*` by hand (`env pull` leaves user-set vars untouched). `NEON_AI_GATEWAY_BASE_URL` is the **bare host** — you append the dialect path yourself (which is exactly what the `@neon/ai-sdk-provider` does for you). The routes under the host are: - `/v1` — unified, OpenAI **Chat Completions**-compatible; recommended default, works with every provider (`/v1/chat/completions`). - `/openai/v1` — OpenAI **Responses** API (required for `gpt-5-…-codex` variants and `gpt-5-5-pro`); the `@ai-sdk/openai` provider uses the Responses API by default (`/openai/v1/responses`). - `/anthropic` — native Anthropic Messages (extended thinking, prompt caching). Give the Anthropic SDK this as its base URL and it appends `/v1/messages` itself, so the full request path is `/anthropic/v1/messages`. - `/gemini` — native Gemini `generateContent`. Give google-genai this as its base URL and it appends `/v1beta/models/:generateContent` itself, so the full request path is `/gemini/v1beta/models/:generateContent`. So `${NEON_AI_GATEWAY_BASE_URL}/v1` is the chat-completions endpoint and `${NEON_AI_GATEWAY_BASE_URL}/openai/v1` the OpenAI Responses endpoint (both appended by you); for the native Anthropic and Gemini dialects you hand the SDK the shorter `/anthropic` or `/gemini` base and it appends the rest. See [Use with Plain SDKs](#use-with-plain-sdks-lower-level) below. For typed, validated access to the injected credentials, pass the same `neon.ts` config object to `parseEnv` from `@neon/env` — it returns an `env.aiGateway` namespace (`apiKey`, `baseUrl`) derived from your config. ## Build Agents with the Vercel AI SDK (Recommended) The [Vercel AI SDK](https://ai-sdk.dev) is the recommended way to call the gateway and build agents from TypeScript: one set of primitives (`generateText`, `streamText`, tool calling, structured output) over every catalog model, with first-class streaming for the long agent responses Neon Functions are built to host. The dedicated `@neon/ai-sdk-provider` reads `NEON_AI_GATEWAY_BASE_URL` + `NEON_AI_GATEWAY_TOKEN` from the injected env with **zero config** and routes each model to the best endpoint (Anthropic → Messages, OpenAI/Codex → Responses, everything else → MLflow). On a Neon Function that streams text and generates images, just pick a catalog model: ```typescript import { neon } from "@neon/ai-sdk-provider"; import { streamText } from "ai"; const result = streamText({ model: neon("gpt-5-mini"), // or claude-sonnet-4-6, gemini-3-flash, ... messages, tools: { image_generation: neon.tools.imageGeneration({ outputFormat: "jpeg", size: "1024x1024", }), }, }); return result.toUIMessageStreamResponse(); ``` A single completion is the same provider with `generateText`: ```typescript import { neon } from "@neon/ai-sdk-provider"; import { generateText } from "ai"; const { text } = await generateText({ model: neon("claude-haiku-4-5"), // or gpt-5-3-codex, gemini-3-flash, ... prompt: "Summarize Postgres for me.", }); ``` > Prefer `@neon/ai-sdk-provider` over the bare `@ai-sdk/openai` `openai()`: Neon injects only `NEON_AI_GATEWAY_*`, not `OPENAI_*`, so `openai()` won't pick up the gateway from the env on its own. If you do use `@ai-sdk/openai`, configure it explicitly with `createOpenAI({ apiKey: process.env.NEON_AI_GATEWAY_TOKEN, baseURL: `${process.env.NEON_AI_GATEWAY_BASE_URL}/openai/v1` })`. To build an **agent** — a model that calls tools in a loop and then answers — add `tools` and a `stopWhen` budget. The loop runs in-process, so on a Neon Function it isn't cut off by lambda-style timeouts: ```typescript import { neon } from "@neon/ai-sdk-provider"; import { generateText, tool, stepCountIs } from "ai"; import { z } from "zod"; const { text } = await generateText({ model: neon("claude-sonnet-4-6"), prompt: "How many open todos do I have, and what's the oldest one?", tools: { listTodos: tool({ description: "List the user's open todos.", inputSchema: z.object({}), // AI SDK v5+: `inputSchema`, not `parameters` execute: async () => db.select().from(todos), }), }, stopWhen: stepCountIs(5), // let the model call tools, then summarize }); ``` For a full AI SDK agent deployed as a Neon Function (streaming, tool calling, image generation, persistence), see the `neon-functions` skill's [references/ai-sdk.md](https://neon.com/docs/ai/skills/neon-functions/references/ai-sdk.md). ## Build Agents with Mastra (Recommended) [Mastra](https://mastra.ai) is the recommended framework when you want batteries-included agents — built-in memory, tools, workflows, and tracing — with the model still pointed at the gateway. With `@mastra/core` 1.47+, use a `neon/` magic string; Mastra reads `NEON_AI_GATEWAY_BASE_URL` and `NEON_AI_GATEWAY_TOKEN` from the environment (injected by `neon deploy` when `aiGateway` is enabled). Use `parseEnv` only for other declared services (e.g. `env.postgres.databaseUrl` for `@mastra/pg` memory): ```typescript import { Agent } from "@mastra/core/agent"; import { parseEnv } from "@neon/env"; import config from "../neon"; const env = parseEnv(config); export const personalAssistant = new Agent({ id: "personal-assistant", name: "personal-assistant", instructions: "You are a warm, concise personal assistant with long-term memory.", model: "neon/claude-haiku-4-5", memory, // your Mastra memory store, e.g. @mastra/pg on env.postgres.databaseUrl }); ``` ## Use with Plain SDKs (Lower-Level) When you don't need an agent framework — a single completion, an existing provider-SDK integration, or native provider features — call the gateway with the plain SDKs. Neon injects the `NEON_AI_GATEWAY_*` vars (not `OPENAI_*`), so set the client's `apiKey` + `baseURL` from them. For the OpenAI **Responses** dialect (`/openai/v1`): ```typescript import OpenAI from "openai"; const client = new OpenAI({ apiKey: process.env.NEON_AI_GATEWAY_TOKEN, baseURL: `${process.env.NEON_AI_GATEWAY_BASE_URL}/openai/v1`, }); const res = await client.responses.create({ model: "gpt-5-mini", // swap to claude-sonnet-4-6, gemini-3-flash, ... input: "What is Neon?", }); ``` For the unified **chat-completions** dialect, point `baseURL` at `/v1` instead: ```typescript const client = new OpenAI({ apiKey: process.env.NEON_AI_GATEWAY_TOKEN, baseURL: `${process.env.NEON_AI_GATEWAY_BASE_URL}/v1`, }); const res = await client.chat.completions.create({ model: "claude-sonnet-4-6", messages: [{ role: "user", content: "What is Neon?" }], }); ``` The Anthropic SDK and google-genai work the same way for native provider features — point the Anthropic SDK at `${NEON_AI_GATEWAY_BASE_URL}/anthropic` (it appends `/v1/messages` itself) and google-genai at `${NEON_AI_GATEWAY_BASE_URL}/gemini` (it appends `/v1beta/models/...`). ## Model Identifiers Use a model's catalog ID directly in the `model` field — e.g. `claude-sonnet-4-6`, `gpt-5-mini`, `gemini-3-flash`. No provider prefix is needed. To look up the exact identifiers the gateway serves, which underlying model each maps to, and their context windows, pricing, and capabilities, use any of: - **models.dev Neon provider page: https://models.dev/providers/neon** — the canonical, always-current list of the Neon provider's model IDs and their underlying models. The machine-readable catalog is at https://models.dev/api.json (the `neon` key). - **Models doc:** see Further Reading. ## List Available Models at Runtime (`/v1/models`) The gateway also exposes the model catalog **live from your own branch endpoint**, so an app or agent can discover exactly which models this branch serves without hard-coding the list. It is an OpenAI-compatible list endpoint, served **only on the unified dialect** (`/v1`): ```bash curl "$NEON_AI_GATEWAY_BASE_URL/v1/models" \ -H "Authorization: Bearer $NEON_AI_GATEWAY_TOKEN" ``` - `GET ${NEON_AI_GATEWAY_BASE_URL}/v1/models` → **200** - `GET ${NEON_AI_GATEWAY_BASE_URL}/openai/v1/models` → **404** (not served on the Responses dialect — use `/v1`) **Getting the credentials for the request.** Both values come from the same branch-scoped Neon credential the gateway uses everywhere else — you never manage a provider key: - **Provision via `neon.ts` (recommended).** Enable `aiGateway` in `neon.ts` and run `neon deploy` (or `neon config apply`). Provisioning, `neon link`, and `neon checkout` pull `NEON_AI_GATEWAY_TOKEN` + `NEON_AI_GATEWAY_BASE_URL` into your local `.env.local`; inside a deployed Neon Function they're injected automatically. See **Setup** and **Environment Variables** above. - **Pull into the environment via CLI.** `neon env pull` writes the two vars to `.env`/`.env.local`, or `neon-env run -- ` injects them at runtime without a file — but only when `neon.ts` declares `aiGateway`; the vars are never pulled off branch state alone. - **Provision via the Console UI.** Enable the AI Gateway on the branch in the Neon Console and copy the branch's gateway base URL and a Neon credential (token) from the project's connection/credentials view. Any Neon credential (`nt_live_...`) valid for the branch works as the bearer token; `NEON_AI_GATEWAY_BASE_URL` is the bare branch host (no path). **Response shape** — OpenAI/OpenRouter-compatible list: ```jsonc { "object": "list", "data": [ { "id": "claude-sonnet-4-6", // catalog model ID — use directly in the `model` field "canonical_slug": "claude-sonnet-4-6", "name": "Claude Sonnet 4.6", // human-readable display name "object": "model", "owned_by": "anthropic", // provider slug, e.g. anthropic | openai | google | meta | alibaba | databricks | ... (non-exhaustive; read live) "created": 0, "enabled": true, "context_length": null, "architecture": { "modality": "text->text", "input_modalities": ["text"], "output_modalities": ["text"], "tokenizer": "Claude", // Claude | Gemini | GPT | "" (empty for open-source) "instruct_type": null }, "top_provider": { "is_moderated": false, "context_length": null, "max_completion_tokens": null }, "pricing": null, "per_request_limits": null } // ... one entry per model in the branch's catalog ] } ``` > Note: `context_length`, `pricing`, and `per_request_limits` are currently `null` and `created` is `0` for every entry — for context windows, pricing, and capabilities use the models.dev catalog above. Use `/v1/models` when you need the live, branch-scoped list of servable model IDs (e.g. to populate a model picker or validate a `model` before a request). ## Neon Documentation The Neon documentation is the source of truth and the AI Gateway is evolving rapidly, so always verify against the official docs. Any doc page can be fetched as markdown by appending `.md` to the URL or by requesting `Accept: text/markdown`. Find the right page from the docs index (https://neon.com/docs/llms.txt) and the changelog announcements. ## Further Reading - https://neon.com/docs/ai-gateway/overview.md - https://neon.com/docs/ai-gateway/get-started.md - https://neon.com/docs/ai-gateway/models.md - https://neon.com/docs/ai-gateway/chat-completions.md - https://neon.com/docs/ai-gateway/anthropic-messages.md - https://neon.com/docs/ai-gateway/openai-responses.md - https://neon.com/docs/ai-gateway/gemini.md - https://neon.com/docs/ai-gateway/authentication.md - https://neon.com/docs/ai-gateway/troubleshooting.md --- ## 2. neon-auth - **Source:** https://github.com/neondatabase/agent-skills/blob/main/skills/neon-auth/SKILL.md - **Raw:** https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon-auth/SKILL.md - **Markdown:** https://skillsdocs.com/neondatabase/agent-skills/neon-auth.md - **Licence:** Apache-2.0 — https://spdx.org/licenses/Apache-2.0.html Bundled files (2), referenced from this skill's directory: - `references/managed-auth.md` — https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon-auth/references/managed-auth.md - `references/self-managed.md` — https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon-auth/references/self-managed.md --- name: neon-auth description: >- Add authentication to a new app. Use for "add auth", "add login", Neon Auth (Managed Better Auth), identity routing, sign-up, sign-in, password reset, email OTP, magic links, organizations, phone OTP, OAuth, passkeys, MFA, trusted domains, invalid domain, and @neondatabase/auth. No existing identity: default to Managed Better Auth. Keep working Better Auth, Clerk, Supabase Auth, or another IdP. User asked to migrate from Supabase Auth: Managed Better Auth. A required plugin outside Managed support: self-managed Better Auth on a Neon Function or the existing app host. Also use for auth APIs in @neondatabase/neon-js. metadata: parent: neon source: https://github.com/neondatabase/agent-skills/tree/main/skills/neon-auth --- **FIRST**: Use the parent `neon` skill for a Neon overview, getting started with Neon, Neon development best practices, and more. If the `neon` skill is not installed, fetch it from https://neon.com/docs/ai/skills/neon/SKILL.md or install it with: ```bash neon skills -s neon -y ``` # Neon Auth Neon Auth is Managed Better Auth: users, sessions, and auth config live in the `neon_auth` schema on the branch's Lakebase Postgres, and auth state branches with the database. The client API is the Better Auth method set (`signIn.email`, `signIn.social`, `getSession`) through `@neondatabase/auth`. That wrapper is not a drop-in for bare `better-auth/client`: it pins the plugin list and adds Neon-specific OAuth verifier, iframe popup, and JWT handling. Stay on the wrapper while Auth is managed. This skill chooses identity, then implements Managed Better Auth. It does not replace a working auth server in order to use Postgres, Functions, Object Storage, or the AI Gateway. ## When to Use Inspect existing identity and the required login features before provisioning. A supplied `DATABASE_URL` is not a reason to change identity. Adding a Neon Function is not a reason to change identity. | Situation | What to do | | --- | --- | | No existing auth | Default to Managed Better Auth. [Managed setup](#managed-setup), then [references/managed-auth.md](references/managed-auth.md). | | Needs a feature Managed does not offer | Self-managed Better Auth on the existing app host (Vercel or similar) or a Neon Function. Keep Lakebase Postgres. Confirm the **installed** Better Auth version documents that exact flow before recommending the move. If support stays unresolved, keep the current identity. [references/self-managed.md](references/self-managed.md). | | Already has Better Auth | Keep it. It works with the other Neon primitives. Migrate to Managed only if the user asks. | | User asked to migrate from Supabase Auth | Managed Better Auth. [Supabase Auth](#supabase-auth). Moving only Postgres or adding a Function keeps Supabase Auth. | | Clerk, Auth.js, Supabase Auth, or another working IdP | Keep it unless the user asks to migrate. | Google, GitHub, and Vercel social OAuth are offered on Managed Auth. They are not a reason to leave Managed Auth. Other OAuth providers, generic OAuth, MFA, passkeys, API keys, MCP OAuth, SSO, custom plugins, hooks, and custom JWT claims are the [plugin matrix](#plugin-support) check. Before enabling Managed Auth, confirm the project is on AWS and does not use IP Allow or Private Networking. Leave those protections in place. Configure supported Managed plugins through Neon (Console, API, or `neon neon-auth`), not by passing `plugins` into `@neondatabase/auth`. Enabling `auth: true` is not implementing login. ## What It Does - **Managed identity in Postgres** — users and sessions in `neon_auth`, queryable with SQL, compatible with RLS. - **Auth emails without an app mailer** — verification, email OTP, magic links, and password reset. Getting started uses shared SMTP (`auth@mail.myneon.app`). You do not add Resend or SendGrid to implement login. Production needs custom SMTP: https://neon.com/docs/auth/production-checklist.md - **Branches with the database** — each branch has its own Auth URL and isolated auth state. - **Better Auth client methods via the Neon SDK** — `@neondatabase/auth` (auth only) or `@neondatabase/neon-js/auth` (combined SDK). Optional UI: `@neondatabase/auth-ui`. - **Fixed plugin set** — the Managed client does not accept a `plugins` option. See [plugin support](#plugin-support). ## Availability Managed Better Auth is generally available. AWS regions only. It cannot be enabled on a project with IP Allow or Private Networking. Organization is separately Partial / Beta. Hosting self-managed Better Auth in a Neon Function follows Functions availability and claim rules; use the `neon-functions` skill for that host. An unclaimed project that can enable Auth still cannot use Functions until claim. ## Managed setup Merge Auth into the existing `neon.ts`. Do not replace other fields: ```typescript import { defineConfig } from "@neon/config/v1"; export default defineConfig({ auth: true, }); ``` ```bash neon deploy neon neon-auth status ``` If Function env in that config reads `process.env`, use `neon deploy --env ` as the parent skill describes. The manual service command is `neon neon-auth enable`; do not run both enable and deploy as redundant required steps when `neon.ts` already declares `auth: true`. Then implement login: [references/managed-auth.md](references/managed-auth.md). Claimable projects: follow the parent Claimable path, then `auth: true` and `neon deploy` when login is requested and no existing provider should be preserved. ## Supabase Auth When the user asked to migrate login from Supabase Auth, recommend Managed Better Auth and follow https://neon.com/docs/auth/migrate/from-supabase.md. Moving only Postgres or adding a Function is not that request: keep Supabase Auth. `SupabaseAuthAdapter()` keeps method shapes such as `signInWithPassword` and `signInWithOAuth`. Those calls are not interchangeable with default Better Auth examples (`signIn.email`). Keep an existing adapter caller on that API. Inventory the auth methods and database calls actually used: - Password hashes cannot transfer. Users create new accounts or sign in with OAuth. - Do not promise unchanged user IDs, sessions, or account linking. Plan application foreign keys with the owner. - `updateUser()` cannot change email or password on Managed Auth. Email verification needs application UI (codes work on shared SMTP; links need custom SMTP). - The migration guide lists Supabase phone/SMS/WhatsApp, SAML, and Web3 as unsupported on Managed Auth. Confirm the **installed** Better Auth version if the user still needs that exact flow; if support stays unresolved, keep Supabase Auth and stop the auth cutover. That page's "no phone auth" claim is about Supabase phone sign-in, not the constrained Managed Phone Number plugin (existing users link a number). - `@supabase/supabase-js` used only for Auth does not justify enabling the Data API. Keep Data API only for existing PostgREST / Supabase database-client queries. ## Verification Managed path: sign-up, sign-in, sign-out, session restoration after reload, and protected access, including error and loading states. Exercise email verification (code on shared SMTP) when it is on. Report any flow that remains unverified. A required plugin on the self-managed path is verified in that app's Better Auth setup, not as a Managed flow. ## Plugin support Checked 2026-09-17 against https://neon.com/docs/auth/guides/plugins.md, https://neon.com/docs/auth/roadmap.md, and the `@neondatabase/auth` client plugin list. Re-fetch those pages if this skill may be stale. An unlisted upstream plugin needs a live check; do not treat absence from this table as a dated roadmap item. "Not exposed" means the Managed SDK/UI contract. It is not a claim that every raw server request was tested. | Feature | Managed Auth | Boundary | | --- | --- | --- | | Email/password | Supported | `signUp.email`, `signIn.email` | | Social OAuth (Google, GitHub, Vercel) | Supported | `signIn.social`. Shared Google credentials are for development; production and GitHub/Vercel need your own OAuth apps. https://neon.com/docs/auth/guides/setup-oauth.md | | Admin | Supported | Admin session required. Plugin customization is on the roadmap. | | Email OTP | Supported | Managed delivery. `emailOtp.sendVerificationOtp`, `signIn.emailOtp`. | | Magic Link | Supported | Enable on the branch (off by default). `signIn.magicLink`. | | Organization | Partial, Beta | Members, invitations, owner/admin/member. No Teams, server hooks, custom roles/permissions, or dynamic access control. Emailed invitations: [managed-auth.md](references/managed-auth.md#organization-invitations). | | JWT | Supported | EdDSA (Ed25519), 15-minute expiry, no custom claims. Default client: `.token()` then `data.token`. `SupabaseAuthAdapter()`: `getSession()` then `data.session.access_token` (no `.token()`). | | Open API | Supported | Server routes `/reference` and `/open-api/generate-schema`. | | Phone Number | Supported with constraints | Browser client: existing users link a number, then sign in; no phone-first signup; own SMS webhook; custom UI. Next.js `auth.handler()` forwards the catch-all path, including phone OTP. A missing `auth.phoneNumber` server method is a missing typed helper, not a proxy rejection. https://neon.com/docs/auth/guides/plugins/phone-number.md | | MFA / Two-Factor | Roadmap | Unavailable on Managed Auth. If required: [self-managed.md](references/self-managed.md), after confirming the installed Better Auth version. | | Passkey, API Key, Generic OAuth, One Tap, Multi Session | Not exposed by Managed SDK/UI | If required: [self-managed.md](references/self-managed.md). Generic OAuth is not Google/GitHub/Vercel social sign-in. | | MCP / OAuth Provider | Not Managed Auth | Third-party MCP clients self-authorizing against your server. Keep existing login. See `neon-functions` [references/mcp.md](https://neon.com/docs/ai/skills/neon-functions/references/mcp.md). | | SSO / SAML | Not listed or exposed | If required: [self-managed.md](references/self-managed.md), after confirming the installed Better Auth version. | The default Managed client method is `getAnonymousToken()`. That JWT is a Neon anonymous Data API token. It is not Better Auth's Anonymous-account plugin (`signIn.anonymous`). `anonymousTokenClient()` is the SDK plugin factory, not a method on the public client. Do not call it, and do not call `getAnonymousToken()` on `SupabaseAuthAdapter()`. Trusted domains and webhooks are Neon settings, not installable Better Auth plugins. ## Trusted domains Auth redirects only to origins on its allowlist. `invalid domain` means the app origin is missing. Include the scheme, omit a trailing slash, register production and preview origins before pointing users at them, and target the correct branch: ```bash neon neon-auth domain add https://app.example.com neon neon-auth domain list neon neon-auth domain delete https://old.example.com ``` Localhost ports are pre-approved by default. An existing project can have that off: `neon neon-auth domain allow-localhost get|enable|disable`. Docs: https://neon.com/docs/auth/guides/configure-domains.md OAuth provider redirect is `{NEON_AUTH_BASE_URL}/callback/{provider}` (the Auth URL includes its path). `callbackURL` on `signIn.social` is the later app landing origin and must be trusted. The Managed SDK handles iframe OAuth popup and `neon_auth_session_verifier`. Keep the wrapper, callback route, and middleware. Do not reimplement that flow, and do not promise third-party cookies in every browser. ## Functions and Data API A Function authenticates whoever already signs the user in. Do not switch identity to call a Function. Verify the token in the `neon-functions` skill and https://neon.com/docs/compute/functions/authentication.md. Managed Auth: injected `NEON_AUTH_JWKS_URL`, issuer from `NEON_AUTH_BASE_URL`. Token: default client `.token()` then `data.token`; `SupabaseAuthAdapter()` `getSession()` then `data.session.access_token`. A valid token is not permission to read another user's rows. Sign-out ends the browser session; do not claim it immediately revokes an already-issued JWT. Data API identity: [references/managed-auth.md](references/managed-auth.md). New apps query Postgres from Functions or existing handlers, not the Data API. --- ## 3. neon-functions - **Source:** https://github.com/neondatabase/agent-skills/blob/main/skills/neon-functions/SKILL.md - **Raw:** https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon-functions/SKILL.md - **Markdown:** https://skillsdocs.com/neondatabase/agent-skills/neon-functions.md - **Licence:** Apache-2.0 — https://spdx.org/licenses/Apache-2.0.html Bundled files (7), referenced from this skill's directory: - `references/ai-sdk.md` — https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon-functions/references/ai-sdk.md - `references/function-triggers.md` — https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon-functions/references/function-triggers.md - `references/mastra-studio.md` — https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon-functions/references/mastra-studio.md - `references/mcp.md` — https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon-functions/references/mcp.md - `references/production-hardening.md` — https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon-functions/references/production-hardening.md - `references/sentry.md` — https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon-functions/references/sentry.md - `references/sse.md` — https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon-functions/references/sse.md --- name: neon-functions description: >- Long-running, serverless Node.js HTTP functions deployed onto your Neon branch, with DATABASE_URL injected automatically and compute that runs next to your data. Use when a user wants to host an API, an AI agent with long streaming responses, a WebSocket or server-sent-events (SSE) server, a webhook handler, a Discord bot, an MCP server, or any request/response workload that risks timing out on short, lambda-style serverless functions — and wants it to branch with their database. Also use for Function Triggers: a cron or an object-storage event that POSTs to a function. Triggers include "serverless function", "deploy an API", "long-running function", "streaming agent", "SSE server", "WebSocket server", "webhook handler", "MCP server", "cron", "function trigger", "scheduled function", "cron job", "object storage trigger", "on upload", "run code next to my database", "function that won't time out", "function logs", "Neon Functions", "Neon Compute", "DDoS protection", "rate limiting", and "production hardening". metadata: parent: neon source: https://github.com/neondatabase/agent-skills/tree/main/skills/neon-functions --- **FIRST**: Use the parent `neon` skill for a Neon overview, getting started with Neon, Neon development best practices, and more. If the `neon` skill is not installed, fetch it from https://neon.com/docs/ai/skills/neon/SKILL.md or install it with: ```bash neon skills -s neon -y ``` # Neon Functions Currently available in `aws-us-east-2`, `aws-us-east-1`, `aws-eu-central-1`, and `aws-ap-southeast-1`. Neon Functions are long-running Node.js HTTP handlers deployed onto a Neon branch. Each function gets a public HTTPS URL, runs in the same region as your database, and — if the branch has Postgres — gets `DATABASE_URL` injected automatically. You deploy and manage them through the same Neon CLI, `neon.ts`, and API you already use. Use this skill to help the user define, run locally, deploy, and manage functions next to their database. Deliver a deployed function with its invocation URL, a working local `neon dev` loop, or a precise answer from the official Neon docs. ## When to Use Reach for Neon Functions when the workload is a request/response handler that benefits from staying alive and staying close to the data: - **Long-running request/response flows that outlast lambda-style limits.** Agents that make several LLM calls and tool invocations per request, or image/video generation, routinely blow past the ~10–60s execution caps and short streaming windows of traditional serverless functions. Neon Functions are long-running: the handler just needs to _start_ responding within 15 minutes, and an open stream stays alive as long as bytes keep flowing. That's enough headroom for real agent workloads. - **Stateful streaming without bolting on Redis.** Because a function stays alive across a request, it can host an SSE endpoint or a WebSocket server and hold the connection open in-process — no external state store (Redis, etc.) needed just to keep a stream coherent. Module-scope state (a `pg` pool, an in-memory counter) persists across requests on the same isolate. - **Compute that must sit next to Postgres.** The function runs in the same region as the branch's database, so there are no cross-region round trips on every query. `DATABASE_URL` is injected for you. - **A backend that branches with your data.** Each branch runs its own version of the function at its own URL, against its own isolated database (and storage, and gateway) state. Preview deployments, CI, and dev environments each get a self-contained backend — deploying to a child never affects the parent. - **Query Postgres from the Function (or an existing framework handler).** Prefer that over the Data API. Use the Data API when the application already uses PostgREST or Supabase-js database calls, or is migrating that client. - **Webhooks, bots, and post-response work.** Webhook handlers that fan out into multiple DB writes, Discord/WebSocket bots, and fire-and-forget follow-ups via `waitUntil` (analytics, audit logs) all fit. - **Recurring HTTP work.** A Function Trigger POSTs to the function on a cron (`type: "schedule"`) or when an object is created in Object Storage (`type: "storage_object_created"`). Same `fetch` handler, same 15-minute time-to-first-byte limit. See [Function Triggers](#function-triggers). If the workload is a pure static site, or something that must run outside the supported regions (`aws-us-east-2`, `aws-us-east-1`, `aws-eu-central-1`, and `aws-ap-southeast-1`) today, this isn't the right tool yet (see [Timeouts and Runtime Limits](#timeouts-and-runtime-limits) and [Availability](#availability)). ## What It Does - **Long-running & serverless** — Built for WebSocket servers (see [WebSocket Servers](#websocket-servers)), SSE endpoints (see [Server-Sent Events (SSE)](#server-sent-events-sse)), long agent HTTP streams, and APIs. Still scales to zero when idle. - **Web-standard handler** — A function is any default export with a `fetch(request)` method returning a `Response` (Workers/WinterTC-compatible). A Hono app exports exactly that shape, so `export default app` just works. Runs on Node.js 24, so all Node APIs are available. - **Close to your database** — Runs in the branch's region; `DATABASE_URL` injected automatically when the branch has Postgres. - **Branchable** — Each branch runs its own function version at its own URL against its own isolated state. - **Same CLI/API** — Deploy and manage via `neon`, `neon.ts`, or the Neon API. - **Function Triggers** — Neon POSTs to the function on a cron or an object-storage upload. See [Function Triggers](#function-triggers). ## Availability Check this precondition before setting anything up: Neon Functions is currently available in `aws-us-east-2`, `aws-us-east-1`, `aws-eu-central-1`, and `aws-ap-southeast-1`. Confirm the user's Neon project is in one of these regions. ## Architecture: Where Functions Fit Neon (Functions included) is **backend primitives, not full-stack app hosting**. Host your app on **Vercel** (or Netlify, or another frontend/app host); Functions are the long-running, stateful slice of your backend that lives next to your data. They compose with that platform in two ways: - **Add a Function to a full-stack app.** Your Next.js / TanStack Start app on Vercel (or Netlify) owns UI, auth (Managed Auth, Better Auth, Clerk, or another IdP), and talks directly to Lakebase Postgres and Object Storage. Add a Function as a Hono API layer for the web app and other clients, or for one job next to the data: Object Storage uploads, AI agents, Discord bots, WebSocket or SSE servers. (See [Functions as an Agent Backend](#functions-as-an-agent-backend-nextjs-and-similar-frameworks) for the client-direct pattern.) - **Run the whole backend control plane on Functions.** Especially when the frontend is **client-only** — TanStack Router, React Router in client mode, and similar SPAs hosted on Vercel or Netlify — the client calls Functions **directly**. Build REST APIs and request/response agents, host **MCP servers**, and run anything stateful or that belongs close to Postgres and Object Storage. Either way, authenticate by caller: JWT or API key for app and public HTTP (see the WARNING under [Functions as an Agent Backend](#functions-as-an-agent-backend-nextjs-and-similar-frameworks)); `parseTriggerDelivery` for Function Trigger routes; production hardening in [Production hardening](references/production-hardening.md). Because a Function is just your backend, you can **move pieces between your host and Neon** — relocate an agent or a stateful WebSocket server onto a Function when it needs more runtime, and back if needed. Prefer a Function, or an existing framework handler, that queries Postgres. Use Data API when the application already uses PostgREST/Supabase-js database calls or is migrating that client. ## Production hardening Before exposing production routes, read [Production hardening](references/production-hardening.md). Pick by caller: trusted app server, Function Trigger, or public consumer. Keep long browser streams on the client-direct JWT path unless a verified streaming-compatible proxy is required. Authentication rejects application work; requests to the native URL still reach the Function. ## Setup Functions are declared in `neon.ts` (see the `neon` skill for the branch-first workflow and `neon.ts` basics). Add `@neon/config` and declare functions under `functions`, keyed by **slug**: ```typescript // neon.ts import { defineConfig } from "@neon/config/v1"; export default defineConfig({ functions: { todos: { // slug: ^[a-z0-9]{1,20}$ — lowercase letters/digits, no hyphens name: "todo api", // display label only source: "src/index.ts", // entry file, relative to neon.ts }, }, }); ``` The slug is the function's permanent identity (it appears in the invocation URL and CLI commands) and can't be changed after the first deploy. Use `name` for a human-readable label. A minimal function — a Hono app that queries the branch's Postgres via the injected `DATABASE_URL`: ```typescript // src/index.ts import { Hono } from "hono"; import { drizzle } from "drizzle-orm/node-postgres"; import { Pool } from "pg"; import { parseEnv } from "@neon/env"; import { attachDatabasePool } from "@neon/functions"; import config from "../neon"; import { todos } from "./db/schema"; const env = parseEnv(config); const pool = new Pool({ connectionString: env.postgres.databaseUrl, max: 5 }); attachDatabasePool(pool); const db = drizzle(pool); const app = new Hono(); app.get("/", (c) => c.text("Neon + Hono + Drizzle")); app.post("/todos", async (c) => { const { text } = await c.req.json<{ text: string }>(); const [row] = await db.insert(todos).values({ text }).returning(); return c.json(row, 201); }); app.get("/todos", async (c) => c.json(await db.select().from(todos))); export default app; ``` Create the `pg` pool at module scope (reused across requests on the same isolate) and keep `max` small (e.g. 5), since each isolate keeps its own pool. Call `attachDatabasePool(pool)` so an idle disconnect is not an `uncaughtException` — see [Connecting to Postgres](#connecting-to-postgres). `parseEnv(config)` requires _every_ variable the config implies. A function that only talks to Postgres over the pooled URL can scope it to just that key — `parseEnv` then validates and returns only what you asked for (the keys autocomplete from your `neon.ts`): ```typescript const { postgres } = parseEnv(config, ["DATABASE_URL"]); // not the unpooled URL, auth, etc. const pool = new Pool({ connectionString: postgres.databaseUrl, max: 5 }); attachDatabasePool(pool); ``` ## Develop Locally and Deploy ```bash neon dev # serves every function in neon.ts with hot reload; injects DATABASE_URL & friends neon deploy --env # preferred full deploy from neon.ts; --env is the file Function env is read from ``` Keep `.env` or `.env.local` up to date with every key under `functions.*.env`. `neon env pull` writes Neon-managed vars only; add Function secrets to that file, then pass it as `--env`. `neon deploy --env ` loads that file into `process.env` each time, then uploads those values. A missing value is `undefined` and `defineConfig` throws. Omit the key from `neon.ts` if you do not want to write it. Never coerce a missing `process.env` value to an empty string (that uploads `""` and deletes the live key). An empty assignment (`KEY=`) is also `""`. Use `process.env.X!` when TypeScript needs an assertion. To deploy a single function without applying `neon.ts`: `neon functions deploy --src src/index.ts` (`--src` takes either the entry file or a directory containing `index.ts`, `index.mjs`, or `index.js`). That command's `--env` is `KEY=VALUE` (repeatable), not a file path. Use it for a targeted env update. Retrieve the public URL with `neon functions get ` (the `invocation_url` field, of the form `https://-.compute..us-east-2.aws.neon.tech`). Manage with `neon functions list|get|delete`. When `neon checkout` _creates_ a new branch and a `neon.ts` is present, it applies the policy automatically. Pass `--env ` on that create so Function env that reads `process.env` resolves (`neon checkout feat --create --env .env.local`). Existing process env wins over the file. Checking out an existing branch never reconciles it — apply config changes with `neon deploy --env ` (add `--update-existing` only after reviewing those changes). ## Neon Infrastructure as Code (`neon.ts`) The `functions` block from [Setup](#setup) is part of `neon.ts`, Neon's infrastructure-as-code file — one TypeScript file declares every function (its `source`, display `name`, and `env`) alongside any other branch services, in version control (see the `neon` skill for the full reference). Treat it like Terraform for your branch: ```bash neon config status # print the branch's live config (deployed functions) neon config plan # dry-run diff of what apply would change neon config apply --env # bundle + deploy the declared functions (neon deploy is an alias; pass --env when Function env reads process.env) ``` Functions are **branch-scoped**: each branch runs its own deployment at its own URL. When a `neon.ts` is present, `neon checkout` applies the policy as it _creates_ a branch. Pass `--env ` on that create when Function env reads `process.env`. Checking out an _existing_ branch doesn't redeploy — run `neon deploy --env ` to apply changes. Per-branch deploy tuning (e.g. `runtime`) lives in the `branch` closure, keyed by slug, so it can vary by branch without changing which functions exist: ```typescript export default defineConfig({ functions: { todos: { name: "todo api", source: "src/index.ts" } }, branch: (branch) => ({ functions: { todos: { runtime: "nodejs24" } }, }), }); ``` ## Environment Variables Neon injects branch-scoped connection strings and service URLs at runtime — you don't declare these or pass them at deploy time: | Variable | Notes | | ----------------------- | -------------------------------------------------------------------------------------------------- | | `NEON_BRANCH` | The branch **name** (e.g. `main`, `preview/foo`). Injected on every branch, including the default. | | `DATABASE_URL` | Pooled connection string. Use for most queries. Present only if the branch has Postgres. | | `DATABASE_URL_UNPOOLED` | Direct connection. Use for migrations, `LISTEN`/`NOTIFY`, multi-round-trip transactions. | | `NEON_AUTH_BASE_URL` | Present when Neon Auth is enabled on the branch. | | `NEON_AUTH_JWKS_URL` | Present when Neon Auth is enabled on the branch. JWKS for verifying Managed Auth JWTs. | | `NEON_DATA_API_URL` | Present when the Data API is enabled on the branch. | Object storage (`AWS_*`) and AI Gateway (`NEON_AI_GATEWAY_*`) vars are also injected when those services are declared — see the `neon-object-storage` and `neon-ai-gateway` skills. `neon env pull` / `neon-env run` / `neon dev` emit `NEON_BRANCH` (and the connection strings) into your local dev environment too, so local runs mirror the deployed runtime. **Your own secrets** are per-deployment. Preferred path: declare them in `neon.ts` and run `neon deploy --env `. `` is the gitignored file env pull already writes (`.env` if that file exists, otherwise `.env.local`). Env pull writes Neon-managed vars only; add Function secrets to that file. All declared Function env keys must be present. Omit a key from `neon.ts` if you do not want to write it. `undefined` means you asked to write the key and the value is missing (`defineConfig` throws). Never coerce a missing `process.env` value to an empty string: that uploads `""` and deletes the live key. An empty assignment in the file (`KEY=`) is also `""`. If TypeScript needs an assertion, use `process.env.X!` and make sure the file has the value: ```typescript functions: { todos: { name: "todo api", source: "src/index.ts", env: { RESEND_API_KEY: process.env.RESEND_API_KEY! }, }, } ``` `neon functions deploy --env KEY=VALUE` is the manual path (repeatable; `--env KEY=` deletes a key; unmentioned keys carry over). Use it for a targeted env update, not a full `neon.ts` apply. Load Function secrets into the same file env pull wrote, then `neon deploy --env `. Pull the branch's Neon-managed vars onto disk for local dev with `neon env pull` (`link`/`checkout` do this automatically; pass `--no-env-pull` to skip and use `neon-env run -- ` for runtime injection). Limits: ≤1,000 vars, ≤64 KiB total, and the `NEON_` prefix is reserved. ## Connecting to Postgres When the branch has Postgres, Neon **injects the connection strings at runtime** — you don't declare them, pass them at deploy time, or hardcode anything. The two you'll use: - `DATABASE_URL` — **pooled** connection string (routed through Neon's connection pooler). Use it for normal request/response query traffic. Kept un-prefixed because every Postgres ORM (Drizzle, Prisma, Knex, …) reads `DATABASE_URL` by default. - `DATABASE_URL_UNPOOLED` — **direct** connection string to the same database. Use it for migrations, `LISTEN`/`NOTIFY`, and long multi-statement transactions. **Use Drizzle (or another ORM) on top of node-postgres (`pg`)** for queries and schema management — not Neon's serverless driver. Functions are long-running and reuse an isolate across many requests, so a persistent `pg` pool is the right fit; the serverless driver's HTTP transport is meant for fully isolated, lambda-style runtimes. Create the connection pool **once at module scope** and reuse it across requests — don't open a connection per request: ```typescript import { attachDatabasePool } from "@neon/functions"; import { drizzle } from "drizzle-orm/node-postgres"; import { Pool } from "pg"; const pool = new Pool({ connectionString: process.env.DATABASE_URL, max: 5 }); attachDatabasePool(pool); const db = drizzle(pool); ``` node-postgres emits idle-client failures as `error` on the pool. With no listener that is an `uncaughtException` and Node exits the isolate. Call `attachDatabasePool(pool)` once after `new Pool`. Requires `@neon/functions` ≥ 0.8.0. Expected idle disconnects (`ECONNRESET`, `EPIPE`, `ETIMEDOUT`, Postgres `57P01`, node-postgres's `Connection terminated unexpectedly`) are silent. Anything else is `console.error`, or `onUnexpectedError` if you pass it on the first call. The first call wins; a later call that passes `onUnexpectedError` is ignored and warns. This does not close the pool. **Pooling is recommended because an isolate is reused across many requests** (and several requests can be in flight on the same isolate at once — see [Timeouts and Runtime Limits](#timeouts-and-runtime-limits)). A module-scope pool is opened once on cold start and then shared by every subsequent request that isolate serves, so you amortize connection setup instead of paying it on every request and you avoid exhausting Postgres connections under load. Keep `max` small (e.g. `5`): each isolate keeps its own pool, so total connections to Postgres scale with the number of live isolates. You don't need to close the pool on shutdown — when the runtime evicts an isolate it sends `SIGINT`/`SIGTERM`, and Neon's pooler reclaims those connections for you, so an explicit drain handler is redundant. > Reading `process.env.DATABASE_URL` directly works everywhere. The function in [Setup](#setup) instead uses `@neon/env`'s `parseEnv(config)` to read the same value in a typed, validated way — either is fine. ## Timeouts and Runtime Limits Functions are long-running but **still serverless** — they are a request/response runtime, not a background job runner. The hard limits: - **Time to first byte: 15 minutes.** Your handler must _begin_ returning a response within 15 minutes of receiving a request. Most handlers finish in seconds; the 15-minute ceiling exists so agent workloads like image/video generation have room. - **Heartbeat: 15 minutes.** Open WebSocket/SSE connections stay alive as long as data flows. The timeout only fires when a connection goes silent — send at least one byte every 15 minutes to keep a quiet stream alive. - **`waitUntil`: 15 minutes.** Work registered with `waitUntil` (from `@neon/functions`) keeps the invocation alive after the response is sent, up to 15 minutes — for cleanup like analytics writes and audit logs, **not** a background job runner. Off the Neon runtime (local `neon dev`, tests) it's a no-op: the promise still runs but isn't tracked. - **Idle eviction.** With no active connections Neon shuts the function down; it may also evict/restart for operational reasons — e.g. maintenance, or moving the function to a different compute node (active functions can run for hours first). Treat eviction like a process restart — WebSocket/SSE clients must reconnect. Neon sends `SIGINT` before evicting, so a `process.on("SIGINT", ...)` handler lets you detect that the function is about to be evicted and run any last-minute cleanup. You don't need one just to close Postgres connections — Neon's pooler reclaims those on its own. - **Runtime:** Node.js 24, memory fixed at 2048 MiB. Slugs must match `^[a-z0-9]{1,20}$`. **An isolate is reused across many requests** — multiple requests can be in flight on the same isolate at once (interleaved on Node's single-threaded event loop), and under load the runtime runs several isolates in parallel, each with its own copy of module state. State held in module scope is therefore per-isolate (shared by every request that isolate handles) and in-memory only — persist anything that must survive eviction in Postgres. This reuse is exactly why you create a connection pool once at module scope rather than per request (see [Connecting to Postgres](#connecting-to-postgres)). ## Functions as an Agent Backend (Next.js and Similar Frameworks) A Neon Function is a great home for an AI agent precisely because it **doesn't time out** the way lambda-style serverless does (15-minute budget, see [Timeouts and Runtime Limits](#timeouts-and-runtime-limits)). Proxying that stream through a Next.js route handler, Remix/SvelteKit/Nuxt action, or similar hosted on Vercel, Netlify, and the like **cuts the stream when it exceeds that host's configured duration or transport limits**, even though the Function would keep going. Keep the client-direct JWT path below as the default. A streaming-compatible proxy (HTTP-triggered Cloudflare Worker, after you verify the stream) is the public-consumer exception in [Production hardening](references/production-hardening.md). **Building the agent itself.** The [Vercel AI SDK](https://ai-sdk.dev) and [Mastra](https://mastra.ai) are the recommended ways to build the agent — point either at the Neon AI Gateway (see the `neon-ai-gateway` skill) for one credential across every model, with no extra provider keys. For a complete AI SDK agent running as a Function (streaming `toUIMessageStreamResponse`, multi-step tool calling next to Postgres, and persisting generated images to Object Storage), see [references/ai-sdk.md](https://neon.com/docs/ai/skills/neon-functions/references/ai-sdk.md); for the Mastra equivalent with built-in tracing, see [references/mastra-studio.md](https://neon.com/docs/ai/skills/neon-functions/references/mastra-studio.md). **The fix: call the function directly from the client.** Don't route the long request through your app server. ``` Browser ──(Authorization: Bearer )──▶ Neon Function (agent) ✅ no host timeout Browser ──▶ your app backend ──▶ Neon Function ❌ host cuts the stream ``` - Get a **short-lived bearer token** from the identity the app already uses. Do not switch Clerk, Better Auth, Auth.js, Supabase Auth, or Managed Auth in order to call a Function. - Managed Auth, default client (`createAuthClient` / Next wrapper): `authClient.token()`, then `data.token`. Verify with injected `NEON_AUTH_JWKS_URL` and issuer `new URL(process.env.NEON_AUTH_BASE_URL!).origin`. - Managed Auth with `SupabaseAuthAdapter()`: that client has no `.token()`. Use `getSession()`, then `data.session.access_token`. Same JWKS/issuer as above. - Existing Better Auth / Auth.js / other signer that already publishes JWKS: use that JWKS URL, issuer, and audience. Inspect the installed contract; cookie or database sessions are not a JWKS. - Cookie/database sessions only: mint a short token on the existing app backend (that call is fast and stays within host limits), then the browser calls the Function **directly** with `Authorization: Bearer`. The Function stream must not go through the app host. - Hand the token to the client, e.g. with the Vercel AI SDK: `new DefaultChatTransport({ api: NEON_FUNCTION_URL, fetch })` where `fetch` attaches `Authorization: Bearer `. Your app server is never in the path of the long stream. - Add **CORS** so the browser can reach it (handle `OPTIONS`, set `Access-Control-Allow-Origin`/`-Headers`). > [!WARNING] > A Neon Function has a **public HTTPS URL — it is reachable by anyone.** A direct client→function call means there is no app backend in front of it to gate access, so **you must authenticate the function yourself.** Verify a JWT against the caller's JWKS, check a shared secret / API key, or reject the request. Never deploy an unauthenticated agent. Browser callers use short-lived user tokens. Server or proxy origin secrets (`X-Secret`) stay server-side; see [Production hardening](references/production-hardening.md). ```typescript // src/index.ts — verify the caller before doing any work import { createRemoteJWKSet, jwtVerify } from "jose"; const jwks = createRemoteJWKSet(new URL(process.env.NEON_AUTH_JWKS_URL!)); const issuer = new URL(process.env.NEON_AUTH_BASE_URL!).origin; export default { async fetch(request: Request) { if (request.method === "OPTIONS") return new Response(null, { status: 204, headers: cors(request) }); const auth = request.headers.get("authorization"); if (!auth?.toLowerCase().startsWith("bearer ")) { return new Response("Unauthorized", { status: 401, headers: cors(request), }); } let userId: string; try { const { payload } = await jwtVerify(auth.slice(7), jwks, { issuer }); if (!payload.sub) { return new Response("Unauthorized", { status: 401, headers: cors(request), }); } userId = payload.sub; } catch { return new Response("Unauthorized", { status: 401, headers: cors(request), }); } // Authorize resource access by userId, then run the agent scoped to that user. // ... return result.toUIMessageStreamResponse({ headers: cors(request) }) }, }; ``` That snippet is Managed Auth verification. Mint the bearer token with `.token()` (`data.token`) on the default client, or `getSession()` then `data.session.access_token` on `SupabaseAuthAdapter()`. For another identity, pass that app's JWKS URL and issuer through Function `env` (see [Environment Variables](#environment-variables)) and include `audience` only when that token contract requires it. https://neon.com/docs/compute/functions/authentication.md A valid token is not permission to read another user's rows. Exercise two users: each can access their own data; cross-user access is denied. Repeat after restarting the Function against stored rows. A request-supplied owner id cannot grant access. Persist anything you need to keep (generated images, history) in Postgres — module state doesn't survive eviction. ## WebSocket Servers A WebSocket server is the canonical Functions workload: a long-running handler holds connections open in-process, with no external state store needed to keep a stream coherent. The connection stays alive as long as bytes flow (15-minute heartbeat, see [Timeouts](#timeouts-and-runtime-limits)). **Upgrade from inside `fetch`.** Call `upgradeWebSocket(request)` from [`@neon/functions`](https://www.npmjs.com/package/@neon/functions) and return the response it gives you. Hono apps use the same primitive via `@neon/functions/hono` (see [Hono](#hono) below). There is one entrypoint and no WebSocket dependency to install: ```typescript import { upgradeWebSocket } from "@neon/functions"; export default { async fetch(req: Request): Promise { if (req.headers.get("upgrade")?.toLowerCase() !== "websocket") { return new Response("expected a websocket upgrade", { status: 426 }); } const { socket, response } = upgradeWebSocket(req); socket.addEventListener("message", (event) => socket.send(event.data)); return response; }, }; ``` `socket` is a standard [`WebSocket`](https://developer.mozilla.org/en-US/docs/Web/API/WebSocket), so `addEventListener` and the `onopen`/`onmessage`/`onclose`/`onerror` properties both work. It is still `CONNECTING` when you get it — the runtime writes the `101` only once your handler returns `response`, and the socket opens then. Three rules that matter: - **Return `response` unchanged.** A `101` can't be built as a plain `Response` (the fetch spec caps constructed responses at 200–599), so the runtime hands back an object carrying the pending upgrade. `clone()`, or rebuilding it with `new Response(res.body, res)` as response-rewriting middleware does, discards the upgrade and fails the request. - **Refuse a handshake by returning an ordinary `Response`.** Return a `401`, `403`, or `404` from `fetch`, before you upgrade, to gate a socket. A browser client can't read why a handshake was refused; it sees only a generic connection failure, not your status or body. Refuse to keep clients out, but send any detail the client needs over a separate authenticated request. - **`binaryType` defaults to `"arraybuffer"`**, not the browser's `"blob"`. `event.data` is a `string` for text frames and an `ArrayBuffer` for binary ones, so branch on `typeof`. **With auth.** Browsers can't set headers on a WebSocket, so authenticate with a `?token=` query param (verify it the same way as the [agent backend](#functions-as-an-agent-backend-nextjs-and-similar-frameworks): `jwtVerify` against your JWKS) and refuse before upgrading: ```typescript // src/index.ts import { upgradeWebSocket } from "@neon/functions"; const clients = new Set(); export default { async fetch(request: Request): Promise { if (request.headers.get("upgrade")?.toLowerCase() !== "websocket") { return new Response("WebSocket endpoint — connect with ?token="); } const url = new URL(request.url); const identity = await verifyToken(url.searchParams.get("token")); if (!identity) return new Response("unauthorized", { status: 401 }); const { socket, response } = upgradeWebSocket(request); clients.add(socket); socket.addEventListener("close", () => clients.delete(socket)); socket.addEventListener("message", (event) => { if (typeof event.data !== "string") return; persist(identity.id, event.data); // fan out to every isolate — see below }); return response; }, }; ``` **Subprotocols.** Pass `{ protocol }` to select one the client offered; it is echoed in `Sec-WebSocket-Protocol` and exposed as `socket.protocol`. Selecting one the client did not offer throws a `TypeError`. Omit it and no protocol is negotiated. No extensions are negotiated either — `socket.extensions` is always `""` and `permessage-deflate` is not available. **Hono.** Use `upgradeWebSocket` from `@neon/functions/hono` — the same primitive as Hono's own WebSocket helper, with no `ws` dependency and not the deprecated `@hono/node-ws`. Auth is ordinary middleware; gate upgrade requests before `next()`: ```typescript // src/index.ts import { Hono } from "hono"; import { upgradeWebSocket } from "@neon/functions/hono"; const clients = new Set(); const app = new Hono<{ Variables: { userId: string } }>(); app.use("/ws", async (c, next) => { const identity = await verifyToken(c.req.query("token")); if (!identity) return c.text("Unauthorized", 401); c.set("userId", identity.id); await next(); }); app.get( "/ws", upgradeWebSocket((c) => ({ onOpen(_event, ws) { clients.add(ws.raw); ws.send("welcome"); }, onClose(_event, ws) { clients.delete(ws.raw); }, onMessage(event, ws) { ws.send(`echo: ${event.data}`); }, })), ); export default app; ``` Connect from the browser with the function's `wss://` URL (from `neon functions get `), for example `new WebSocket("wss://-.compute..aws.neon.tech/ws?token=")`. Reconnect on close — isolates are evictable and idle connections may be terminated after 15 minutes. Do not put `cors()` on the upgrade route, and do not read `c.res` before `await next()` or call `c.header()` after it — both rebuild the `101` and break the upgrade. See `@neon/functions` README for the full middleware table. ### Heartbeat (keep the socket alive) A connection stays open **only while bytes flow**: Neon evicts a silent stream after 15 minutes ([Timeouts and Runtime Limits](#timeouts-and-runtime-limits)), and intermediary proxies / load balancers are usually far stricter (often tens of seconds). Don't rely on the app being chatty enough — send a periodic keepalive from the server so the socket never goes quiet. The standard `WebSocket` interface has no `ping()`, so send an application-level message the client filters out: ```typescript const HEARTBEAT_MS = 25_000; // comfortably under proxy idle timeouts const beat = setInterval(() => { for (const socket of clients) { if (socket.readyState === socket.OPEN) socket.send('{"type":"ping"}'); } }, HEARTBEAT_MS); beat.unref?.(); ``` The client skips these when handling messages. There is no protocol-level shortcut here: the standard `WebSocket` from `upgradeWebSocket` has no `ping()`, and a browser can't send ping frames from JavaScript, so an application-level message is the only keepalive a browser client can use. (A Node `ws` client can send ping frames, and the server auto-replies with a pong, but a browser can't.) ### Keeping clients in sync across isolates (do not skip this) Under load the runtime runs **several isolates in parallel, each with its own copy of module state** — so each isolate has its own `clients` set. Broadcasting only to that local set means a client on isolate A never sees an event produced on isolate B, and the feed silently fractures. It's easy to miss: `neon dev` runs a single process (one isolate), so in-process broadcast always _looks_ fine locally but breaks in production, where concurrent connections spread across many isolates. Module state doesn't survive eviction anyway, so **Postgres is the shared source of truth**. Pick a fan-out strategy. In every snippet below, `pool` is a pooled `pg` client and `clients` is this isolate's `Set` of live connections. **1. Poll Postgres — the default, and the only option that keeps Scale to Zero.** Each isolate re-reads the shared state (or rows past a cursor) on a short interval and pushes changes to its own clients. One query per isolate per tick (not per client), and none when the isolate has no clients — so an idle compute still suspends. ```typescript let lastId = "0"; // bigint id, so a string let polling = false; async function poll() { if (polling || clients.size === 0) return; // guard overlap; no clients → no query → compute can scale to zero polling = true; try { const { rows } = await pool.query( "SELECT id, payload FROM events WHERE id > $1 ORDER BY id", [lastId], ); for (const { id, payload } of rows) { lastId = id; for (const socket of clients) { if (socket.readyState === socket.OPEN) socket.send(payload); } } } catch (err) { console.error("[poll]", err); } finally { polling = false; } } // Seed from the latest id so a fresh isolate sends only new rows, not the whole table, then poll. pool .query("SELECT coalesce(max(id), 0)::text AS id FROM events") .then((seed) => { lastId = seed.rows[0].id; }) .catch((err) => console.error("[seed]", err)) .finally(() => setInterval(poll, 1000).unref?.()); ``` - **Latency:** up to the interval (~1s) — fine for counters, chat, and dashboards. - **Scaling:** database load grows with the number of live isolates, not clients. Keep the cursor on an indexed `serial`/`bigserial` PK and the interval sane. - **Scale to Zero:** ✅ preserved — polling stops when no clients are connected, so the compute suspends on its normal timer. - **Ordering:** `WHERE id > cursor` can skip a row that commits out of sequence: a transaction that took a lower id but commits after a higher one is already behind the cursor, so the poll never returns it. For a broadcast feed occasional loss is usually fine; when you need every row, use `LISTEN`/`NOTIFY` or poll by `created_at` with a small overlap window and dedupe by id. **2. `LISTEN`/`NOTIFY` — lowest latency, but requires disabling Scale to Zero.** Each isolate `LISTEN`s on a channel over a dedicated **unpooled** connection; broadcasting is `NOTIFY`, so every isolate (including the sender's) re-pushes to its sockets. Near-instant — but the listener holds an idle connection that **does not count as active**, so [Scale to Zero](https://neon.com/docs/introduction/scale-to-zero) suspends the compute and drops it, silently killing the feed. Only use it on an **always-on** compute (Scale to Zero disabled — a paid-plan setting). ```typescript import { attachDatabasePool } from "@neon/functions"; import { Pool, Client } from "pg"; const pool = new Pool({ connectionString: process.env.DATABASE_URL, max: 5 }); attachDatabasePool(pool); const CHANNEL = "chat_events"; // One dedicated DIRECT connection per isolate, just to receive events. // Use DATABASE_URL_UNPOOLED — LISTEN needs a real session, not a pooled one. // Don't call attachDatabasePool here: it would silence the idle drop that killed the feed. // The error listener keeps the process alive; reconnect the client on error in production (omitted here). const listener = new Client({ connectionString: process.env.DATABASE_URL_UNPOOLED, }); listener.on("error", (err) => { console.error(err); }); listener.connect().then(() => listener.query(`LISTEN ${CHANNEL}`)); listener.on("notification", (msg) => { if (!msg.payload) return; for (const socket of clients) { if (socket.readyState === socket.OPEN) socket.send(msg.payload); } }); // Broadcast by NOTIFYing through the pool — every isolate's listener fires. function broadcast(event: unknown) { return pool.query("SELECT pg_notify($1, $2)", [ CHANNEL, JSON.stringify(event), ]); } ``` **3. External pub/sub (e.g. [Upstash](https://upstash.com) Redis) — best at scale.** For high fan-out, sub-second latency at large connection counts, or multi-region, publish/subscribe through a dedicated broker. Highest throughput, and it doesn't touch Postgres or block Scale to Zero — at the cost of another service to run. **Rule of thumb:** start with **polling** (works with Scale to Zero, no extra infra); switch to `LISTEN`/`NOTIFY` only on always-on compute that needs sub-second latency; move to Redis when fan-out outgrows Postgres. ### Client must reconnect Idle functions are evicted (and isolates restart for operational reasons), so a client's socket **will** drop — treat reconnection as normal, not exceptional. Reconnect with exponential backoff, capped, and **re-mint a fresh token on every attempt** (tokens are short-lived, so a stale one fails the `upgrade` auth check): ```typescript let closed = false, retry = 0, timer: ReturnType; async function connect() { if (closed) return; const token = await getToken(); // re-mint each attempt; short-lived const ws = new WebSocket(`${WS_URL}?token=${encodeURIComponent(token)}`); ws.onopen = () => { retry = 0; // reset backoff on success }; ws.onmessage = (e) => { /* apply the event */ }; ws.onclose = () => { if (!closed) timer = setTimeout(connect, Math.min(1000 * 2 ** retry++, 15000)); }; ws.onerror = () => ws.close(); // let onclose drive the retry } connect(); ``` Together — `upgradeWebSocket` inside `fetch`, JWT auth over `?token=`, cross-isolate fan-out, and client backoff — these compose into a complete realtime chat backend on a single function. ## Server-Sent Events (SSE) When you only need **server → client** streaming (live counters, notifications, progress, token streams), SSE is simpler than a WebSocket and needs no upgrade at all: a plain `fetch` handler returns a `Response` whose body is a `ReadableStream` with `Content-Type: text/event-stream`, and the runtime holds it open as long as bytes flow. The browser consumes it with `EventSource`, which **reconnects on its own** — so there's no client backoff to write. ```typescript // src/index.ts — minimal SSE endpoint const encoder = new TextEncoder(); export default { fetch: () => { let t: ReturnType; return new Response( new ReadableStream({ start(controller) { controller.enqueue(encoder.encode("data: hello\n\n")); t = setInterval( () => controller.enqueue(encoder.encode(": ping\n\n")), 25_000, ); }, cancel() { clearInterval(t); // fires when the client disconnects }, }), { headers: { "Content-Type": "text/event-stream", "Cache-Control": "no-cache, no-transform", }, }, ); }, }; ``` The same rules as WebSockets apply. **Heartbeat:** a stream stays open only while bytes flow — Neon's window is 15 minutes ([Timeouts and Runtime Limits](#timeouts-and-runtime-limits)) but proxies are usually far stricter, so emit a `: ping\n\n` comment every ~25–30s (shown above) to keep idle streams from being dropped. Keep state in Postgres, and fan out across isolates using one of the [sync strategies](#keeping-clients-in-sync-across-isolates-do-not-skip-this) (hold a `Set` of stream controllers and `enqueue` to each). `EventSource` is GET-only and can't set headers, so authenticate with a `?token=` query param or cookie, exactly like the WebSocket case. [references/sse.md](https://neon.com/docs/ai/skills/neon-functions/references/sse.md) has the full pattern — Hono variant, cross-isolate fan-out, wire format, client, and caveats. ## Function Triggers A Function Trigger POSTs JSON to your function on a cron (`schedule`) or when an object is created in Object Storage (`storage_object_created`). Declare it in `neon.ts`, apply with `neon deploy`, and authenticate the delivery with `parseTriggerDelivery` (`@neon/functions/triggers`). `parseTrigger` (Hono) and `parseTriggerInvocation` stay schedule-only. Prefer `neon.ts`; CLI and the Neon MCP trigger tools (`list_triggers`, `create_trigger`, …) are the backup. Trigger routes must not require a user JWT or `X-Secret`; Neon POSTs to the native URL without those. Production caller shapes: [references/production-hardening.md](references/production-hardening.md). Full field list, CLI, MCP, payload, inheritance, and both handler shapes: [references/function-triggers.md](references/function-triggers.md). ## MCP Servers An [MCP](https://modelcontextprotocol.io) server is a natural Functions workload: a long-running HTTP handler that exposes tools to AI clients (Cursor, Claude, ChatGPT, agents), with those tools reading and writing the branch's Postgres right next to the compute. MCP's **streamable HTTP transport** is a plain `POST`/`GET` on a single endpoint (conventionally `/mcp`), so it maps onto a function's `fetch` handler with no `upgrade` method or extra protocol. The simplest host is a Hono app using the official [`@modelcontextprotocol/sdk`](https://github.com/modelcontextprotocol/typescript-sdk) plus [`@hono/mcp`](https://github.com/honojs/middleware/tree/main/packages/mcp), which bridges the transport to a route. Build the server, register its tools, and create the transport once at module scope, then hand every `/mcp` request to it: ```typescript const transport = new StreamableHTTPTransport(); app.all("/mcp", async (c) => { if (!mcpServer.isConnected()) await mcpServer.connect(transport); return transport.handleRequest(c); }); ``` Because the function's URL is public, **authenticate before connecting the transport** — [Better Auth](https://better-auth.com) covers both OAuth (its MCP plugin makes your app the authorization server so third-party clients self-authorize per the MCP spec) and a simpler API-key / session-JWT check for your own callers. Public-consumer edge protection: [references/production-hardening.md](references/production-hardening.md). [references/mcp.md](https://neon.com/docs/ai/skills/neon-functions/references/mcp.md) has the full pattern — server with Postgres-backed tools via Drizzle, both Better Auth auth options, and testing with `mcporter` / `add-mcp`. ## Integrations and Observability ### Built-in branch logs ```bash neon logs query --branch production --source function --since 1h ``` Functions is one of the two sources branch logs cover today, alongside Object Storage. Logs are scoped to a single branch, so pass `--branch` when the deployed function isn't on the branch you're checked out on. Everything else about logs — the required CLI version, filters, the SDK, and the Loki-compatible read API — is in the parent `neon` skill's **Observability** section. ### Application instrumentation A function is a long-lived Node.js process running a web-standard request/response handler, so standard Node integration SDKs work unchanged. Initialize them once at module load, gated on an env var so local dev and unconfigured branches stay a no-op, and pass secrets via `--env` or `neon.ts` `env`. - **Sentry** — error monitoring across the HTTP framework, the function runtime, and an agent's own caught/fallback failures (the long-running case Functions target): see [references/sentry.md](https://neon.com/docs/ai/skills/neon-functions/references/sentry.md). - **Mastra Studio (Mastra Cloud)** — run a Mastra agent on a function and ship its traces to a Studio project for observability: see [references/mastra-studio.md](https://neon.com/docs/ai/skills/neon-functions/references/mastra-studio.md). ## Neon Documentation The Neon documentation is the source of truth and Functions is evolving rapidly, so always verify against the official docs. Any doc page can be fetched as markdown by appending `.md` to the URL or by requesting `Accept: text/markdown`. Find the right page from the docs index (https://neon.com/docs/llms.txt) and the changelog announcements. ## Further Reading - https://neon.com/docs/compute/functions/overview.md - https://neon.com/docs/compute/functions/get-started.md - https://neon.com/docs/compute/functions/deploy.md - https://neon.com/docs/compute/functions/environment-variables.md - https://neon.com/docs/compute/functions/reference/neon-ts.md - https://neon.com/docs/compute/functions/reference/runtime-limits.md - https://neon.com/docs/compute/functions/authentication.md - https://neon.com/docs/compute/functions/custom-domains.md - https://neon.com/docs/cli/triggers.md - [references/function-triggers.md](references/function-triggers.md) - [references/production-hardening.md](references/production-hardening.md) --- ## 4. neon-object-storage - **Source:** https://github.com/neondatabase/agent-skills/blob/main/skills/neon-object-storage/SKILL.md - **Raw:** https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon-object-storage/SKILL.md - **Markdown:** https://skillsdocs.com/neondatabase/agent-skills/neon-object-storage.md - **Licence:** Apache-2.0 — https://spdx.org/licenses/Apache-2.0.html --- name: neon-object-storage description: >- S3-compatible object storage that branches with your Neon project, so files and the database stay in sync across every branch. Use when a user wants object storage, a bucket, blob/file storage, or somewhere to put uploads, images, documents, avatars, or user-generated files for their app or agent — especially when they already use (or are setting up) Lakebase Postgres and don't want to add a separate storage provider like AWS S3, Cloudflare R2, or Supabase Storage. Triggers include "object storage", "bucket", "blob storage", "file storage", "store uploads/images/files", "S3-compatible storage", "presigned URL", "where do I put files", "storage logs", "bucket logs", "CDN in front of object storage", "Neon Object Storage", "Neon Storage", and "storage that branches with my database". metadata: parent: neon source: https://github.com/neondatabase/agent-skills/tree/main/skills/neon-object-storage --- **FIRST**: Use the parent `neon` skill for a Neon overview, getting started with Neon, Neon development best practices, and more. If the `neon` skill is not installed, fetch it from https://neon.com/docs/ai/skills/neon/SKILL.md or install it with: ```bash neon skills -s neon -y ``` # Neon Object Storage Currently available in `aws-us-east-2`, `aws-us-east-1`, `aws-eu-central-1`, and `aws-ap-southeast-1`. Neon Object Storage is S3-compatible object storage that branches with your projects: every branch gets its own isolated storage state, so files and database rows stay in sync across dev, preview, staging, and production. Use this skill to help the user store and serve files that branch alongside their database. Deliver a working bucket and upload/download flow, a branch-aware S3 client wired to the injected env vars, or a precise answer from the official Neon docs. ## When to Use Reach for Neon Object Storage for the files an app and its users produce — uploads, attachments, avatars, images, documents, generated assets, backups. It is the default place to put them when the app is already on Neon: - **They already use Lakebase Postgres and don't want a second provider.** One backend, one bill, one CLI, one set of branches — instead of standing up and wiring a separate AWS S3 / R2 / Supabase Storage account. The same Neon credential that backs the database backs storage. - **Files must stay in sync with the database across environments.** Storage branches _together with_ your Postgres data. Fork a branch and the child instantly inherits the parent's buckets and objects at that point in time — copy-on-write, so no data is duplicated. This is what makes agent, dev, preview, and test environments seamless: a preview branch gets a consistent snapshot of _both_ the rows and the files they reference, and writes on the child never touch the parent. - **They want safe, throwaway environments.** Upload, overwrite, and delete files in a preview/CI branch without any risk to production data, then drop the branch. - **They want standard S3 tooling.** It's built on S3 semantics and speaks the S3 API, so the AWS SDKs, `boto3`, the AWS CLI, and presigned URLs all work — reliable and familiar, with no proprietary client. If the files in question ship with the app itself — HTML, JS bundles, CSS, the images in `public/` — that's static web hosting and belongs on Vercel, Netlify, or Cloudflare instead. Public assets that are served from a bucket want a CDN in front of them (see [Architecture: Where Object Storage Fits](#architecture-where-object-storage-fits)). ## What It Does - **S3-compatible** — Works with existing S3 SDKs, `boto3`, the AWS CLI, and presigned URLs. Path-style addressing and SigV4 only. - **Branches with your database** — Every Neon branch gets its own isolated, copy-on-write storage state. Forking copies no data. - **Two access modes** — `private` buckets require a credential for every operation; `public_read` buckets allow anonymous reads with authenticated writes. - **One credential system** — The same Neon credential system used by Functions and the AI Gateway. ## Availability Check this precondition before setting anything up: Neon Object Storage is currently available in `aws-us-east-2`, `aws-us-east-1`, `aws-eu-central-1`, and `aws-ap-southeast-1`. Confirm the user's Neon project is in one of these regions before proceeding. Region coverage: https://neon.com/docs/get-started/backend-overview.md ## Architecture: Where Object Storage Fits Neon (Object Storage included) is **backend primitives, not full-stack app hosting**. Object Storage holds the files the app and its users produce — uploads, attachments, avatars, documents, generated images, backups — keyed from Postgres rows on the same branch. Two boundaries follow from that: - **Put a CDN in front of public assets.** A `public_read` object is read anonymously at `${AWS_ENDPOINT_URL_S3}//` — the branch's storage endpoint, injected as an env var (see [Environment Variables](#environment-variables)). For assets a browser loads on every page view — avatars, product images, anything hot — use that as the origin for a Cloudflare or Vercel CDN, and set `Cache-Control` on `PutObject` so the edge knows how long to hold each object. A cached object is only as fresh as its key, so write each version to a new key (`avatars//.jpg`) and repoint the key stored in Postgres, rather than overwriting one key and waiting out the TTL. The endpoint is branch-scoped, so a production CDN points at the production branch while preview branches read their own endpoint directly rather than sharing a cache. Private buckets stay on presigned URLs instead, which carry their signature in the query string. - **Host the app itself elsewhere.** Anything checked into the repo — HTML, JS bundles, CSS, and the images and fonts that ship in `public/` — belongs on Vercel, Netlify, or Cloudflare, along with the index documents, SPA fallbacks, and custom domains that go with them. Neon has no website mode to serve them through: `PutBucketWebsite` returns `501 Not Implemented`. ## Setup Object storage is part of the `neon.ts` infrastructure-as-code config (see the `neon` skill for the branch-first workflow, `link`/`checkout`, and `neon.ts` basics). Declare buckets under `buckets`, keyed by bucket name: ```typescript // neon.ts import { defineConfig } from "@neon/config/v1"; export default defineConfig({ buckets: { images: {}, // private by default "public-assets": { access: "public_read" }, }, }); ``` Provision the declared buckets on the linked branch: ```bash neon deploy # alias for `neon config apply` ``` ## Neon Infrastructure as Code (`neon.ts`) The `buckets` block above is part of `neon.ts`, Neon's infrastructure-as-code file — one TypeScript file declares your buckets alongside every other service the branch should have (see the `neon` skill for the full reference). Reconcile the declaration against a branch the Terraform way: ```bash neon config status # print the branch's live config (which buckets exist) neon config plan # dry-run diff of what apply would change neon config apply # create the declared buckets (neon deploy is an alias) ``` Buckets are **branch-scoped**: when a `neon.ts` is present, `neon checkout` applies the policy as it _creates_ a branch, so a fresh preview/CI branch comes up with its buckets already provisioned (and copy-on-write objects inherited from the parent). Checking out an _existing_ branch doesn't reconcile it — run `neon deploy` to apply changes. Provisioning (`config apply` / `deploy`), `link`, and `checkout` also pull the branch's S3 credentials into your local `.env.local`, so the same `env pull` step shown below happens for you on those commands. ## Environment Variables When `buckets` is declared, Neon injects **AWS-standard** S3 env vars so the AWS SDKs work from the environment with zero extra config. Inside a deployed Neon Function these are injected automatically; locally, pull them onto disk (or inject them at runtime) via the CLI: ```bash neon env pull # writes the branch's vars into .env (or .env.local) # or, without writing a file, inject at runtime: neon-env run -- ``` | Variable | Meaning | | ----------------------- | --------------------------------------------------- | | `AWS_ACCESS_KEY_ID` | S3 Access Key ID (the branch credential's token id) | | `AWS_SECRET_ACCESS_KEY` | S3 Secret Access Key | | `AWS_ENDPOINT_URL_S3` | Branch S3 endpoint URL | | `AWS_REGION` | Region, e.g. `us-east-2` | Because the names are AWS-standard, the AWS SDK picks up the credentials, endpoint, and region from the environment automatically. Credentials are branch-scoped and valid for that branch and all its descendants. For typed, validated access to these credentials instead of reading `process.env` directly, pass the same `neon.ts` config object to `parseEnv` from `@neon/env` — it returns an `env.storage` namespace (`accessKeyId`, `secretAccessKey`, `endpoint`, `region`) derived from your config. See the `neon` skill. ## Working with Objects: the Files SDK (Recommended) The simplest, most portable way to read and write objects is the [Files SDK](https://files-sdk.dev) with its `neon` adapter — a small, unified storage API (`upload`, `download`, `url`, `list`, `exists`, `copy`, `delete`, `signedUploadUrl`) over web-standard I/O. It uses the AWS S3 client under the hood, configured appropriately for Neon, and relabels errors as `Neon error` — so there's nothing to misconfigure. Reach for this first. Install it alongside the AWS S3 peer dependencies the adapter uses internally: ```bash npm install files-sdk @aws-sdk/client-s3 @aws-sdk/s3-presigned-post @aws-sdk/s3-request-presigner ``` The adapter resolves its endpoint, region, and credentials from the same injected `AWS_*` env vars — pass only the bucket name: ```typescript import { Files } from "files-sdk"; import { neon } from "files-sdk/neon"; const files = new Files({ adapter: neon({ bucket: "images" }) }); // Upload — body may be a Buffer, Uint8Array, Blob, File, ReadableStream, or string await files.upload("generated/cat.jpg", fileBuffer, { contentType: "image/jpeg" }); // Download const file = await files.download("generated/cat.jpg"); const bytes = new Uint8Array(await file.arrayBuffer()); // Presigned GET — share without exposing credentials (defaults to a 1h expiry) const url = await files.url("generated/cat.jpg", { expiresIn: 3600 }); // Plus: files.exists(), files.list({ prefix }), files.copy(), files.delete(), files.signedUploadUrl() ``` Swap the adapter import (`files-sdk/s3`, `files-sdk/r2`, `files-sdk/gcs`, …) and the rest of your code is unchanged. ## Working with Objects: the AWS S3 Client (Alternative) Neon speaks the S3 API directly, so you can drop down to the AWS SDK whenever you prefer the native client or already depend on it. The credentials, endpoint, and region are read from the standard AWS env chain, so the only setting you pass is `forcePathStyle: true` — Neon requires path-style addressing, so the S3 client **must** set it: ```typescript import { S3Client } from "@aws-sdk/client-s3"; const s3 = new S3Client({ forcePathStyle: true, // required: Neon uses path-style addressing }); ``` Then upload, download, and presign with the raw command objects: ```typescript import { PutObjectCommand, GetObjectCommand } from "@aws-sdk/client-s3"; import { getSignedUrl } from "@aws-sdk/s3-request-presigner"; const BUCKET = "images"; // Upload await s3.send( new PutObjectCommand({ Bucket: BUCKET, Key: "generated/cat.jpg", Body: fileBuffer, ContentType: "image/jpeg", }), ); // Download const res = await s3.send( new GetObjectCommand({ Bucket: BUCKET, Key: "generated/cat.jpg" }), ); const bytes = await res.Body?.transformToByteArray(); // Presigned GET — share without exposing credentials const url = await getSignedUrl( s3, new GetObjectCommand({ Bucket: BUCKET, Key: "generated/cat.jpg" }), { expiresIn: 3600 }, ); ``` ## Pairing Storage with the Database on a Branch The canonical pattern: an agent generates an image → `PutObject` into the `images` bucket → a row is inserted in Postgres → a presigned URL is returned on read. Store the bucket **key** (not the bytes) in a Postgres column, and presign on read. Because both the row and the object live on the same branch, they branch together and never drift. ## CLI Bucket and Object Commands `neon` also has first-class bucket/object commands (`neon bucket create|list|delete`, `neon bucket object put|get|list|delete`) for scripting and one-off operations. ## Built-in Branch Logs ```bash neon logs query --branch production --source storage --since 1h ``` Storage is one of the two sources branch logs cover today, alongside Neon Functions. Logs are scoped to a single branch, so pass `--branch` when the bucket you're debugging isn't on the branch you're checked out on. Everything else about logs — the required CLI version, filters, the SDK, and the Loki-compatible read API — is in the parent `neon` skill's **Observability** section. ## Neon Documentation The Neon documentation is the source of truth and Object Storage is evolving rapidly, so always verify against the official docs. Any doc page can be fetched as markdown by appending `.md` to the URL or by requesting `Accept: text/markdown`. Find the right page from the docs index (https://neon.com/docs/llms.txt) and the changelog announcements. ## Further Reading - https://neon.com/docs/get-started/backend-overview.md - https://neon.com/docs/storage/overview.md - https://neon.com/docs/storage/get-started.md - https://neon.com/docs/storage/buckets.md - https://neon.com/docs/storage/objects.md - https://neon.com/docs/storage/authentication.md - https://neon.com/docs/storage/s3-compatibility.md - https://neon.com/docs/storage/troubleshooting.md - https://files-sdk.dev — Files SDK docs (the `neon` adapter) --- ## 5. neon-postgres-branches - **Source:** https://github.com/neondatabase/agent-skills/blob/main/skills/neon-postgres-branches/SKILL.md - **Raw:** https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon-postgres-branches/SKILL.md - **Markdown:** https://skillsdocs.com/neondatabase/agent-skills/neon-postgres-branches.md - **Licence:** Apache-2.0 — https://spdx.org/licenses/Apache-2.0.html --- name: neon-postgres-branches description: >- Choose and create the right Neon branch type for testing and development. Use when users ask about Neon branching, migration testing with real data, isolated test environments, schema-only branch workflows for sensitive data, resetting a branch from its parent, branch expiration and CI/CD branch lifecycles, or branch creation via Neon CLI or Neon MCP. Triggers include "Neon branch", "test migrations safely", "branch production data", "schema-only branch", "reset branch", "branch per PR" and "sensitive data testing". metadata: parent: neon source: https://github.com/neondatabase/agent-skills/tree/main/skills/neon-postgres-branches --- **FIRST**: Use the parent `neon` skill for a Neon overview, getting started with Neon, Neon development best practices, and more. If the `neon` skill is not installed, fetch it from https://neon.com/docs/ai/skills/neon/SKILL.md or install it with: ```bash neon skills -s neon -y ``` # Lakebase Postgres Branching **Outcome:** a created Neon branch — or a clear, actionable next step if creation cannot proceed. Choose the correct branch type, then execute branch creation with the CLI (or MCP where the CLI isn't usable). - **Normal branch** for realistic migration and query testing with real data. - **Schema-only branch (Beta)** for sensitive data workflows where structure is needed without copying rows. ## Branch Type Decision Use this decision rule first: 1. If the user wants to test complex migrations, performance, or behavior against production-like data, choose a **normal branch**. 2. If the user needs to avoid copying sensitive data, choose a **schema-only branch**. If the request is ambiguous, ask one clarifying question: "Do you need realistic data for testing, or only schema structure because the data is sensitive?" ## Tool Selection: CLI or MCP Support both the Neon CLI and the Neon MCP server, but **default to the CLI**. Use MCP only when the CLI is unavailable or blocked in your environment, cannot be authenticated, or the user explicitly asks for MCP. - CLI link: https://neon.com/docs/cli/quickstart.md - MCP link: https://neon.com/docs/ai/neon-mcp-server.md ### Selection order 1. Check the CLI first: - Run `neon --version` to confirm the CLI is installed. - Run `neon projects list` to confirm auth/context. 2. If the CLI is missing, direct installation via quickstart. 3. If the CLI is installed but not authenticated, guide the user through `neon auth` (or API key auth), then continue. 4. Switch to MCP when the CLI cannot be used — no CLI access in the environment, execution blocked, or authentication not possible — or when the user explicitly asks for MCP. Confirm Neon MCP tools are available and authenticated (for example, listing projects works), then follow the MCP branch flow below. 5. If neither path is successful, use the Neon REST API: - https://neon.com/docs/guides/branching-neon-api.md ### MCP branch flow 1. Choose normal vs schema-only based on data sensitivity and migration-testing goals. 2. Use branch tools (for example, `create_branch`) to create the branch. 3. Validate with read tools (for example, `describe_branch`). 4. For migration workflows, prefer branch-based migration flows before applying to main. ## Create a Normal Branch (Preferred for Real-Data Migration Testing) Use this when the user needs realistic testing conditions. Real production-like data can expose edge cases your seed or data migration scripts miss, which helps catch migration issues before going live. Link: https://neon.com/docs/introduction/branching.md ### Steps 1. Settle the tool path first (see [Selection order](#selection-order)): verify the CLI with `neon --version`, and fall back to MCP only if the CLI isn't usable. 2. Ensure project context is set (`neon set-context --project-id `) or include `--project-id` on commands. 3. Create the branch: ```bash neon branches create \ --name \ --parent \ --expires-at 2026-12-15T18:02:16Z ``` 4. Optionally fetch a connection string for the new branch: ```bash neon connection-string ``` ## Create a Schema-Only Branch (Beta, Sensitive Data) Use this when users must not copy production rows into the test branch. Link: https://neon.com/docs/guides/branching-schema-only.md ### Steps 1. Settle the tool path first (see [Selection order](#selection-order)): verify the CLI with `neon --version`, and fall back to MCP only if the CLI isn't usable. 2. Create the schema-only branch: ```bash neon branches create \ --name \ --parent \ --schema-only \ --expires-at 2026-12-15T18:02:16Z ``` If multiple projects exist, include `--project-id`: ```bash neon branches create \ --name \ --parent \ --schema-only \ --project-id \ --expires-at 2026-12-15T18:02:16Z ``` ### Beta Support Guidance (Mandatory) Schema-only branching is in Beta. If users report unexpected behavior, errors, or missing capabilities: 1. Ask them to share feedback in the Neon Console: - https://console.neon.tech/app/projects?modal=feedback 2. Recommend opening a support conversation in the Neon Discord: - https://neon.com/discord ## Reset from Parent Use this when a child branch has drifted and the user wants a clean refresh from the parent branch's latest schema and data. Link: https://neon.com/docs/guides/reset-from-parent.md ### What it does - Fully replaces the child branch schema and data with the parent's latest state. - Does not merge; local changes on the child branch are lost. - Keeps the same connection details, but active connections are briefly interrupted during reset. ### When to recommend it - Development or staging branch is too far behind production. - User wants to start a new feature from a clean parent-aligned state. - Team wants to refresh staging from production for consistent testing baselines. ### Hard constraints and blockers - Only child branches can be reset (root branches and schema-only root branches cannot be reset from parent). - If the target branch has children, reset is blocked until those child branches are removed. - After a parent branch is restored from snapshot, reset-from-parent may be unavailable for up to 24 hours. - Reset-from-parent always uses the current parent state; use Instant restore for point-in-time recovery needs. ### CLI usage ```bash neon branches reset --parent --preserve-under-name ``` If project context is not already set, include the project ID: ```bash neon branches reset --parent --preserve-under-name --project-id ``` `--preserve-under-name` keeps the pre-reset state as a backup branch for rollback, but adds one extra branch to clean up later. Optional context setup to avoid repeating `--project-id`: ```bash neon set-context --project-id ``` ### Console and API usage - **Console:** Open the target child branch, then select **Reset from parent** from **Actions**. - **API:** Use the restore endpoint for the branch and set `source_branch_id` to the parent branch ID. ## Notes and Caveats - Schema-only branches are for structure-only cloning and sensitive/compliant data controls. - Schema-only branches are independent root branches (no parent branch and no shared history), so reset-from-parent does not apply. - For migration testing that depends on real-world row shapes, volumes, and edge cases, prefer normal branches. - Root branch allowances and per-branch storage limits can cap how many schema-only branches users can create. - If a user is unsure, default recommendation is: - **Normal branch** for migration validation. - **Schema-only branch** for compliance and privacy constraints. ## Useful Workflow Patterns If the user asks for process recommendations (not just a single command), suggest these: - **One branch per PR:** Create branch when PR opens, delete when merged/closed, keep migration tests isolated. - **One branch per test run:** Create branch at pipeline start, run migrations/tests, delete at end for deterministic CI. - **One branch per developer:** Isolated dev environments with production-like shape; avoid team collisions on shared test data. - **PII-aware branching:** If production has sensitive data, derive dev/PR branches from an anonymized branch or use schema-only branches. - **Ephemeral lifecycle hygiene:** Set branch expiration and automate cleanup so old branches do not accumulate avoidable storage/history cost. ### Post-creation environment update prompt After branch creation, ask whether the user wants to update local environment credentials to point at the new branch. - Ask: "Do you want me to update your `.env` `DATABASE_URL` to this new branch connection string?" - If yes, write the new branch connection string to the requested env file/key. - If no, leave credentials unchanged and share the connection string for manual use. - Never overwrite an existing env key without explicit confirmation. ## Neon Infrastructure as Code (`neon.ts`) Beyond creating branches imperatively (CLI / MCP / API above), you can **program what configuration new branches receive** declaratively in `neon.ts` — Neon's infrastructure-as-code file (see the `neon` skill for the full reference). The `branch` property is a function of the branch being evaluated that returns its settings, so every branch born from your project gets a consistent lifecycle and compute profile without per-branch flags. ```bash npm i @neon/config ``` ```typescript // neon.ts import { defineConfig } from "@neon/config/v1"; export default defineConfig({ branch: (branch) => { if (branch.exists) return {}; // never reconcile existing branches if (branch.isDefault) return { protected: true }; if (branch.name.startsWith("preview/") || branch.name.startsWith("dev")) { return { parent: "main", ttl: "7d", // ephemeral: auto-expire 7 days after creation (max 30d) postgres: { computeSettings: { autoscalingLimitMinCu: 0.25, // scale to zero autoscalingLimitMaxCu: 1, // keep throwaway branches cheap suspendTimeout: "5m", }, }, }; } return {}; }, }); ``` The closure receives a read-only descriptor of the target branch — `name`, `exists`, `isDefault`, `parentId`, and more — and returns the tuning to apply: `parent`, `ttl` (auto-expiry), `protected`, and `postgres.computeSettings`. This is the declarative complement to the **Ephemeral lifecycle hygiene** and per-PR / per-test patterns above: instead of remembering `--expires-at` on every `neon branches create`, the TTL and compute profile live in version control and apply to every matching branch. Because `neon checkout` applies this policy when it **creates** a branch, a fresh `preview/*` or `dev-*` branch comes up already expiring and scaled-to-zero. Checking out an _existing_ branch doesn't reconcile it — run `neon deploy` (alias for `neon config apply`) to apply changes to a branch that already exists. ## Branching in CI/CD Common CI/CD use cases for Neon branches: - **Per-PR preview deployments:** Branch on PR open, deploy the preview against it, delete on close. Each PR gets an isolated database branch. Injecting the branch's `DATABASE_URL` into the deployed app is hosting-provider-specific — see [preview-branches-with-cloudflare](https://github.com/neondatabase/preview-branches-with-cloudflare), [preview-branches-with-vercel](https://github.com/neondatabase/preview-branches-with-vercel), or [preview-branches-with-fly](https://github.com/neondatabase/preview-branches-with-fly) for tested patterns. - **Migration testing in CI:** Run risky schema changes against a branch with production-like data before merge. - **Schema diff visibility:** Use the [schema-diff GitHub Action](https://github.com/marketplace/actions/neon-schema-diff-github-action) to auto-comment a DB-layer diff on the PR. ## Examples ### Example 1: Migration testing with realistic data **User input:** "I need to test a risky migration against production-like data." **Agent output shape:** 1. Recommend a normal branch and explain why. 2. Share docs link: https://neon.com/docs/introduction/branching 3. Check the tool path first (CLI with `neon --version`; MCP only if the CLI isn't usable). 4. Provide commands: - `neon branches create --name migration-test --parent main --expires-at 2026-12-15T18:02:16Z` - `neon connection-string migration-test` ### Example 2: Sensitive data development workflow **User input:** "We cannot copy production data because of compliance." **Agent output shape:** 1. Recommend schema-only branch and explain why. 2. Share docs link: https://neon.com/docs/guides/branching-schema-only 3. Check the tool path first (CLI with `neon --version`; MCP only if the CLI isn't usable). 4. Provide command: - `neon branches create --name compliance-dev --parent main --schema-only --project-id --expires-at 2026-12-15T18:02:16Z` 5. Mention Beta support path: - https://console.neon.tech/app/projects?modal=feedback - https://neon.com/discord ## Further Reading - https://neon.com/docs/guides/branch-expiration.md - https://neon.com/docs/guides/neon-github-integration.md - https://neon.com/docs/ai/neon-mcp-server.md - https://neon.com/branching --- ## 6. neon-postgres-egress-optimizer - **Source:** https://github.com/neondatabase/agent-skills/blob/main/skills/neon-postgres-egress-optimizer/SKILL.md - **Raw:** https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon-postgres-egress-optimizer/SKILL.md - **Markdown:** https://skillsdocs.com/neondatabase/agent-skills/neon-postgres-egress-optimizer.md - **Licence:** Apache-2.0 — https://spdx.org/licenses/Apache-2.0.html --- name: neon-postgres-egress-optimizer description: >- Diagnose and fix excessive Postgres egress (network data transfer) in a codebase. Use when a user mentions high database bills, unexpected data transfer costs, network transfer charges, egress spikes, "why is my Neon bill so high", "database costs jumped", SELECT * optimization, query overfetching, reduce Neon costs, optimize database usage, or wants to reduce data sent from their database to their application. Also use when reviewing query patterns for cost efficiency, even if the user doesn't explicitly mention egress or data transfer. metadata: parent: neon source: https://github.com/neondatabase/agent-skills/tree/main/skills/neon-postgres-egress-optimizer --- **FIRST**: Use the parent `neon` skill for a Neon overview, getting started with Neon, Neon development best practices, and more. If the `neon` skill is not installed, fetch it from https://neon.com/docs/ai/skills/neon/SKILL.md or install it with: ```bash neon skills -s neon -y ``` # Postgres Egress Optimizer Guide the user through diagnosing and fixing application-side query patterns that cause excessive data transfer (egress) from their Postgres database. Most high egress bills come from the application fetching more data than it uses. Work the four steps in order: **diagnose** which queries transfer the most data, **analyze** the codebase behind them, **fix** the anti-patterns, then **verify** nothing broke and the transfer actually dropped. ## Step 1: Diagnose Identify which queries transfer the most data. The primary tool is the `pg_stat_statements` extension. ### Check if pg_stat_statements is available ```sql SELECT 1 FROM pg_stat_statements LIMIT 1; ``` If this errors, the extension needs to be created: ```sql CREATE EXTENSION IF NOT EXISTS pg_stat_statements; ``` On Neon the extension is available by default, but it may still need this CREATE EXTENSION step. ### Handle empty stats Stats are cleared when a Neon compute scales to zero and restarts. If the stats are empty or the compute recently woke up: 1. Reset the stats to start a clean measurement window: `SELECT pg_stat_statements_reset();` 2. Let the application run under representative traffic for at least an hour. 3. Return and run the diagnostic queries below. If the user has stats from a production database, use those. If they have no access to production stats, proceed to Step 2 and analyze the codebase directly — code-level patterns are often sufficient to identify the worst offenders. ### Diagnostic queries Run these to identify the top egress contributors. Focus on queries that return many rows, return wide rows (JSONB, TEXT, BYTEA columns), or are called very frequently. **Queries returning the most total rows:** ```sql SELECT query, calls, rows AS total_rows, rows / calls AS avg_rows_per_call FROM pg_stat_statements WHERE calls > 0 ORDER BY rows DESC LIMIT 10; ``` **Queries returning the most rows per execution** (poorly scoped SELECTs, missing pagination): ```sql SELECT query, calls, rows AS total_rows, rows / calls AS avg_rows_per_call FROM pg_stat_statements WHERE calls > 0 ORDER BY avg_rows_per_call DESC LIMIT 10; ``` **Most frequently called queries** (candidates for caching): ```sql SELECT query, calls, rows AS total_rows, rows / calls AS avg_rows_per_call FROM pg_stat_statements WHERE calls > 0 ORDER BY calls DESC LIMIT 10; ``` **Longest running queries** (not a direct egress measure, but helps identify problem queries during a spike): ```sql SELECT query, calls, rows AS total_rows, round(total_exec_time::numeric, 2) AS total_exec_time_ms FROM pg_stat_statements WHERE calls > 0 ORDER BY total_exec_time DESC LIMIT 10; ``` ### Interpret the results Rank findings by estimated egress impact: - **High row count + wide rows** = biggest egress. A query returning 1,000 rows where each row includes a 50KB JSONB column transfers ~50MB per call. - **Extreme call frequency** on even small queries adds up. A query called 50,000 times/day returning 10 rows each = 500,000 rows/day. - **Cross-reference with the schema** to identify which columns are wide. Look for JSONB, TEXT, BYTEA, and large VARCHAR columns. ## Step 2: Analyze the Codebase For each query identified in Step 1, or for each database query in the codebase if no stats are available, check: - Does it select only the columns the response needs? - Does it return a bounded number of rows (LIMIT/pagination)? - Is it called frequently enough to benefit from caching? - Does it fetch raw data that gets aggregated in application code? - Does it use a JOIN that duplicates parent data across child rows? ## Step 3: Fix Apply the appropriate fix for each problem found. Below are the most common egress anti-patterns and how to fix them. ### Unused columns (SELECT \*) **Problem:** The query fetches all columns but the application only uses a few. Large columns (JSONB blobs, TEXT fields) get transferred over the wire and discarded. **Fix:** Name only the columns the response needs. **Before:** ```sql SELECT * FROM products; ``` **After:** ```sql SELECT id, name, price, image_urls FROM products; ``` ### Missing pagination **Problem:** A list endpoint returns all rows with no LIMIT. This is an unbounded egress risk — every new row in the table increases data transfer on every request. Flag this regardless of current table size. This is easy to miss because the application may work fine with small datasets. But at scale, an unpaginated endpoint returning 10,000 rows with even moderate column widths can transfer hundreds of megabytes per day. **Fix:** Bound the result set with `ORDER BY` plus `LIMIT`/`OFFSET`. **Before:** ```sql SELECT id, name, price FROM products; ``` **After:** ```sql SELECT id, name, price FROM products ORDER BY id LIMIT 50 OFFSET 0; ``` When adding pagination, check whether the consuming client already supports paginated responses. If not, pick sensible defaults and document the pagination parameters in the API. ### High-frequency queries on static data **Problem:** A query is called thousands of times per day but returns data that rarely changes. Every call transfers the same rows from the database. This pattern is only visible from `pg_stat_statements` — the code itself looks normal. Look for queries with extremely high call counts relative to other queries. Common examples: configuration tables, category lists, feature flags, user role definitions. **Fix:** Add a caching layer between the application and the database so it avoids hitting the database on every request. ### Application-side aggregation **Problem:** The application fetches all rows from a table and then computes aggregates (averages, counts, sums, groupings) in application code. The full dataset transfers over the wire even though the result is a small summary. **Fix:** Push the aggregation into SQL. **Before:** The application fetches entire tables and aggregates in code with loops or `.reduce()`. **After:** ```sql SELECT p.category_id, AVG(r.rating) AS avg_rating, COUNT(r.id) AS review_count FROM reviews r INNER JOIN products p ON r.product_id = p.id GROUP BY p.category_id; ``` ### JOIN duplication **Problem:** A JOIN between a wide parent table and a child table duplicates all parent columns across every child row. If a product has 200 reviews and the product row includes a 50KB JSONB column, the join sends that 50KB × 200 = ~10MB for a single request. This is distinct from the SELECT \* problem. Even if you select only needed columns, a JOIN still repeats the parent data for every child row. The fix is structural: avoid the join entirely. **Fix:** Split the join into two queries, one per table. **Before:** ```sql SELECT * FROM products LEFT JOIN reviews ON reviews.product_id = products.id WHERE products.id = 1; ``` **After (two separate queries):** ```sql SELECT id, name, price, description, image_urls FROM products WHERE id = 1; SELECT id, user_name, rating, body FROM reviews WHERE product_id = 1; ``` Two queries instead of one JOIN. The product data is fetched once. The reviews are fetched once. No duplication. ## Step 4: Verify After applying fixes: 1. **Run existing tests** to confirm nothing broke. 2. **Check the responses** — make sure the API still returns the same data shape. Column selection and pagination changes can break clients that depend on specific fields or full result sets. 3. **Measure the improvement** — if pg_stat_statements data is available, reset it (`SELECT pg_stat_statements_reset();`), let traffic run, then re-run the diagnostic queries to compare before and after. ## Neon Infrastructure as Code (`neon.ts`) The fixes above cut **egress** (data transferred out of Postgres). The other big non-prod cost lever is **compute**, and you can codify it durably in `neon.ts` — Neon's infrastructure-as-code file (see the `neon` skill for the full reference) — so dev, preview, and CI branches stay cheap by default instead of relying on per-branch flags: ```bash npm i @neon/config ``` ```typescript // neon.ts import { defineConfig } from "@neon/config/v1"; export default defineConfig({ branch: (branch) => { if (branch.exists || branch.isDefault) return {}; // don't touch prod return { ttl: "7d", // ephemeral branches auto-expire instead of accruing storage postgres: { computeSettings: { autoscalingLimitMinCu: 0.25, // scale to zero when idle autoscalingLimitMaxCu: 1, // cap autoscaling on throwaway branches suspendTimeout: "5m", }, }, }; }, }); ``` ```bash neon config apply # apply to the current branch (neon deploy is an alias) ``` This is complementary, not a substitute: query-pattern fixes are what actually reduce egress charges, while these settings keep non-production compute and storage from quietly inflating the same bill. Because `neon checkout` applies the policy when it creates a branch, new dev/preview branches inherit the cheap profile automatically. ## Further Reading - https://neon.com/docs/introduction/network-transfer.md - https://neon.com/docs/introduction/cost-optimization.md --- ## 7. neon-postgres - **Source:** https://github.com/neondatabase/agent-skills/blob/main/skills/neon-postgres/SKILL.md - **Raw:** https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon-postgres/SKILL.md - **Markdown:** https://skillsdocs.com/neondatabase/agent-skills/neon-postgres.md - **Licence:** Apache-2.0 — https://spdx.org/licenses/Apache-2.0.html Bundled files (4), referenced from this skill's directory: - `references/full-text-search.md` — https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon-postgres/references/full-text-search.md - `references/hybrid-search.md` — https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon-postgres/references/hybrid-search.md - `references/lakebase-search-drizzle.md` — https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon-postgres/references/lakebase-search-drizzle.md - `references/vector-search.md` — https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon-postgres/references/vector-search.md --- name: neon-postgres description: >- Guides and best practices for working with Lakebase Postgres on Neon: connections, pooled vs direct, schema migrations, branching, autoscaling, scale-to-zero, instant restore, read replicas, IP allow lists, logical replication, and Lakebase Search. Use when the work is an existing DATABASE_URL, SQL, schema, inspect, or search. New backends, Auth, files, Functions, and LLM calls go to the parent `neon` skill. Also use for "@neondatabase/serverless", "@neondatabase/neon-js", "neon inspect db", "semantic search", "vector search", "full-text search", "BM25", or "hybrid search". metadata: parent: neon source: https://github.com/neondatabase/agent-skills/tree/main/skills/neon-postgres --- **FIRST**: Use the parent `neon` skill for a Neon overview, getting started with Neon, Neon development best practices, and more. If the `neon` skill is not installed, fetch it from https://neon.com/docs/ai/skills/neon/SKILL.md or install it with: ```bash neon skills -s neon -y ``` # Lakebase Postgres Lakebase Postgres is the database at the core of Neon. It runs on the lakebase architecture — OLTP built directly on cloud object storage — which decouples storage from compute to offer autoscaling, branching, instant restore, and scale-to-zero. It's fully compatible with Postgres and works with any language, framework, or ORM that supports Postgres. It is the same database whether you reach it through Neon or through Databricks; this skill covers the Neon access path. Login, users, sessions, and `@neondatabase/auth` belong in `neon-auth`. ## Setup Flow ### 1. Select the organization and project If a `DATABASE_URL` is already supplied (prompt, environment, or repo) or a `.neon` file points at a project, use it. Do not list organizations or create a second project for schema work. Otherwise use the CLI (default) or MCP server to list organizations and projects. Let the user select an existing project or create a new one. ### 2. Get the connection string If a `DATABASE_URL` is already supplied, use it. Do not fetch another through the CLI or MCP. Otherwise use the CLI (default), `neon env pull`, or the MCP server to get the connection string. Store it in `.env` as `DATABASE_URL`. Read the file first before modifying it, to avoid overwriting existing values. #### When to use pooled vs direct connections | Use case | Connection type | | ---------------------------------------- | ---------------- | | Web applications, serverless functions | Pooled (-pooler) | | Schema migrations | Direct | | pg_dump / pg_restore | Direct | | Logical replication | Direct | | Long-running analytics with temp tables | Direct | | Admin tasks needing SET or session state | Direct | | LISTEN / NOTIFY | Direct | ### 3. Pick the connection method and driver Preserve the existing ORM and driver. For new TypeScript schema work with no established choice, Drizzle is a suggestion: https://neon.com/docs/guides/drizzle.md. Refer to the connection methods guide to pick the correct driver based on how the runtime treats your code: https://neon.com/docs/connect/choose-connection.md. Driver notes: - On Vercel, use `node-postgres` (`npm install pg`) with Vercel Fluid compute and `import { attachDatabasePool } from "@vercel/functions";` - On Cloudflare, use `node-postgres` with Cloudflare Hyperdrive - On Neon Functions, use `node-postgres`, as the functions are long-running and reuse the pool across requests. - Use the `@neondatabase/serverless` driver for serverless and edge environments (for example, when using Netlify) — HTTP transport for one-shot queries, WebSocket for transaction support. Link: https://neon.com/docs/serverless/serverless-driver.md ### 4. Set up the schema Manage schemas and migrations as code. Avoid running ad hoc schema migrations against your database, since they're hard to manage. If you're using an ORM, follow your ORM's best practices to manage schemas and migrations. For example, if using Drizzle, only use Drizzle for schema and migration management unless instructed otherwise. ## Branching Use this when the user is planning isolated environments, schema migration testing, preview deployments, or branch lifecycle automation. Key points: - Branches are instant, copy-on-write clones (no full data copy). - Each branch has its own compute endpoint. - Use the neon CLI or MCP server to create, inspect, and compare branches. Link: https://neon.com/docs/introduction/branching.md For detailed branch creation workflows (normal vs schema-only branches, reset-from-parent, CLI/MCP selection), use the `neon-postgres-branches` skill. If it isn't installed, fetch it from https://neon.com/docs/ai/skills/neon-postgres-branches/SKILL.md or install it with: ```bash neon skills -s neon-postgres-branches -y ``` ## Migrations Test a migration on a branch of production, against production-like data, before applying it to production. Use a **direct (non-pooled)** connection string when you run the migration, not a pooled one. `neon connection-string` returns the direct string by default; make sure the hostname does not include the `-pooler` suffix. ## Troubleshooting and Neon-Specific Performance Use Neon's predefined, read-only diagnostics before writing catalog queries by hand. The Neon CLI `neon inspect db` subcommands and the Neon MCP server's `inspect_database` tool run the same checks. This section covers Neon-specific diagnostic tools, compute cache behavior, and platform signals. When the evidence points to generic Postgres work such as rewriting a query, choosing an index, changing a schema, or interpreting plan nodes, load the [`postgres-best-practices`](https://github.com/neondatabase/postgres-skills/tree/main/skills/postgres-best-practices) skill and carry the diagnostic evidence into that workflow. Docs: - CLI: https://neon.com/docs/cli/inspect.md - Query performance: https://neon.com/docs/postgresql/query-performance.md - `pg_stat_statements`: https://neon.com/docs/extensions/pg_stat_statements.md - Neon Local File Cache: https://neon.com/docs/extensions/neon.md ### Choose CLI or MCP Prefer the Neon CLI when terminal access and authentication are available: ```bash neon inspect db ``` The CLI resolves the project and branch from the current Neon context. Use `--project-id`, `--branch`, and `--database-name` to override it. Omit `--database-name` to inspect every database on the branch. Use `--db-url` only when inspecting a Postgres database directly instead of resolving it through the Neon API. When using Neon MCP, call `inspect_database` with `projectId` and one `check`. Pass `branchId`, `databaseName`, or `computeId` only when needed. Omit `databaseName` to inspect all databases on the branch. Increase `limit` only when the result says it was truncated. ### Pick the Diagnostic | Symptom or question | Checks | | ---------------------------------------------- | ------------------------------------ | | Which relations consume storage? | `table-sizes`, `index-sizes` | | Is an index unused or a table scanned heavily? | `unused-indexes`, `seq-scans` | | What has run for 5+ minutes or holds locks? | `long-running-queries`, `locks` | | Which queries consume the most total time? | `outliers` | | Which queries run most often? | `calls` | | Does the active data fit in compute cache? | `lfc-hit-rate`, `working-set` | | Is autovacuum behind or is space wasted? | `vacuum-stats`, `bloat` | | Is logical replication healthy? | `replication-slots`, `subscriptions` | Do not confuse these checks: - `long-running-queries` reports statements running **right now** for more than five minutes. - `outliers` ranks the top queries by cumulative execution time since statistics were reset. It does not rank by mean latency. - `calls` ranks by execution count over the same statistics history. `outliers` and `calls` require `pg_stat_statements`. `lfc-hit-rate` and `working-set` require the `neon` extension. If a check reports a missing extension, ask before running the suggested `CREATE EXTENSION` statement because installing an extension modifies the database. ### Interpret Results Safely - Treat `unused-indexes` as a candidate list, not permission to drop indexes. Confirm the observation window, constraints, and workload before removal. - A sequential scan can be correct for a small table or a query reading much of a table. Check table size, selectivity, and the query plan before adding an index. - `bloat` is a statistical estimate. Confirm the impact and plan locks or maintenance before `VACUUM FULL`, `REINDEX`, or similar remediation. - Cache and Postgres statistics reset when compute restarts, including scale-to-zero suspension. Run a representative workload before interpreting fresh `lfc-hit-rate`, `working-set`, `vacuum-stats`, or `pg_stat_statements` results. - Compute-wide checks (`lfc-hit-rate`, `working-set`, and `replication-slots`) run once even when inspecting every database. - One failing database can fail an all-databases inspection; retry the relevant check with an explicit `databaseName` to isolate it. ### Inspect Neon Cache Behavior Per Query Standard `EXPLAIN (ANALYZE, BUFFERS)` reports Postgres shared-buffer activity, but it does not show Neon's Local File Cache (LFC) or page prefetching. For a safe read-only query, add Neon's `FILECACHE` and `PREFETCH` options: ```sql EXPLAIN (ANALYZE, BUFFERS, PREFETCH, FILECACHE) SELECT ...; ``` - `File cache: hits` counts pages found in the compute's LFC. - `File cache: misses` counts pages not found in the LFC and fetched from database storage. - `Prefetch: hits`, `misses`, `expired`, and `duplicates` show how effectively Neon fetched pages before the executor requested them. `FILECACHE` and `PREFETCH` provide metrics for this query and do not require the `neon` extension. By contrast, `neon inspect db lfc-hit-rate` and `working-set` provide compute-wide statistics and do require the extension. The MCP `explain_sql_statement` tool can produce a standard plan but does not expose `FILECACHE` or `PREFETCH` options. To collect those Neon-specific metrics through MCP, use `run_sql` with the explicit, read-only `EXPLAIN` statement above. Because `ANALYZE` executes the statement, use it only when execution is safe; do not run it autonomously for mutating SQL. Compare cold- and warm-cache runs carefully because the first execution can populate the cache and materially change later results. ### Performance Workflow 1. Reproduce the symptom and note its time window. 2. Run the smallest relevant `inspect` checks from the table above. 3. Identify a specific query before changing schema or compute. Use MCP `explain_sql_statement` for a standard plan, or the Neon-specific `EXPLAIN` above when LFC or prefetch behavior matters. 4. If the bottleneck is query shape, indexing, schema, locking, or vacuum behavior, load `postgres-best-practices` and carry forward the inspection results and query plan. Keep Neon compute, cache, connection, and platform decisions in this skill. 5. Re-run the same check and workload to verify the change. Use MCP `list_slow_queries` instead of `inspect_database` when the user specifically needs queries ranked by average execution time with a custom threshold and limit. Outside the explicit `EXPLAIN` case above, use `run_sql` only for read-only diagnostic SQL when the predefined checks do not answer the question. ## Autoscaling Use this when the user needs compute to scale automatically with workload and wants guidance on CU sizing and runtime behavior. Link: https://neon.com/docs/introduction/autoscaling.md ## Scale to Zero Use this when optimizing idle costs and discussing suspend/resume behavior, including cold-start trade-offs. Key points: - Idle computes suspend automatically after a default of 5 minutes; the timeout is configurable, and suspension can only be disabled on the Launch and Scale plans. - First query after suspend typically has a cold-start penalty (around hundreds of ms) - Storage remains active while compute is suspended. Link: https://neon.com/docs/introduction/scale-to-zero.md ## Instant Restore Use this when the user needs point-in-time recovery or wants to restore data state without traditional backup restore workflows. Key points: - History windows for instant restore depend on plan limits. - Users can create branches from historical points-in-time. - Time Travel queries can be used for historical inspection workflows. Link: https://neon.com/docs/introduction/branch-restore.md ## Read Replicas Use this for read-heavy workloads where the user needs dedicated read-only compute without duplicating storage. Key points: - Replicas are read-only compute endpoints sharing the same storage. - Creation is fast and scaling is independent from primary compute. - Typical use cases: analytics, reporting, and read-heavy APIs. Link: https://neon.com/docs/introduction/read-replicas.md ## Connection Pooling Use this when the user is in serverless or high-concurrency environments and needs safe, scalable Postgres connection management. Key points: - Neon pooling uses PgBouncer. - Add `-pooler` to endpoint hostnames to use pooled connections. - Pooling is especially important in serverless runtimes with bursty concurrency. Link: https://neon.com/docs/connect/connection-pooling.md ## IP Allow Lists Use this when the user needs to restrict database access by trusted networks, IPs, or CIDR ranges. Link: https://neon.com/docs/introduction/ip-allow.md ## Logical Replication Use this when integrating CDC pipelines, external Postgres sync, or replication-based data movement. Key points: - Neon supports native logical replication workflows. - Useful for replicating to/from external Postgres systems. Link: https://neon.com/docs/guides/logical-replication-guide.md ## Lakebase Search Use Lakebase Search for semantic, full-text, and hybrid search: - For semantic search, read [Vector search](references/vector-search.md). - For full-text search with BM25 ranking, read [Full-text search](references/full-text-search.md). - For combining semantic and lexical results, read [Hybrid search](references/hybrid-search.md). - For managing any of the above through Drizzle ORM, read [Managing Lakebase Search with Drizzle](references/lakebase-search-drizzle.md). Links: - [Get started with Lakebase Search](https://neon.com/docs/ai/lakebase-search-get-started) - [`lakebase_vector` reference](https://neon.com/docs/extensions/lakebase-vector) - [`lakebase_text` reference](https://neon.com/docs/extensions/lakebase-text) ## Gotchas ### Pooled vs direct connections: use the direct URL for migrations, dumps, and replication Neon gives you two connection strings for the same database: a **pooled** one (hostname with the `-pooler` suffix) and a **direct/unpooled** one (no `-pooler` suffix). `neon env pull` writes them as `DATABASE_URL` and `DATABASE_URL_UNPOOLED`. The pooled connection routes through PgBouncer in transaction mode, which doesn't support session-level operations. Choose the right one: - **Pooled (`DATABASE_URL`)** — your application's normal query traffic, especially serverless and connection-per-request workloads. - **Direct (`DATABASE_URL_UNPOOLED`)** — schema migrations (Prisma Migrate, Drizzle Kit, Alembic, and others), `pg_dump` / `pg_restore`, logical replication, `LISTEN`/`NOTIFY`, and anything relying on `SET` or other session state. Running migrations, dumps, or replication over the pooled connection can fail, and never in a way that names pooling: `prepared statement "s0" already exists` from Prisma Migrate, a `SET search_path` that doesn't persist past its own transaction so the next query reports `relation "mytable" does not exist`, or a write intermittently hitting a read-only transaction (`SQLSTATE 25006`) that a pooled backend inherited from an earlier client. Migration tools generally take both strings at once — Prisma's `directUrl` alongside `url` — so point that at the direct one rather than swapping `DATABASE_URL` and losing pooling for the application. See https://neon.com/docs/connect/connection-pooling.md. --- ## 8. neon - **Source:** https://github.com/neondatabase/agent-skills/blob/main/skills/neon/SKILL.md - **Raw:** https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon/SKILL.md - **Markdown:** https://skillsdocs.com/neondatabase/agent-skills/neon.md - **Licence:** Apache-2.0 — https://spdx.org/licenses/Apache-2.0.html Bundled files (6), referenced from this skill's directory: - `references/auth.md` — https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon/references/auth.md - `references/claimable-neon.md` — https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon/references/claimable-neon.md - `references/function-triggers.md` — https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon/references/function-triggers.md - `references/logs-loki.md` — https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon/references/logs-loki.md - `references/parse-env.md` — https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon/references/parse-env.md - `references/sdk.md` — https://raw.githubusercontent.com/neondatabase/agent-skills/main/skills/neon/references/sdk.md --- name: neon description: >- Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, and the AI Gateway. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASE_URL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database. metadata: source: https://github.com/neondatabase/agent-skills/tree/main/skills/neon --- # Neon Neon is a complete set of cloud backend primitives around Lakebase Postgres, from Databricks — Lakebase Postgres, Auth (managed Better Auth), long-running Functions, Object Storage, and an AI Gateway, all instant, branchable, and serverless. **Lakebase Postgres** is the database itself. It is one product, reached two ways: through Neon, with a free plan and the full set of backend primitives above, or through Databricks, alongside the rest of the Databricks suite. Same infrastructure, same features, same engineering team. Call the database Lakebase Postgres, and use "Neon" for the brand and for this access path — not as a name for the database. A Neon branch is an isolated, copy-on-write clone of your data, taken from its current state or from a past state within your project's retained history window. You can freely modify or delete it. It shares data with its parent until writes cause it to diverge, and those writes are stored independently as deltas. Agents pick Neon for instant Postgres provision, copy-on-write branches and snapshots, compute that scales to zero (storage is still billed), and ordinary Postgres that works with any driver or ORM. ## Backend Primitives Neon bundles several backend primitives for building apps and agents that all branch together: - **Lakebase Postgres** — Postgres that scales and branches with your app, built on the lakebase architecture: OLTP directly on cloud object storage, with storage decoupled from compute. - **Auth** — Managed Better Auth with users and sessions stored in Postgres. - **Object Storage** — S3-compatible object storage that branches with your projects. - **Functions** — Neon's compute offering: long-running serverless functions that run close to your database, for WebSocket servers, long agent HTTP streams, APIs, and server-sent event servers. A Function Trigger POSTs to a function on a cron. - **AI Gateway** — One API for frontier and open-source models, supporting the chat completions API and the responses API, powered by Databricks Unity AI Gateway. - **Data API** — Optional PostgREST-compatible HTTP interface. Use it only when the app already uses PostgREST or a Supabase database client, or is migrating that client. New apps query Postgres from Functions or existing handlers. There is no `neon-data-api` skill; configuration is `dataApi` in `neon.ts` (see [Type-safe config](#type-safe-config-invalid-setups-dont-compile) when you have chosen it). ### Region availability Object Storage, Functions, and AI Gateway are currently available on projects in `aws-us-east-2`, `aws-us-east-1`, `aws-eu-central-1`, and `aws-ap-southeast-1`. Before guiding a user through any of these services, confirm they are working in one of these regions. If not, they will need to create a new project in a supported region. ## Architecture: How to Use Neon **Recommended: full-stack app with Neon as the backend.** Default to Next.js on Vercel (or Netlify, Cloudflare, or other app platforms). Prefer Next.js + Vercel first; TanStack Start, Nuxt, and SvelteKit are full-stack alternatives. The app owns its UI and server. Query Lakebase Postgres from route handlers, server functions, or Neon Functions. Add [Neon Functions](https://neon.com/docs/compute/functions/overview.md) as a backend layer between the web app and Lakebase Postgres, Object Storage, Auth, and AI Gateway. A Hono API on Functions can expose endpoints with an OpenAPI specification for the web app and other clients (mobile, desktop). You can also add a Function for one job next to the data: Object Storage uploads, AI agents, Discord bots, WebSocket or SSE servers. Functions support long-running requests that complement the web app. A Function must start returning a response within 15 minutes. WebSocket connections and HTTP streams stay open while data flows; send at least one byte every 15 minutes to keep a quiet stream alive. See [runtime limits](https://neon.com/docs/compute/functions/reference/runtime-limits.md). For long agent or image streams, mint a JWT on the app server and have the client call the Function directly. See the `neon-functions` skill for authentication and runtime limits. **Second best: client-only app with a Functions backend.** Host the SPA on Vercel (or Netlify, Cloudflare, or other app platforms) and call Functions from the browser. For an app using PostgREST or a `supabase-js` database client, prefer migrating database calls to REST endpoints in a Hono Function that queries Lakebase Postgres. Enforce authorization in the Function instead of relying on browser-facing RLS. Neon provides backend primitives that compose with the app host. Neon does not host the frontend. Offer the Data API only as a Supabase / PostgREST migration path when an existing PostgREST or `supabase-js` database client must keep working. Putting PostgREST in the browser and relying on RLS is easy to get wrong: misconfigured policies expose the database to the client. Do not recommend this for new apps. An installed Supabase package used only for Auth or Storage does not establish a database-client dependency. Route generic REST endpoint requests to a Function or existing app handler. Functions have public HTTPS URLs. Verify a JWT or API key at the top of the handler and enforce authorization before accessing data. See the `neon-functions` skill. ## Convert an app onto Neon Inspect the repo before provisioning. 1. Map requested capabilities: login, files, HTTP APIs, LLM calls, SQL. 2. Reuse what is already there: a supplied `DATABASE_URL`, an existing ORM or driver, Better Auth, Clerk or another auth provider, S3 or another object store, an existing `.neon` / `neon.ts`, an existing Data API or PostgREST client. 3. Select Neon primitives for capabilities that are still undecided. 4. Provision only when infrastructure is missing: `neon init` / `neon link` / Claimable, then `neon.ts`, then `neon deploy`. 5. Verify the app flow (sign-in, upload, API call), not only that env vars landed. Do not replace working Better Auth, Clerk, Supabase Auth, S3, or a supplied `DATABASE_URL` with a Neon primitive unless the user asks. Do not rewrite an existing `neon.ts`. If Neon credentials fail for an existing account, stop and ask the user to sign in; do not create a Claimable project as a substitute. A supplied `DATABASE_URL` with no Neon credentials is schema work: complete it without provisioning. Managed Better Auth cannot be enabled on a project that uses IP Allow or Private Networking. Leave those protections in place. New projects are created in AWS regions. Prefer pooled `DATABASE_URL` for application traffic. | Need | Use | | --- | --- | | Login, users, sessions (no existing provider) | `neon-auth` — Managed Better Auth (`auth: true`) | | Existing Better Auth, Clerk, Supabase Auth, or another working IdP | Keep it. `neon-auth` only if they ask to migrate | | User asked to migrate from Supabase Auth | `neon-auth` (Managed Better Auth; keep `SupabaseAuthAdapter()` call shapes) | | Files, uploads, blobs (no existing object store) | Object Storage | | HTTP APIs, cron, WebSocket, SSE, long-running agents | Functions querying Postgres | | LLM calls | AI Gateway | | SQL, schema, inspect, search | `neon-postgres` | | Existing PostgREST / Supabase database client | Data API (`dataApi` in `neon.ts`) | | Generic REST endpoints | Function or existing handler, not Data API | Use `neon-auth` to choose identity and to implement Managed Better Auth; the [Auth guide](references/auth.md) points there. Keep existing Better Auth, Clerk, and Supabase Auth unless the user asked to migrate login. Auth cannot be enabled on a project with IP Allow or Private Networking. ## Neon Documentation The Neon documentation is the source of truth for all Neon-related information. Always verify claims against the official docs before responding. Neon features and APIs evolve, so prefer fetching current docs over relying on training data. ### Finding the Right Page Look the page up before you fetch it — **don't guess URLs!** The docs index lists every available page with its URL and a short description: ``` https://neon.com/docs/llms.txt ``` ### Fetching Docs as Markdown Any Neon doc page can be fetched as markdown in two ways: 1. **Append `.md` to the URL** (simplest): https://neon.com/docs/introduction/branching.md 2. **Request `text/markdown`** on the standard URL: `curl -H "Accept: text/markdown" https://neon.com/docs/introduction/branching` Both return the same markdown content. Use whichever method your tools support. ## Choosing the Right Skill Neon provides a set of agent skills in addition to the official documentation. When a task matches one of the rows below, work from that skill rather than from this overview. You may have some of these skills already installed, or you may need to install them. The skills below live in the [`neondatabase/agent-skills`](https://github.com/neondatabase/agent-skills) repo: | Skill | Use it for | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `neon-postgres` | Working with databases, including connections, schemas, queries, search, and autoscaling: SQL development, schema design, performance optimization, and scaling decisions. | | `neon-auth` | Identity routing and Managed Better Auth setup (login, users, sessions, trusted domains). Fetch: https://neon.com/docs/ai/skills/neon-auth/SKILL.md | | `neon-postgres-branches` | Choosing or creating the right branch type for dev, preview, test, or CI workflows. Use this skill as a slash command. | | `neon-object-storage` | Storing and serving files (uploads, images, blobs), including branching them with the database. | | `neon-functions` | Deploying long-running or streaming serverless functions — APIs, agents, SSE/WebSocket servers, and Function Triggers (cron and object-storage). | | `neon-ai-gateway` | Calling an LLM or routing across model providers with one credential, including discovering the branch's servable models at runtime via the OpenAI-compatible `/v1/models` endpoint. | | `neon-postgres-egress-optimizer` | Diagnosing or fixing excessive Postgres egress (network data-transfer) costs in a codebase. | There is no `neon-data-api` skill. Configure `dataApi` in `neon.ts` only for PostgREST / Supabase database-client compatibility or a migration that already depends on it. For guidance on agent platforms that provision and operate Lakebase Postgres on Neon at scale, use `neon-postgres-agent-platforms`, which lives in a separate repo: [`neondatabase/neon-for-agent-platforms`](https://github.com/neondatabase/neon-for-agent-platforms). ### Installing the Right Skill First check whether the target skill is already installed and accessible (for example, it appears in the available skills list or its `SKILL.md` is present). If it is, use it directly. If it is not installed, install it with `neon skills`: ```bash neon skills -s ``` Replace `` with the skill you need (for example, `neon-object-storage`, `neon-functions`, or `neon-ai-gateway`). Useful flags: - `--global` — install globally instead of into the current project. - `-y` — non-interactive mode (skip prompts). - `--agent ` — pick the target agent(s) for non-interactive mode. For example, to install the object storage skill globally for a specific agent without prompts: ```bash neon skills -s neon-object-storage --global -y --agent ``` `neon-auth` is not in the CLI skill catalog of current releases. Unknown names fail, so do not run `neon skills -s neon-auth`. Fetch it: ``` https://neon.com/docs/ai/skills/neon-auth/SKILL.md ``` References: https://neon.com/docs/ai/skills/neon-auth/references/managed-auth.md and https://neon.com/docs/ai/skills/neon-auth/references/self-managed.md. If those URLs are unpublished, fetch the same files from https://github.com/neondatabase/agent-skills/blob/main/skills/neon-auth/SKILL.md If the Neon CLI is not available, you can visit https://neon.com/.well-known/agent-skills for a registry of all available Neon skills and fetch them manually. ### Updating Skills Keep the skills up to date: for every new session, update them so you are working with the latest best practices. Run `neon skills update` to update all installed Neon skills, or `neon skills update -y` to skip prompts. If the skills were installed via a plugin, they are updated automatically. ## Getting Started with Neon **Prefer the CLI over the MCP server** unless the user instructs otherwise, the CLI is unavailable or blocked in your environment, or it is not authenticated, since it provides more capabilities, including deploying Neon Functions. ### Check the CLI, then credentials ```bash neon --version ``` If that fails, install first: ```bash npm i -g neon # npm bun add -g neon # bun pnpm add -g neon # pnpm ``` For full CLI installation options, see https://neon.com/docs/cli/install.md Then inspect credentials without printing secrets. `NEON_API_KEY` or a `neon profile list -o json` row whose `account` is not `-` is an account. A `DEFAULT` row with `account: "-"` and `file: "missing"` is not. - Credentials already available: reuse them. Do not launch a browser. - A human needs to sign in: they run `neon login` (`neon auth` is an alias). An unattended agent must not launch browser authentication. - No account yet: follow [Starting without a Neon account](#starting-without-a-neon-account) for the Claimable Neon path. ### Combined setup: `neon init` When both agent tooling and project setup are needed, use authenticated `neon init`. `--agent` takes the coding-agent name. `-y` skips prompts but does not supply project selection or credentials. `--skip-template` skips scaffolding a starter app. Link an existing project: ```bash neon init --skip-template --agent cursor \ --org-id --project-id -y ``` Create and link a project: ```bash neon init --skip-template --agent cursor \ --org-id --project-name my-app \ --region-id aws-us-east-2 -y ``` `--services` may declare `auth`, `data-api`, `functions`, `object-storage`, and `ai-gateway` (repeat the flag or comma-separate). Pass `none` for the bare starter policy. It writes `neon.ts`; it does not deploy or wire the app. Selecting `data-api` also declares Auth (the default Data API provider requires it). Use `data-api` only for PostgREST / Supabase database-client compatibility. If `init` already installed the Neon plugin, do not also run `neon mcp` and `neon skills` for the same agent. When tooling already exists, only one component is missing, or env writes need `--no-env-pull`, use the manual steps below. `init` has no `--no-env-pull`. Before a command that pulls env, inspect existing configuration. If a supplied `DATABASE_URL` or `AWS_*` value must stay, pass `--no-env-pull` on `link` / `checkout` and write env to a separate `--file`. ### 1. Install the Neon CLI Use the install check above. Do not run `neon login` unattended. MCP remains the fallback when the CLI is unavailable, blocked, unauthenticated, or the user prefers it. ### 2. Install the Neon MCP Server ```bash neon mcp --oauth --project --agent cursor -y ``` `--oauth` writes the server URL and leaves sign-in to the MCP client. That is not an authenticated MCP session. `--project` means project-level agent config, not a Neon project ID; the agent must support project-level installs (`cursor` does). Bare `neon mcp -y` installs globally and can reuse or mint an account-wide API key — do not treat it as the unattended default. For all available plugins and IDE integrations, see: https://neon.com/docs/ai/ai-agents-tools.md For full MCP server installation options, see https://neon.com/docs/ai/connect-mcp-clients-to-neon.md ### 3. Install Neon Agent Skills ```bash neon skills -s neon --agent cursor -y ``` To install a specific skill only (not `neon-auth` until the CLI catalog includes it; fetch it as in [Installing the Right Skill](#installing-the-right-skill)): ```bash neon skills -s --agent cursor -y ``` Useful flags: `--global`, `-y`, `--agent `. Interactive `neon skills` with no flags prompts. ### 4. Link Your Project and Get Started With setup complete, connect the workspace to a Neon org, project, and branch. Then consult the skill for each Neon feature your app requires. See [Choosing the Right Skill](#choosing-the-right-skill) above. Non-interactive link: ```bash neon link --project-id -y neon link --org-id --project-name my-app --region-id aws-us-east-2 ``` `-y` skips the already-linked confirmation and pins the default branch when the project has more than one. Pass `--branch ` when branch selection matters. #### Useful CLI Commands 1. `neon link` — Writes org, project, and branch IDs to a git-ignored `.neon` file. Run once per project. Once linked, project- and branch-scoped commands no longer need `--project-id` or `--branch` (for example, `neon branch list`). Non-interactive: `--org-id` / `--project-id` / `--project-name` plus `--region-id`, and `-y` when appropriate. There is no `neon link --agent`. 2. `neon checkout ` — Pins a branch in `.neon` and pulls that branch's env. An existing branch is enough. A missing **name** needs `--create` for unattended use (`neon checkout dev --create`). A missing branch **id** cannot be created. Interactive checkout with no name may offer to create; do not rely on that unattended. Drives the [Branch-First Dev Flow](#branch-first-dev-flow) below. 3. `neon config init` — Initializes a `neon.ts` file, which declares how you provision and manage Neon services, in the root of the project. 4. `neon env pull` — Fetches the current branch's Neon environment variables (`DATABASE_URL`, …) into your existing `.env`, or `.env.local` if you don't have one (override the target with `--file`). No branch ID needed; it reads `.neon`. **`link` and `checkout` run this for you by default**, so you rarely call it directly. Without `neon.ts`, a **bare** `neon env pull` includes the default Gateway credential on claimed projects. Implicit pulls bundled into `link` / `checkout` / `apply` do **not** pull an undeclared Gateway token. Declaring `aiGateway` in `neon.ts` requests those variables. With `neon.ts`, pull includes only the services declared there and errors if the branch is missing one. ### Bootstrap a New Project `neon bootstrap` scaffolds from a Neon project template. ```bash neon bootstrap ``` ## Starting without a Neon account If the Getting Started account check found credentials, use them. If a command waits on a browser (`Awaiting authentication in web browser`) or authentication fails, stop and ask the user to sign in (`neon auth`) or mint an API key. Do not create a Claimable project as a substitute for a failed existing account. If there is no Neon account yet, follow [references/claimable-neon.md](https://neon.com/docs/ai/skills/neon/references/claimable-neon.md). Do not run `neon init --agent` or `neon auth` on this path; those need a human Neon account. If `neon claim` is missing, the reference has the REST fallback. Unclaimed projects expire at `project_expires_at` (72 hours today). Claim codes expire in `expires_in` (15 minutes today). Functions, Object Storage, and AI Gateway report `requires_claim` before a human claims the project; report that and keep the denied capabilities. Add Auth with `neon.ts` and `neon deploy` when login is requested and no existing provider should be preserved. Add the Data API only for PostgREST / Supabase database-client compatibility or a migration that already depends on it. Requests for neon.new, Claimable Postgres, claimable.neon.tech, instant Postgres, or a no-signup database are the same path. ## Neon Infrastructure as Code `neon.ts` is Neon's branch config and infrastructure-as-code file: declare which Neon services your project's branches should have, get type-safe env vars, and program branch settings — all in TypeScript. It's the config layer for your Neon services, and it composes with the branch-first loop below. Add it with `@neon/config`: ```bash npm i @neon/config ``` ```typescript // neon.ts import { defineConfig } from "@neon/config/v1"; export default defineConfig({ aiGateway: true, buckets: { images: { access: "private", }, }, functions: { imagegen: { name: "AI SDK image agent", source: "src/index.ts", }, }, }); ``` ### Provision services with neon config Every project ships with Lakebase Postgres; `neon.ts` also declares Auth, Functions, buckets, and the AI Gateway. Data API is a compatibility toggle, not part of a default backend: ```typescript // neon.ts export default defineConfig({ auth: true, functions: {}, buckets: {}, aiGateway: true, // see the neon-ai-gateway skill }); ``` Empty `functions` / `buckets` maps are configuration slots, not a deployed API. Do not replace an existing `neon.ts` wholesale with this example. Reconcile the declaration from the CLI — the Neon equivalent of `terraform status` / `plan` / `apply`: ```bash neon status # print the branch's live config (read-only). Alias for `neon config status`. neon config plan # dry-run diff of what apply would change (read-only) neon deploy --env # apply neon.ts. Pass --env when Function env reads process.env. Alias for `neon config apply` ``` `apply` / `deploy` provision the declared services **and then pull the branch's env into your local `.env.local`** (e.g. `Pulled 5 Neon variables into .env.local: DATABASE_URL, …`), so your local env always matches what's deployed. ### Function env and `neon deploy` `neon deploy` is the preferred full deployment: it applies `neon.ts` (services and functions) to the linked branch. `neon deploy --env ` loads that file into `process.env` before evaluating `neon.ts`, then uploads those values as Function env. Use it every time Function env reads `process.env`. `` is the gitignored file `neon env pull` already writes (`.env` if that file exists, otherwise `.env.local`). Env pull writes Neon-managed vars only (`DATABASE_URL`, `NEON_AI_GATEWAY_*`, …). Add every key under `functions.*.env` to that file yourself, then pass the same path to `--env`. Every declared Function env key must be a defined string. `undefined` (an unset `process.env.X`) means you listed a key you want written but the value is missing: `defineConfig` throws. Omit the key from `neon.ts` if you do not want to write it. Never coerce a missing `process.env` value to an empty string: that uploads `""` and deletes the live key. An empty assignment in the file (`KEY=`) is also `""`. If TypeScript needs a type assertion, use `process.env.X!` and make sure the file actually has the value. Use `neon functions deploy` when you are not applying `neon.ts`: a single function by slug, or a targeted `--env KEY=VALUE` update (that flag is not a file path). ### Function Triggers A Function Trigger POSTs to a Neon Function on a cron (`type: "schedule"`) or when an object is created in a bucket (`type: "storage_object_created"`). Same regions as Functions. Prefer a `triggers` map in `neon.ts` (the record key is the trigger name) and `neon deploy`. CLI, MCP, REST, inherited-trigger behavior, and parsers: [references/function-triggers.md](https://neon.com/docs/ai/skills/neon/references/function-triggers.md). Handler payload and Hono example: the `neon-functions` skill, `references/function-triggers.md`. ### Type-safe env vars with parseEnv `@neon/env`'s `parseEnv` returns a typed env object from your `neon.ts` config. Require a subset of keys when an app does not need every implied variable: [references/parse-env.md](https://neon.com/docs/ai/skills/neon/references/parse-env.md). ### Branch configuration Beyond services, `neon.ts` can program what configuration _new_ branches receive via the `branch` property — a function of the branch being evaluated that returns its settings: ```typescript // neon.ts import { defineConfig } from "@neon/config/v1"; export default defineConfig({ auth: true, branch: (branch) => { if (branch.exists) { // leave existing branches untouched return {}; } if (branch.name.startsWith("dev")) { return { ttl: "7d", // clean up the branch after 7 days postgres: { computeSettings: { autoscalingLimitMinCu: 0.25, // scale to zero autoscalingLimitMaxCu: 1, // keep it cheap suspendTimeout: "5m", }, }, }; } return {}; }, }); ``` The `branch` function receives the target branch (its `name`, whether it `exists` yet, whether it's the default, and more) and returns the tuning you want. Here new `dev-*` branches get a 7-day TTL so they clean themselves up, plus a cheap scale-to-zero compute profile, while existing branches and everything else fall through to the defaults. Because `neon checkout` applies this policy on create, a fresh `dev-*` branch comes up with these settings already in place. ### Type-safe config: invalid setups don't compile Because `neon.ts` is TypeScript, the compiler catches invalid infrastructure before you ever deploy — and Neon encodes the actual rules (and their fixes) into the types, so the error tells you what to do rather than failing with a useless `Type 'true' is not assignable to type 'never'`. The canonical case, **when the app has chosen Data API for PostgREST/Supabase compatibility**: the Data API verifies requests with Neon Auth by default, so enabling it on its own is a type error _on_ `dataApi`. Do not enable Auth merely to satisfy this error in an app that never needed Data API. ```typescript export default defineConfig({ dataApi: true, // type error: `dataApi` (default authProvider 'neon') requires Neon Auth }); ``` The message names both fixes, so pick one: ```typescript // 1. Enable Neon Auth (the default Data API auth provider): export default defineConfig({ auth: true, dataApi: true }); // 2. Or verify a third-party IdP instead of Neon Auth: export default defineConfig({ dataApi: { authProvider: "external", jwksUrl: "https://your-idp/.well-known/jwks.json", }, }); ``` Treat a `neon.ts` type error as the config telling you which services must go together — read the message, it spells out the valid combinations. See https://neon.com/docs/reference/neon-ts.md for documentation on the `neon.ts` file. ## Branch-First Dev Flow Neon branches enable a branch-first development flow, which we recommend when using Neon services. This and `neon.ts` above are the two halves of the recommended setup — `neon.ts` declares what every branch should have, and the branch-first loop is how you move between those branches day to day. Each works on its own, and they compose. Create a Neon branch any time you would create a git branch. Use the following commands if you have CLI access: - `neon checkout ` — Pins an existing branch by updating only the branch pointer in `.neon`. Pass `--create` to create a missing **name** (`neon checkout dev --create`). Run without a name for an interactive picker. It does not touch code or local Postgres. - `neon env pull` — Fetches the current branch's Neon environment variables into your `.env`. **`link` and `checkout` run this for you by default**, so you rarely call it directly. - `neon diff` — Shows the schema diff between the child branch and its parent. Run this to see what changes have been made to the schema since the last branch was created and before you commit your changes. ```bash neon link # once; also pulls the linked branch's env neon checkout dev-add-search --create # per feature; also pulls the branch's env ``` Because `link` and `checkout` pull env by default, the branch's `DATABASE_URL` lands in your local `.env` automatically — build against it, then `checkout` the next branch and repeat. As the agent, drive this loop yourself: run `checkout` between tasks. ### How checkout composes with neon.ts When a `neon.ts` is present, `neon checkout --create` applies your policy as it **creates** a branch, so a fresh branch comes up with its declared settings and services already in place. Pass `--env ` on that create so Function env that reads `process.env` resolves (`neon checkout feat --create --env .env.local`). Existing process env wins over the file. Checking out an _existing_ branch never reconciles it — apply config changes to it explicitly with `neon deploy --env ` (alias for `neon config apply`). `--update-existing` auto-confirms overriding remote settings; add it only after reviewing those changes. The bundled `env pull` also checks `neon.ts` against the linked branch and fails fast if the branch is missing a declared service, pointing you at `neon deploy --env ` to provision it, so your local env and the remote branch never drift apart silently. ### Opting out of local env vars If env vars are injected at runtime instead of written to disk — or you simply don't want secrets in the working tree — pass `--no-env-pull` to `link` / `checkout` and supply the env another way: - `neon-env run -- ` (from `@neon/env`) injects the branch's vars at runtime. - `neon-env export` prints dotenv or `--format json`. - `fetchEnv` from `@neon/env` is the programmatic version. - `neon dev` injects the same vars into the local Functions dev server. When an agent should not write a local `.env`, instruct it (for example in your `AGENTS.md`) to run `neon checkout --no-env-pull` and rely on runtime injection. For reading env you _already_ have on disk (typed and validated against your `neon.ts`), use `parseEnv` — see [Type-safe env vars with parseEnv](https://neon.com/docs/ai/skills/neon/references/parse-env.md). ## Observability Neon exposes branch-scoped logs for Functions and Object Storage today (`aws-us-east-2`, `aws-us-east-1`, `aws-eu-central-1`, and `aws-ap-southeast-1`). Query the branch that hosts the deployed function or bucket, not the checkout used for development. ```bash neon logs query --since 1h neon logs query --branch production --source function --minimum-severity error --since 6h ``` CLI flags, LogQL, MCP fallback, Loki HTTP, Grafana URLs, and `@neon/sdk` pagination: [references/logs-loki.md](https://neon.com/docs/ai/skills/neon/references/logs-loki.md). ## Manage Neon Resources Use [`@neon/sdk`](https://neon.com/docs/ai/skills/neon/references/sdk.md) to manage projects, branches, and snapshots from TypeScript. New code should prefer it over `@neondatabase/api-client`. ### Neon for (Agentic) Platforms Enroll in the [Neon Agent Program](https://neon.com/programs/agents.md) only when the work is a fleet of user databases (app-generating agents and platforms). A single-app backend skips this. Instant provision, snapshots, scale-to-zero compute (storage still billed), Auth, and Data API compatibility details: that page. --- ## Part: Credited skills --- ## 9. score-eval - **Source:** https://github.com/neondatabase/agent-skills/blob/main/evals/neon-postgres-egress-optimizer/.claude/skills/score-eval/SKILL.md - **Raw:** https://raw.githubusercontent.com/neondatabase/agent-skills/main/evals/neon-postgres-egress-optimizer/.claude/skills/score-eval/SKILL.md - **Markdown:** https://skillsdocs.com/neondatabase/agent-skills/score-eval.md - **Origin:** Credited — installed into this repository, not published from it. - **Licence:** Apache-2.0 — https://spdx.org/licenses/Apache-2.0.html --- name: score-eval disable-model-invocation: true --- Score the eval diff at $ARGUMENTS against the eval rubric. 1. Read the diff file at the path provided 2. Read the eval rubric at eval-rubric.md 3. Read the original fixture app in fixtures/hono-drizzle-app/ for comparison 4. For each problem P1-P5, answer the Detected? and Fixed? questions from the rubric as yes or no 5. Append a row to results.csv — fill in all fields you can determine from the diff and context. Leave fields you can't determine empty.