Changelog

Agent Runners now include a frontend-design skill that guides AI agents toward creating distinctive, production-grade frontend interfaces with high design quality.

When building web components, pages, or applications, AI agents often default to generic, cookie-cutter aesthetics. The frontend-design skill steers agents toward creative, polished output that avoids that “AI slop” look and instead produces UIs with real visual identity and craft.

Here’s what a generated calculator component looks like without the skill:

And here’s the same prompt with the frontend-design skill enabled:

The skill is automatically available in Agent Runners and activates when the agent is asked to build web components, pages, or applications. No configuration required—just prompt your agent to build a UI and the skill handles the rest.

Learn more about Agent Runners and available skills in the Netlify docs.

Anthropic’s Claude Opus 4.7 model is now available through Netlify’s AI Gateway and Agent Runners with zero configuration required.

Use the Anthropic SDK directly in your Netlify Functions without managing API keys or authentication. The AI Gateway handles everything automatically. Here’s an example using the Claude Opus 4.7 model:

import Anthropic from '@anthropic-ai/sdk';

export default async () => {
    const anthropic = new Anthropic();

    const response = await anthropic.messages.create({
        model: 'claude-opus-4-7',
        max_tokens: 4096,
        messages: [
            {
                role: 'user',
                content: 'How can AI improve my coding?'
            }
        ]
    });

    return new Response(JSON.stringify(response), {
        headers: { 'Content-Type': 'application/json' }
    });
};

Claude Opus 4.7 is available for all Function types and Agent Runners. You get automatic access to Netlify’s caching, rate limiting, and authentication infrastructure.

Learn more in the AI Gateway documentation and Agent Runners documentation.

We’re introducing some pricing updates to our Credit-based plans. Here’s a quick summary of the changes, explained more below.

• Unlimited seats on the Pro plan
• Unlimited form submissions on all Credit plans
• Updated credit rates for bandwidth, compute, and web requests

To understand more on why we’re making these changes, check out our official Netlify blog post on Pricing Netlify for the next 3 billion builders.

Not sure if your plan is impacted? Check out our Impact summary based on plan table.

Read on for concise details and impact timelines.

Unlimited seats on the Pro plan

The Credit Pro plan now includes free unlimited team member seats with a monthly subscription. This means you can invite anyone you like to join your team for the monthly subscription of $20 for 3,000 credits to use across your team’s projects.

Invite or add Owners, Developers, Internal Builders, Publishers, Git Contributors, and Reviewers to your team without extra seat charges. Before you were charged $20 per seat, including for active Git Contributors.

This change applies to Pro plans using credits metered billing only. Legacy Pro plans are not affected. Learn more about how different plans are affected in our impact by plan summary table.

Impact timeline

These seat plan changes apply right away to new upgrades and plans.

For existing teams with a Credit Pro plan, your seat charges will be removed for existing seats at the start of your next billing cycle. In the meantime, you can invite more people to join and collaborate without seat charges starting today.

Unlimited form submissions

Now form submissions are free across all Credit plans. Previously, each form submission cost 1 credit.

Impact timeline

For existing teams with a Credit plan, you’ll notice form submission cost changes take effect starting today.

Updated metered billing

As part of this pricing shift, we’ve also updated how credits are calculated for certain resources. These updates still keep our services competitive.

Impact timeline

For existing teams with a Credit plan, you’ll notice the metered billing changes take effect starting today.

Impact summary based on plan

Not sure how these pricing updates impact you and your plan?

Check out our impact summary table below for a quick overview.

Learn more

Learn more about Credit-based pricing plans and how credits work.

Managing team members just got easier. The Members page now includes sorting and filter controls that help you quickly find and organize your team, available for Pro and above plans.

You can now search for team members by name, filter by role, filter by project access, sort by last activity, and more — making it simple to audit access, find specific collaborators, or review who’s been active recently. These controls are especially useful as your team grows and you need more visibility into membership and permissions.

These controls are available now for all teams on Pro plans and above. Head to your team’s Members page to try them out.

The GA version of Netlify DB launches the week of April 20, 2026, bringing many significant improvements and it won’t require installing an extension anymore.

The move from the beta experience to the GA database experience is not automatic, and is not required. We will publish detailed instructions for anyone wishing to migrate. There will be no required switch or migration, no loss of data, and no sudden charges for anyone using an already-created database with the beta experience.

