Netlify Functions Redesigned for Agent Experience With Event Handlers and Cross-Platform Support.

Netlify shipped a comprehensive set of upgrades to Netlify Functions designed to improve what the company calls "Agent Experience," making serverless function configuration more legible to both AI agents and human developers. The update, announced on the company blog, introduces event-triggered functions via exported named handlers, native support for fetchable modules, and declarative per-function resource configuration.

The headline feature is a new approach to event-driven functions. Developers can now subscribe to events by exporting a fully typed, named handler rather than relying on filename conventions. This makes function intent explicit in code and immediately parseable by AI coding assistants.

As previously covered, this pattern replaces the previous practice of encoding event types in filenames, making functions more maintainable and less opaque to automated tooling.

Netlify Functions now natively support the fetchable module interface, allowing code written for Deno, Bun, Hono, and Nitro to run with minimal or no changes. This addresses a longstanding friction point for developers working across multiple serverless platforms.

The fetchable module pattern provides a standard interface for request/response handling that works across runtimes. Netlify's implementation means developers can lift code from other platforms and deploy it without rewriting handler signatures. Fetchable module support also improves compatibility with framework-specific deploy targets that assume this interface.

Background functions, which execute asynchronously without blocking HTTP responses, can now be declared with a simple background: true property instead of requiring a -background filename suffix. This declarative approach makes function behavior immediately clear in the code itself.

Developers can now configure region, memory (up to 4 GB), and CPU (up to 2 vCPU) on a per-function basis directly in code. These settings are testable in deploy previews, eliminating the need to push to production to validate resource allocation.

The ability to specify compute resources inline is particularly relevant for functions that handle variable workloads or require specific geographic deployment. Previously, these configurations required separate configuration files or platform settings.

Netlify emphasized that all changes are additive. Every existing function signature continues to work without modification. There are no deprecations and no required migrations.

This backward compatibility is critical for enterprise users with large codebases and for AI agents attempting to understand and modify existing projects. By preserving all prior APIs while adding new, more explicit patterns, Netlify reduces the risk that automated code generation will produce non-functional results.

The updates align with Netlify's broader focus on Agent Experience, a design philosophy centered on making platform behavior predictable and discoverable for AI coding tools. The company has previously published metrics on how it measures Agent Experience, including factors like documentation clarity, API consistency, and configuration explicitness.

The timing of these updates reflects the rapid adoption of AI coding assistants like Cursor, Claude, and ChatGPT in web development workflows. As more developers rely on these tools to scaffold projects and write serverless functions, platforms that make their APIs easy for AI to parse gain a competitive advantage.

Netlify's approach contrasts with platforms that require extensive context or implicit knowledge to configure correctly. By moving configuration into code and using typed exports, Netlify Functions become easier for AI agents to reason about and modify.

The full documentation for the new function patterns is available in Netlify's official documentation, and existing projects can adopt the new patterns incrementally without breaking current deployments.