Netlify Functions Retire Magic Filenames for Typed Config

Netlify rebuilt the configuration surface of Netlify Functions so the settings live in typed code instead of filename conventions, making them something an AI coding agent can actually read and edit instead of guess at. The change, detailed in a June 25, 2026 post on the Netlify blog, touches how functions declare background execution, subscribe to platform events, and set their deploy region.

What actually changed

The clearest example is background functions. Netlify has long supported them by naming a file with a -background suffix, a convention a human has to know and an agent has to infer from a corpus of examples. That naming scheme still works, but new functions can instead set background: true directly in an exported config object, alongside the function’s other settings (Netlify Functions background docs).

Platform events get the same treatment. Any function can now subscribe to events like deploySucceeded, userLogin or formSubmitted by exporting a named handler method on the same default export object that already carries the function’s fetch handler. That’s one file and one typed object, instead of separate wiring per event type. Handler arguments and return values are fully typed, and a returned value is automatically turned into the corresponding platform action where applicable (Netlify Functions API reference).

A new getContext import from the @netlify/functions package (currently at version 5.3.0 on npm) replaces reading request context off a global, so editors and IDE tooling, human or automated, can resolve the type without special-casing a runtime global. Netlify says none of this is a breaking change; the older patterns keep working, and teams can migrate function-by-function on their own schedule.

The pitch: config that doesn’t require memorization

Netlify’s framing for the update is “Agent Experience” (AX), a term the company says it coined in 2025 for how well an AI agent, not just a human developer, can discover an API, call it correctly and recover from an error. Netlify Functions 2.0 shipped in 2023 aimed at developer experience; this update is explicitly aimed at the agent that’s now often the one writing the function in the first place. The company has been pushing the framing beyond this one release, too, including a netlify.ai onboarding flow for autonomous agents and a “Show HN” post on the same theme (Hacker News).

The broader AX pitch has picked up some outside traction. HackerNoon covered Netlify CEO Matt Biilmann arguing AX is the successor to DX rather than a replacement for it, and the term shows up independently in posts from other infrastructure vendors making a similar case about their own APIs. So this isn’t only a Netlify talking point; it’s part of a broader vendor conversation about designing for coding agents as users.

Our take: the technical change here is useful. Typed, in-code config is easier for a linter, an IDE or an agent to reason about than a filename suffix, full stop. But “Agent Experience” as a category is still mostly a rebrand of what used to be called good API design: typed, discoverable, documented, doesn’t require tribal knowledge. That’s not a knock on shipping it. It’s a reminder that the bar for good developer tooling was already rising before agents showed up to read it.