Starting today, April 13, 2026, you cannot create new databases using the beta Netlify DB experience. You can still claim existing databases to your own Neon account.

If you created a database in the past week, recall from the Netlify DB beta docs that you must claim your database within 7 days through your own Neon account or the the database will be automatically deleted. Learn more in our docs on claiming your database.

A denial-of-service (DoS) vulnerability (CVE-2026-23869, CVSS 7.5) has been disclosed affecting React Server Components (RSCs), a feature used by Next.js and other React metaframeworks. A malicious payload can cause excessive CPU consumption. Here’s what Netlify customers need to know.

Impact on Netlify

Nominally, this is a server-side DoS vulnerability. However, on Netlify this has minimal impact: our autoscaling serverless architecture means that a malicious request resulting in a crashed or hung function does not affect other requests. However, active exploitation could increase your function costs.

Affected frameworks

All RSC frameworks are affected:

• Next.js (see version table below)
• React Router 7 (if using RSC preview)
• Waku
• @parcel/rsc
• @vitejs/plugin-rsc

Astro, Gatsby, and Remix are not affected.

React affected versions

See the React advisory for full details.

Next.js affected versions

See the Next.js advisory for full details.

What should I do?

If any of your projects are using an affected version, we recommend upgrading as soon as possible to a patched release.

For Next.js 13.x and 14.x users: patches are not planned for these versions. Consider upgrading to Next.js 15.x or 16.x.

Note that any publicly available deploy previews and branch deploys may remain vulnerable until they are automatically deleted. Consider deleting these deploys manually.

Resources

• React CVE-2026-23869
• React security advisory
• Next.js security advisory

Watching a deploy? You’ll notice logs now appear faster and more smoothly in the Netlify UI. We’ve reduced log delivery latency and decreased the size of the batches sent to the browser, so output streams in closer to real time.

This means less waiting and fewer large chunks of text appearing all at once. Instead, logs flow steadily as your build progresses — making it easier to follow what’s happening and catch issues early.

Deploy logs are available on the detail page of every deploy and show build image details, dependency caching, all standard output from your build, Build Plugin execution, and the final deploy status. For successful deploys, highlights are automatically included in the deploy summary.

You can also share specific log lines with your team — select a line number to highlight it, or shift+click a range to generate a shareable URL. Select the clipboard icon to copy the entire log.

For more details, check out the deploy log documentation.

No changes are required on your end. The improvement applies automatically to all deploy logs viewed on app.netlify.com.

You can now deploy sites to Netlify directly from OpenAI Codex using the Netlify plugin in the Codex plugin directory.

Codex plugins extend Codex with apps, skills, and MCP servers, to access external tools, data, and workflows directly from your coding environment. With the Netlify plugin, Codex can create projects, configure settings, and deploy without leaving the coding workflow.

What you can do

Deploy directly from Codex

• Deploy projects using the Netlify CLI workflow
• Generate preview URLs automatically
• Deploy to production when ready
• Validate build configuration before deployment

Manage your projects

• Create new projects
• Install extensions
• Manage environment variables
• Configure visitor access controls
• Manage forms
• Update project settings

Review and fix deployments

• Inspect deploy status
• Retrieve build logs
• Identify configuration issues
• Iterate on fixes within Codex

Codex is also available through Agent Runners, where you can prompt AI agents against your live project and deploy changes directly from the Netlify Dashboard.

The Netlify plugin for Codex is available now in the Codex plugin directory.

Shopify’s Hydrogen framework now works on Netlify with React Router 7 and Hydrogen 2026.1.0. The Netlify Hydrogen template has been fully rebuilt, and @netlify/vite-plugin-react-router now supports Hydrogen sites out of the box.

The updated template also comes with two meaningful improvements:

• Netlify Cache API integration — Data fetching is cached using the Netlify Cache API, giving you low-latency responses without extra configuration.
• Full local platform emulation — The Netlify Vite Plugin provides zero-config local emulation of Blobs, Functions, Edge Functions, and AI Gateway during development, so what you test locally matches what runs in production.

To get started with a new Hydrogen site on Netlify, deploy the updated template:

To move an existing Hydrogen site over to Netlify, follow the How to deploy a Shopify Hydrogen storefront to Netlify guide.

Learn more:

• Hydrogen template on GitHub
• @netlify/vite-plugin-react-router v3.1.0 release notes
• How to deploy a Shopify Hydrogen storefront to Netlify