diff --git a/docs/src/content/docs/agent-guidance.md b/docs/src/content/docs/agent-guidance.md
index e64da068e..eb2504a2d 100644
--- a/docs/src/content/docs/agent-guidance.md
+++ b/docs/src/content/docs/agent-guidance.md
@@ -96,6 +96,23 @@ sentry log list --follow
 sentry log list --query "severity:error"
 ```
 
+### Capture Events Locally (Spotlight)
+
+```bash
+# Run the app with the local server auto-enabled; tail errors/traces/logs.
+# No DSN needed — with no DSN, events go ONLY to the local server (nothing
+# reaches the user's Sentry org, no production quota). With a DSN set, the
+# SDK sends to both.
+sentry local run -- npm run dev          # or: python manage.py runserver, etc.
+
+# Watch only AI/agent (gen_ai, mcp) spans while iterating on an agent.
+sentry local serve -f ai
+
+# Server-side SDKs read SENTRY_SPOTLIGHT automatically. For BROWSER/client
+# events (e.g. Next.js), the SDK does NOT read the env var — reference it in
+# the client config: Sentry.init({ spotlight: process.env.NEXT_PUBLIC_SENTRY_SPOTLIGHT ?? false })
+```
+
 ### Explore the API Schema
 
 ```bash
diff --git a/docs/src/fragments/commands/local.md b/docs/src/fragments/commands/local.md
index 343de505d..a73fa2236 100644
--- a/docs/src/fragments/commands/local.md
+++ b/docs/src/fragments/commands/local.md
@@ -2,6 +2,8 @@
 
 `sentry local` runs a local development server that captures Sentry SDK envelopes from your dev stack and surfaces errors, traces, and logs in real time — right in your terminal. No authentication required.
 
+No DSN is required either. If your app has no DSN configured, events flow **only** to the local server — nothing reaches your Sentry organization and no production quota is used. If a DSN *is* set, the SDK sends to both Sentry and the local server.
+
 If a server is already running on the port, the command attaches as an SSE consumer instead of starting a duplicate.
 
 ## Examples
@@ -36,6 +38,14 @@ Env vars injected into the child process:
 | `NEXT_PUBLIC_SENTRY_SPOTLIGHT` | `http://localhost:<port>/stream` |
 | `SENTRY_TRACES_SAMPLE_RATE` | `1` (unless already set) |
 
+**Server vs. client.** Server-side SDKs (`@sentry/node`, Python, and friends) read `SENTRY_SPOTLIGHT` automatically — no code changes needed. Browser/client SDKs can't read process env, so the CLI also injects `NEXT_PUBLIC_SENTRY_SPOTLIGHT` to expose the URL to Next.js client bundles. The SDK does **not** read that variable on its own, though — to capture client-side events you must reference it in your client config:
+
+```ts
+Sentry.init({ spotlight: process.env.NEXT_PUBLIC_SENTRY_SPOTLIGHT ?? false });
+```
+
+Other frameworks expose client env vars under different prefixes (Vite `VITE_`, CRA `REACT_APP_`) — set the equivalent yourself.
+
 ## Endpoints
 
 | Method | Path                            | Description                                        |
@@ -78,6 +88,13 @@ Use `--quiet` to suppress tail output entirely if you only need the SSE stream.
 
 GenAI operations show the model name, MCP tool calls show the tool being invoked, and database queries show the system and query summary. This works automatically when your Sentry SDK is configured with AI/LLM integrations.
 
+To watch only agent activity, filter to the `ai` item type:
+
+```bash
+sentry local -f ai          # only AI/agent spans
+sentry local -f ai -f error # agent spans and errors
+```
+
 ## JSON output
 
 Use `--format json` (or `-F json`) for machine-readable NDJSON output, one JSON object per envelope item:
diff --git a/plugins/sentry-cli/skills/sentry-cli/SKILL.md b/plugins/sentry-cli/skills/sentry-cli/SKILL.md
index 410349511..c0658546d 100644
--- a/plugins/sentry-cli/skills/sentry-cli/SKILL.md
+++ b/plugins/sentry-cli/skills/sentry-cli/SKILL.md
@@ -106,6 +106,23 @@ sentry log list --follow
 sentry log list --query "severity:error"
 ```
 
+#### Capture Events Locally (Spotlight)
+
+```bash
+# Run the app with the local server auto-enabled; tail errors/traces/logs.
+# No DSN needed — with no DSN, events go ONLY to the local server (nothing
+# reaches the user's Sentry org, no production quota). With a DSN set, the
+# SDK sends to both.
+sentry local run -- npm run dev          # or: python manage.py runserver, etc.
+
+# Watch only AI/agent (gen_ai, mcp) spans while iterating on an agent.
+sentry local serve -f ai
+
+# Server-side SDKs read SENTRY_SPOTLIGHT automatically. For BROWSER/client
+# events (e.g. Next.js), the SDK does NOT read the env var — reference it in
+# the client config: Sentry.init({ spotlight: process.env.NEXT_PUBLIC_SENTRY_SPOTLIGHT ?? false })
+```
+
 #### Explore the API Schema
 
 ```bash
diff --git a/plugins/sentry-cli/skills/sentry-cli/references/local.md b/plugins/sentry-cli/skills/sentry-cli/references/local.md
index 647aed124..d9d602eae 100644
--- a/plugins/sentry-cli/skills/sentry-cli/references/local.md
+++ b/plugins/sentry-cli/skills/sentry-cli/references/local.md
@@ -51,6 +51,9 @@ sentry local --quiet
 
 sentry local -f error -f log    # only errors and logs
 
+sentry local -f ai          # only AI/agent spans
+sentry local -f ai -f error # agent spans and errors
+
 sentry local --format json
 ```