@netlify/agent-runner-cli 1.90.1 → 1.90.3

package/dist/skills/netlify-ai-gateway/SKILL.md

@@ -1,10 +1,12 @@
 ---
 name: netlify-ai-gateway
-description: Use Netlify AI Gateway for AI inference in Netlify Functions and server-side code. Use when adding AI/LLM features with OpenAI, Anthropic, or Google Gemini without managing API keys.
+description: Use Netlify AI Gateway for AI inference in Netlify Functions and server-side code. Use when adding AI/LLM features with OpenAI, Anthropic, or Google Gemini without managing API keys. Must be read before selecting or changing any AI model. Contains the list of supported models.
 ---
 
 # Netlify AI Gateway
 
+> **IMPORTANT:** Only use models listed in the "Available Models" section below. AI Gateway does not support every model a provider offers. Using an unsupported model will cause runtime errors.
+
 Zero-config AI inference for Netlify projects. Netlify automatically injects environment variables so official
 provider SDKs work without API keys or configuration.
 
@@ -87,7 +89,7 @@ const response = await openai.responses.create({
 console.log(response.output_text)
 ```
 
-### Google Gemini
+### Gemini
 
 ```bash
 npm install @google/genai
@@ -201,24 +203,6 @@ for (const item of response.output) {
 }
 ```
 
-### Google Gemini (Imagen)
-
-```typescript
-import { GoogleGenAI } from '@google/genai'
-
-const ai = new GoogleGenAI({})
-
-const response = await ai.models.generateImages({
-  model: 'imagen-4.0-generate-001',
-  prompt: 'A cute otter in a river',
-  config: { numberOfImages: 1 },
-})
-
-for (const image of response.generatedImages) {
-  const imageBytes = image.image.imageBytes
-}
-```
-
 ## Netlify Functions
 
 Full example of a Netlify Function using AI Gateway:
@@ -354,64 +338,13 @@ const response = await fetch(`${process.env.ANTHROPIC_BASE_URL}/v1/messages`, {
 
 ## Available Models
 
-Key models per provider. For the latest list, see https://docs.netlify.com/build/ai-gateway/overview/.
-
-### Anthropic
-
-- `claude-opus-4-6`
-- `claude-opus-4-5-20251101`
-- `claude-opus-4-1-20250805`
-- `claude-sonnet-4-5-20250929`
-- `claude-sonnet-4-20250514`
-- `claude-haiku-4-5-20251001`
-- `claude-3-7-sonnet-20250219`
-- `claude-3-5-haiku-20241022`
-
-### OpenAI
+For the latest list, see https://docs.netlify.com/build/ai-gateway/overview/.
 
-- `gpt-5.2`
-- `gpt-5.1`
-- `gpt-5.1-codex`
-- `gpt-5`
-- `gpt-5-mini`
-- `gpt-5-nano`
-- `gpt-4.1`
-- `gpt-4.1-mini`
-- `gpt-4.1-nano`
-- `gpt-4o`
-- `gpt-4o-mini`
-- `o3`
-- `o3-mini`
-- `o4-mini`
-- `gpt-image-1` (image generation)
-- `codex-mini-latest`
-
-### Google Gemini
-
-- `gemini-3-pro-preview`
-- `gemini-3-flash-preview`
-- `gemini-2.5-pro`
-- `gemini-2.5-flash`
-- `gemini-2.5-flash-lite`
-- `gemini-2.0-flash`
-- `gemini-2.0-flash-lite`
-- `imagen-4.0-generate-001` (image generation)
-- `veo-3.0-generate-preview` (video generation)
+<!-- AVAILABLE_MODELS -->
 
 ## Rate Limits
 
-Tokens per minute (TPM) are scoped per **account** across all projects. Both input and output tokens count.
-For Anthropic, cached tokens are excluded; for other providers, cached tokens are included.
-For the latest limits, see https://docs.netlify.com/build/ai-gateway/overview/.
-
-| Model | Free | Personal | Pro |
-|-------|------|----------|-----|
-| claude-sonnet-4-5-20250929 | 18,000 | 90,000 | 180,000 |
-| gpt-5 | 18,000 | 90,000 | 180,000 |
-| gpt-4o-mini | 250,000 | 500,000 | 750,000 |
-| gemini-2.5-pro | 24,000 | 120,000 | 240,000 |
-
-Set up rate limiting rules on your functions to prevent abuse from client-side callers.
+Tokens per minute (TPM) are scoped per **account** across all projects. For current limits per model and plan tier, see https://docs.netlify.com/build/ai-gateway/overview/.
 
 ## Limitations
 

package/dist/skills/netlify-forms/SKILL.md

@@ -49,7 +49,9 @@ form.addEventListener('submit', async (e) => {
 })
 ```
 
-> **SSR apps (Next.js, TanStack Start, SvelteKit, Remix, Nuxt):** POST to `/__forms.html` instead of `/`. SSR frameworks intercept POSTs to `/`, silently preventing Netlify from processing the submission. See [JavaScript Frameworks](#javascript-frameworks-ssr--client-rendered-apps) below.
+> **SSR/SPA apps (React, Vue, TanStack Start, Next.js, SvelteKit, Remix, Nuxt):** You MUST create a static HTML skeleton
+> file for build-time form detection. Without it, Netlify cannot detect the form during build and submissions will
+> silently fail. See [JavaScript Frameworks](#javascript-frameworks-ssr--client-rendered-apps) below.
 
 **Critical AJAX requirements:**
 
@@ -58,34 +60,43 @@ form.addEventListener('submit', async (e) => {
    ```html
    <input type="hidden" name="form-name" value="contact" />
    ```
-3. For SSR/SPA apps, POST to `/__forms.html` instead of `/` (see JavaScript Frameworks section)
 
 ## JavaScript Frameworks (SSR & Client-Rendered Apps)
 
-Netlify's build bot cannot detect forms rendered client-side. For any SSR or SPA framework (React, Vue, TanStack Start, Next.js, SvelteKit, Remix, Nuxt), you MUST:
+Netlify's build bot cannot detect forms rendered client-side. For any SSR or SPA framework (React, Vue, TanStack Start,
+Next.js, SvelteKit, Remix, Nuxt), you MUST:
 
-1. Create `public/__forms.html` containing a static HTML skeleton of each form for build-time detection
-2. Submit via AJAX with `e.preventDefault()` — full-page POST will not work
-3. POST to `/__forms.html` (not `/`) — SSR frameworks intercept POSTs to `/`, silently preventing Netlify from processing submissions
+1. **Create a static HTML skeleton** in `public/` for build-time form detection — this is the critical step. Without it,
+   Netlify never registers the form and submissions will silently fail or 404.
+2. Submit via AJAX with `e.preventDefault()` — full-page POST will not work in SPAs
+3. Include a hidden `form-name` field matching the form's `name` attribute
 
 ### Static Form Skeleton
 
-Create `public/__forms.html`:
+Create a static HTML file (e.g. `public/__forms.html`) containing every form your app uses. The file name does not
+matter — Netlify scans all HTML files in the build output:
 
 ```html
 <!-- public/__forms.html — only for Netlify's build bot detection -->
 <html>
   <body>
-    <form name="contact" data-netlify="true" hidden>
+    <form name="contact" data-netlify="true" netlify-honeypot="bot-field" hidden>
       <input type="hidden" name="form-name" value="contact" />
       <input name="name" />
       <input name="email" />
       <textarea name="message"></textarea>
+      <input name="bot-field" />
     </form>
   </body>
 </html>
 ```
 
+**Rules:**
+
+- The form `name` attribute must exactly match the `form-name` value in your React/Vue component
+- Include every field your component submits — Netlify validates field names against the registered form
+- Add `netlify-honeypot="bot-field"` and a `bot-field` input for spam protection
+
 ### React Example
 
 ```jsx
@@ -94,7 +105,7 @@ function ContactForm() {
     e.preventDefault()
     const formData = new FormData(e.target)
 
-    await fetch('/__forms.html', {
+    await fetch('/', {
       method: 'POST',
       headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
       body: new URLSearchParams(formData).toString(),
@@ -102,9 +113,14 @@ function ContactForm() {
   }
 
   return (
-    <form name="contact" method="POST" onSubmit={handleSubmit}>
+    <form name="contact" method="POST" data-netlify="true" netlify-honeypot="bot-field" onSubmit={handleSubmit}>
       {/* Hidden field required for AJAX */}
       <input type="hidden" name="form-name" value="contact" />
+      <p style={{ display: 'none' }}>
+        <label>
+          Don't fill this out: <input name="bot-field" />
+        </label>
+      </p>
       <input name="name" required />
       <input name="email" type="email" required />
       <textarea name="message" />
@@ -203,7 +219,8 @@ The `action` path must:
 - Be relative to site root
 - Point to an existing page
 
-> **Pretty URLs:** Netlify serves `thank-you.html` at `/thank-you` by default. Use `action="/thank-you"`, not `action="/thank-you.html"` — the `.html` path returns 404.
+> **Pretty URLs:** Netlify serves `thank-you.html` at `/thank-you` by default. Use `action="/thank-you"`, not
+> `action="/thank-you.html"` — the `.html` path returns 404.
 
 ## Notifications
 
@@ -293,17 +310,13 @@ export default async (req: Request, context: Context) => {
 
 ### Form succeeds but no submissions appear (SSR apps)
 
-**Cause:** POST to `/` is intercepted by the SSR handler (Next.js, TanStack Start, SvelteKit, Remix, Nuxt). The SSR handler returns 200, so `fetch()` reports success, but Netlify never processes the submission.
+**Cause:** The form was not detected during build. Without a static HTML skeleton, Netlify doesn't register the form, so
+submissions are passed through to the SSR handler (Next.js, TanStack Start, SvelteKit, Remix, Nuxt). The SSR handler
+returns 200, so `fetch()` reports success, but Netlify never processes the submission.
 
-**Fix:** POST to `/__forms.html` instead of `/`:
-
-```javascript
-await fetch('/__forms.html', {
-  method: 'POST',
-  headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
-  body: new URLSearchParams(formData).toString(),
-})
-```
+**Fix:** Create a static HTML skeleton in `public/` (see
+[JavaScript Frameworks](#javascript-frameworks-ssr--client-rendered-apps) section). Once the form is properly registered
+at build time, Netlify intercepts form POSTs at the CDN level before they reach the SSR handler.
 
 ### File upload fails
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@netlify/agent-runner-cli",
   "type": "module",
-  "version": "1.90.1",
+  "version": "1.90.3",
   "description": "CLI tool for running Netlify agents",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",