Changelog

Build and ship web apps faster with AI and Netlify. Start with a prompt, use production infrastructure, and grow without rebuilding.

To help you and your agents build more effectively, we’re introducing reusable Prompt Templates available directly from within Netlify.

Browse a curated collection of reusable prompts for common Netlify workflows: accessibility audits, A/B testing with Edge Functions, and more. Each template uses variable placeholders so you can adapt it to your project without starting from scratch.

Prompt Templates live directly in your project’s agent runs dashboard. From there you can:

• Browse public prompt templates
• Customize and save your own versions of any template for your team
• Submit templates back to the community to share what is working for you

Learn more about managing Prompt Templates for your team.

OpenAI’s GPT-5.4 Nano and GPT-5.4 Mini models are now available through Netlify’s AI Gateway with zero configuration required.

Use the OpenAI SDK directly in your Netlify Functions without managing API keys or authentication. The AI Gateway handles everything automatically. Here’s an example using the GPT-5.4 Nano model:

import OpenAI from 'openai';

export default async () => {
    const openai = new OpenAI();

    const response = await openai.responses.create({
        model: 'gpt-5.4-nano',
        input: 'Give a concise explanation of how AI works.',
    });

    return Response.json(response);
};

GPT-5.4 Nano and GPT-5.4 Mini are available for all Function types. You get automatic access to Netlify’s caching, rate limiting, and authentication infrastructure.

Learn more in the AI Gateway documentation

We’ve updated how you manage who can access what on your Netlify project and created a new role designed for the workflow needs of cross-functional AI-assisted builders.

Teams have asked for clearer ways to support people building internal tools and people collaborating on existing projects with AI agents and some guardrails.

With the new Internal Builder role and more granular project access control, Netlify now better supports new ways of working with AI across your cross-functional teams.

Introducing the Internal Builder role

This role is ideal for marketers building campaign pages, HR teams spinning up internal sites, or anyone using AI tools to ship without a traditional dev workflow.

The Internal Builder role is built to cover these two use cases:

• Build with Agent Runners with guardrails for existing projects
• Support internal tool builders with their new projects

Build with Agent Runners with guardrails

Internal Builders can use Agent Runners to build and iterate on web projects with guardrails that support the ways cross-functional teams work.

The Internal Builder role can iterate on existing web projects using Agent Runners but cannot publish directly to production or access Project configuration settings, such as to change environment variables. This ensures the Internal Builder doesn’t accidentally break existing functionality.

For projects connected to a Git provider, the Internal Builder can open a pull request for review from their agent run. This allows Developers and Owners to decide when to go live with changes.

Use cases supported:

• Marketing team member who needs to build campaign landing pages quickly with stakeholder review
• Designer who iterates on pricing page with AI assistance with stakeholder review

Support internal tool builders

Once someone with an Internal Builder role creates a project, they automatically get a Developer role on that project without changing their role and access permissions to other projects.

This allows your cross-functional teams to own the building process for their internal tools.

Use cases supported:

• HR team member who wants to build an information site for a company trip to Mexico
• Sales rep building internal tools for their team

New granular project access

We’ve upgraded the ways you can manage project access for your team members.

Team Owners can specify project access when adding team members to projects or when they edit existing project access.

They can assign a role scoped only to specific projects or to all projects (including future ones).

This means the same person can be an Internal Builder on most projects but a Developer on the internal tool they’ve created. Access can be scoped to exactly what each person needs.

For more details, check out our docs on Roles and permissions and Manage project access.

Try it out

To add an Internal Builder to your team, go to your team’s Members page and invite a new member or update an existing member’s role. Let us know if you have any feedback.

We’ve updated how credits are displayed across the Netlify UI. Instead of showing a “used credits / total credits” counter, you’ll now see your available credits — the number of credits you actually have left to use.

Now, you’ll see exactly how many credits remain on your account without needing to do the math yourself. For a detailed breakdown of your monthly credit consumption, check the Credit usage breakdown card on your team’s billing page.

Learn more about how credits work.

Astro 6 is out today, and it just works on Netlify on day one. To upgrade, run:

npx @astrojs/upgrade

This will update Astro, the Netlify adapter, and all other official integrations together.

What’s new

Some highlights include:

• Vite 7 and a redesigned dev server — Faster builds and a better dev server built from the ground up.
• Content Layer API — Legacy content collections are fully removed. All collections must now use the Content Layer API.
• Node 22 — Node 18 and 20 are no longer supported.

Check the full upgrade guide for all the details.

Watch out for import.meta.env

One change worth calling out: import.meta.env values are now always inlined at build time in Astro 6. This means if you were relying on import.meta.env to read environment variables at runtime in your server-side code, those values will be baked into your build output instead.

To read environment variables at runtime, use process.env instead:

- const apiKey = import.meta.env.API_KEY;
+ const apiKey = process.env.API_KEY;

This is especially important for secrets. If a secret is inlined into your server bundle, it’s no longer secret. The good news: Netlify’s smart secret scanning will automatically detect exposed secrets in your build output and fail the build before it goes live, so you’ll know right away if something slipped through.

Deploy an Astro 6 site on Netlify

If you want to get started with a new site, start with the Astro on Netlify doc, or just click this button:

Team Owners can now set a credit limit on AI inference usage to keep Agent Runners and AI Gateway costs within budget.

When your team’s usage hits the credit cap you define, active agent runs stop, new agent runs are blocked, and continued AI Gateway usage is paused to help you keep more of your credit balance.

This is especially useful for teams actively using AI features who want predictable monthly costs without manually watching the meter. Set it once, and Netlify enforces it automatically across your entire team.

Learn more in our docs on limiting AI features.

Agent run credits tracking

You can also track how much each agent run task costs on your agent runs page, shown next to how long the agent took to run the task.

Learn more about AI inference usage and how credits work.

OpenAI’s GPT-5.4 and GPT-5.4 Pro models are now available through Netlify’s AI Gateway and Agent Runners with zero configuration required.

Use the OpenAI SDK directly in your Netlify Functions without managing API keys or authentication. The AI Gateway handles everything automatically. Here’s an example using the GPT-5.4 model:

import OpenAI from 'openai';

export default async () => {
    const openai = new OpenAI();

    const response = await openai.responses.create({
        model: 'gpt-5.4',
        input: 'Give a concise explanation of how AI works.',
    });

    return Response.json(response);
};

GPT-5.4 and GPT-5.4 Pro are 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.

Starting today, all completed agent runs show a screenshot of your Deploy Preview. This makes it easier to quickly see the result of an agent run and keep track of agent run sessions without opening the full preview.

Test it out today:

1. Go to your Netlify project dashboard.
2. On the left, select Agent runs, then choose an existing agent run or start a new one by entering a prompt and selecting Run task.
3. At the bottom of your agent run sessions, you’ll find a screenshot of your Deploy Preview. The screenshot is taken from the main page of your project.

Note: If you’ve set up private deploys or password protection, the screenshot will show a sign-in page instead. Learn more about Password protection.

Learn more about getting started with Agent Runners.