Posts tagged "Agent-runners"
-
OpenAI’s GPT-5.6 Sol, Luna, and Terra 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.6 Sol model:
import OpenAI from 'openai';export default async () => {const openai = new OpenAI();const response = await openai.responses.create({model: 'gpt-5.6-sol',input: 'Give a concise explanation of how AI works.',});return Response.json(response);};GPT-5.6 Sol, Luna, and Terra 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.
-
Anthropic’s Claude Sonnet 5 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 Sonnet 5 model:
import Anthropic from '@anthropic-ai/sdk';export default async () => {const anthropic = new Anthropic();const response = await anthropic.messages.create({model: 'claude-sonnet-5',max_tokens: 4096,messages: [{role: 'user',content: 'How can AI improve my coding?'}]});return Response.json(response);};Claude Sonnet 5 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 have redesigned Netlify functions for an improved agent experience.
With these updates, functions are more discoverable, easier to autocomplete, update, and manage for people and agents alike. They move function configuration into code, making it type-safe and immediately visible to editors, tools, and agents, with no platform-specific naming conventions to memorize or get wrong. None of these changes are breaking, so you can adopt them on your own timeline.
Netlify Functions are serverless functions that run on-demand in response to HTTP requests or platform events. They handle server-side logic without any infrastructure to manage, and live in your repository at
netlify/functions/.To learn more about these updates in depth, check out our blog on redesigning Netlify functions for agent experience. See the table below for a summary.
Feature What changed What it means for agents What you need to do Event handlers Export typed event handlers from the default export object Typed handlers are discoverable like any API, with no magic filenames to guess or get wrong. Nothing required. Adopt the new syntax for new event handlers for better agent discoverability and updates. Background functions Declare with background: truein config instead of the-backgroundfilename suffixType-safe and config-driven, not name-driven. Agents can set it in code without guessing platform naming conventions, and get an error if the value is wrong. Nothing required. The -backgroundsuffix still works.Region selection Set per-function via the regionconfig property, replacing the global UI settingAgents can set region as a type-safe config property, catching invalid values before deploy rather than at runtime. Use deploy previews to test before going live. Nothing required. Optionally move region out of the UI into config for per-function control. Memory and vCPU Set via memoryorvcpuconfig properties; both values scale together automaticallyAgents provisioning compute-heavy workloads (inference, large payloads) can do so in code. Nothing. Defaults unchanged. Set only if your workload needs more than 1 GB / 0.5 vCPU. Requires a credit-based Pro plan. getContext()Named import from @netlify/functions, replacing theNetlify.contextglobalNamed imports surface in autocomplete and carry type information. Globals are invisible to agents; named imports are not. Nothing required. Netlify.contextstill works. Switch togetContext()for better discoverability.Learn more in the Netlify Functions documentation, which has also been recently revamped.
-
Anthropic’s Claude Opus 4.8 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.8 model:
import Anthropic from '@anthropic-ai/sdk';export default async () => {const anthropic = new Anthropic();const response = await anthropic.messages.create({model: 'claude-opus-4-8',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.8 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.
-
Google’s Gemini 3.5 Flash model is now available through Netlify’s Agent Runners with zero configuration required.
Learn more in the Agent Runners documentation.
-
We’re making it easier to use Agent Runners in the existing workflows you have. Now you can do the following in a more seamless way:
- Prompt new changes using Agent Runners more quickly from a GitHub pull request link
- Copy output from Agent Runners faster so you can get back to what you’re doing
- Track pull request ownership so you can understand who is doing what at-a-glance
Start prompting updates from GitHub PR comment link
GitHub-linked sites already receive a comment on each pull request with links to build logs, failure diagnostics, and more. That comment now also includes a Make changes link that opens Agent Runner for the site, with the pull request‘s branch pre-selected in the dropdown.
This makes it faster to act on review feedback or investigate a failing build.
Learn more about Agent Runners.
Copy to clipboard in single click
You can now copy Agent Runner output with a single click.
Previously, grabbing output text — especially long responses or anything on mobile — meant manually selecting it all. A new copy-to-clipboard button now appears alongside Agent Runner output, making it easy to drop results into a doc, a message, or wherever you need them.
Pull requests auto-assign people for clearer ownership
Agent Runner–created pull requests now automatically assign the person who opened them, provided their GitHub account is linked with Netlify.
Before this change, pull requests opened by an agent runner had no assignee, making it harder for teams to track ownership at a glance. Now, when Netlify can match the user to a GitHub account, the pull request is assigned to them automatically.
To take advantage of this, make sure your GitHub account is connected under your Netlify account settings.
-
OpenAI’s GPT-5.5 and GPT-5.5 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.5 model:
import OpenAI from 'openai';export default async () => {const openai = new OpenAI();const response = await openai.responses.create({model: 'gpt-5.5',input: 'Give a concise explanation of how AI works.',});return Response.json(response);};GPT-5.5 and GPT-5.5 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.
-
You can now rename an agent run to more easily identify it in your list of runs and share it with teammates.
Previously, agent runs were automatically titled based on your prompt, which made longer lists harder to scan once you had several runs going.
Editing the title lets you give each agent run a short, meaningful name, such as the feature you’re building or the bug you’re chasing, so you can find it again quickly and send it to a teammate without needing to explain which run is which.
Try it out
Open any agent run, select the title, and type a new name. The updated title appears in your list of runs and anywhere the run is shared.
Learn more about Agent Runners.
-
Agent Runners now include a
frontend-designskill 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-designskill 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-designskill 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.