@netlify/agent-runner-cli 2.16.0-server.0 → 2.16.0-server.2

package/dist/skills/netlify-server@backend/SKILL.md

@@ -164,9 +164,7 @@ See the [changelog post](https://www.netlify.com/changelog/2026-10-07-context-us
 
 The AI Gateway works with zero configuration: provider credentials and base URLs (`OPENAI_API_KEY`, `OPENAI_BASE_URL`, and equivalents for other providers) are injected into `process.env` automatically. See the `netlify-ai-gateway` skill for supported models and usage.
 
-AI Gateway, Netlify Blobs, and Netlify Database clients can be created once at module scope and reused: the platform keeps their credentials current. One exception: `NETLIFY_PURGE_API_TOKEN` expires after 15 minutes, so read it from `process.env` each time you call the purge API and never store it in a module-level variable. On a server, pass the site ID to `purgeCache` explicitly: `purgeCache({ siteID: getContext().site.id, tags })`.
-
-Use site-wide Blobs stores (`getStore`). `getDeployStore()` doesn't work on production deploys yet.
+AI Gateway, Netlify Blobs, and Netlify Database clients can be created once at module scope and reused: the platform keeps their credentials current. One exception: `NETLIFY_PURGE_API_TOKEN` expires after 15 minutes, so read it from `process.env` each time you call the purge API and never store it in a module-level variable.
 
 ```javascript
 import OpenAI from 'openai'

package/dist/skills/netlify-server@netlifyserver/SKILL.md

@@ -9,7 +9,7 @@ A Netlify Server is one long-running Node.js process deployed alongside your sit
 
 ## When to use this skill: explicit request only
 
-Netlify Server is an experimental primitive. The rule for choosing it is strict:
+Netlify Server is in Early Access. The rule for choosing it is strict:
 
 - ONLY build with a Netlify Server when the prompt **explicitly requests a "Netlify Server"** by name (for example "build this as a Netlify Server" or "use the Netlify Server primitive").
 - If the prompt does not name it, discard this skill entirely, even when the request mentions Express, Hono, WebSockets, servers in general, or would otherwise seem like a good fit. In those cases use **Netlify Functions** (see the `netlify-functions` skill) and the other platform primitives as usual.
@@ -168,9 +168,7 @@ See the [changelog post](https://www.netlify.com/changelog/2026-10-07-context-us
 
 The AI Gateway works with zero configuration: provider credentials and base URLs (`OPENAI_API_KEY`, `OPENAI_BASE_URL`, and equivalents for other providers) are injected into `process.env` automatically. See the `netlify-ai-gateway` skill for supported models and usage.
 
-AI Gateway, Netlify Blobs, and Netlify Database clients can be created once at module scope and reused: the platform keeps their credentials current. One exception: `NETLIFY_PURGE_API_TOKEN` expires after 15 minutes, so read it from `process.env` each time you call the purge API and never store it in a module-level variable. On a server, pass the site ID to `purgeCache` explicitly: `purgeCache({ siteID: getContext().site.id, tags })`.
-
-Use site-wide Blobs stores (`getStore`). `getDeployStore()` doesn't work on production deploys yet.
+AI Gateway, Netlify Blobs, and Netlify Database clients can be created once at module scope and reused: the platform keeps their credentials current. One exception: `NETLIFY_PURGE_API_TOKEN` expires after 15 minutes, so read it from `process.env` each time you call the purge API and never store it in a module-level variable.
 
 ```javascript
 import OpenAI from 'openai'

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@netlify/agent-runner-cli",
   "type": "module",
-  "version": "2.16.0-server.0",
+  "version": "2.16.0-server.2",
   "description": "CLI tool for running Netlify agents",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
@@ -48,6 +48,7 @@
     "check:types": "tsc --noEmit",
     "prompts": "LOG=0 vitest run --config vitest.prompts.config.js",
     "site:build": "npm run prompts && node site/build.mjs",
+    "site:dev": "npm run site:build && netlify dev --dir site/dist",
     "postinstall": "node scripts/postinstall.js"
   },
   "engines": {