> Full Neon documentation index: https://neon.com/docs/llms.txt
> IMPORTANT: If this page contains inaccurate or outdated information, report it: POST to https://neon.com/api/docs-feedback with {"feedback": "describe the issue", "path": "/changelog/2026-04-17"}

# Neon Postgres plugin for OpenAI Codex, snapshot API size fields, Singapore region networking, and more

## Neon plugin for OpenAI Codex

The **Neon Postgres** plugin is officially available in the [OpenAI Codex](https://developers.openai.com/codex/) plugin directory. It adds the **Neon MCP Server** and Neon-focused **Agent Skills** to Codex, so you can create and manage Neon projects, branches, and databases from chat, run SQL and migrations, and get guided help on connections, branching, autoscaling, Neon Auth, and more.

### Install the plugin

**Codex CLI:** If you do not have the CLI yet, install it and start `codex`:

**npm**

```bash filename="Terminal"
npm install -g @openai/codex
codex
```

**Homebrew**

```bash filename="Terminal"
brew install --cask codex
codex
```

Then in Codex run `/plugins`, find **Neon Postgres**, and choose **Install plugin**. Complete any Neon sign-in or connection prompts.

For **Codex app** instructions, more detail on what's bundled, and example prompts, see **[Codex plugin for Neon](https://neon.com/docs/ai/ai-codex-plugin)**. For an overview, see the **[Neon blog](https://neon.com/blog/neon-codex-plugin)**.

## Snapshot API responses include storage size fields

The `snapshot` object in the Neon API now supports `full_size` and `diff_size` fields for monitoring snapshot storage.

- **Manual** snapshots expose `full_size`: the full logical size at the time of the snapshot.
- **Scheduled** snapshots: the **first** scheduled snapshot reports the full logical size via `full_size`. **Subsequent snapshots** report a `diff_size` value, which is the storage since the previous scheduled snapshot.

```json {9}
{
  "snapshots": [
    {
      "id": "snap-twilight-boat-an3a2yx2",
      "name": "production at 2026-04-17 09:57:07 UTC (manual)",
      "source_branch_id": "br-gentle-leaf-anax5tl3",
      "created_at": "2026-04-17T09:57:09Z",
      "manual": true,
      "full_size": 30965760
    }
  ]
}
```

The fields are supported on **`snapshot`** objects in responses from:

- [Create snapshot](https://api-docs.neon.tech/reference/createsnapshot)
- [List snapshots](https://api-docs.neon.tech/reference/listsnapshots)
- [Update snapshot](https://api-docs.neon.tech/reference/updatesnapshot)

For more on these fields (when each is present, omitted, or zero, and how that relates to charging and incremental billing), see [Snapshot size fields in API responses](https://neon.com/docs/guides/backup-restore#snapshot-size-fields-in-api-responses) in [Backup & restore](https://neon.com/docs/guides/backup-restore).

**Note: Snapshot billing reminder**

Snapshot storage billing starts **May 1, 2026**. For more information, see [Backup & restore](https://neon.com/docs/guides/backup-restore).

## New NAT gateway IPs and VPC endpoint services in Asia Pacific (Singapore)

We've expanded infrastructure capacity in the AWS Asia Pacific (Singapore) region (`ap-southeast-1`) with new NAT gateway IP addresses and new VPC endpoint service addresses for Private Networking.

**Tip: Update your IP allowlists**

If you have IP allowlists on external systems that Neon connects to, **update those allowlists to include the new NAT gateway addresses**. Connections may be affected intermittently if traffic routes through non-allowlisted NAT gateways.

If you use Private Networking in `ap-southeast-1`, you can now use the additional VPC endpoint service addresses for enhanced capacity and reliability. See the [Regions documentation](https://neon.com/docs/introduction/regions#aws-nat-gateway-ip-addresses) for the complete list of NAT gateway IPs and the [Private Networking guide](https://neon.com/docs/guides/neon-private-networking) for VPC endpoint service addresses by region.

<details>

<summary>**Organizations**</summary>

Fixed an issue where **approaching maximum storage** notification emails for organization-owned projects were sent to every organization Member. These emails are now sent to organization Admins only. See [Notes and limitations](https://neon.com/docs/manage/user-permissions#notes-and-limitations) in the User permissions documentation for how this fits with Admin and Member roles.

</details>

<details>

<summary>**Backup & restore**</summary>

Fixed an issue where finalizing a **snapshot restore** could leave **both** the previous branch and the restored branch marked as **protected**, which inflated protected-branch counts toward your plan limit. Finalizing the restore now **moves** the protected setting to the branch that holds the restored data. See **[Backup & restore](https://neon.com/docs/guides/backup-restore#multi-step-restore)** (finalize step).

</details>

<details>

<summary>**Compute updates**</summary>

**Scheduled compute updates:** Computes whose **maximum** autoscale size is **8 CU** now receive scheduled updates. **Previously**, computes with a **maximum** autoscale size of **8 CU** were treated like **large computes** and did not receive scheduled updates automatically. Computes whose **maximum** is **greater than 8 CU** still follow the [large compute](https://neon.com/docs/manage/updates#updating-large-computes) rules and need a manual restart. See **[Updates](https://neon.com/docs/manage/updates)**.

</details>