@agent-native/core 0.68.1 → 0.68.2

package/docs/content/template-clips.md

@@ -1,6 +1,7 @@
 ---
 title: "Clips"
 description: "Async screen recording, calendar-synced meeting notes, and push-to-talk voice dictation — paste Clips links into agents and they can read transcripts, visuals, and summaries."
+search: "Clips browser logs developer logs console logs network logs fetch XHR Chrome extension diagnostics recorder desktop app"
 ---
 
 # Clips
@@ -33,10 +34,31 @@ Think along the lines of Loom + Granola + Wispr Flow rolled into one app — but
 - **Share clips** with per-clip permissions (public, team, private). Link tracking and threaded comments work too.
 - **Preview public clips in Slack** with a Loom-style playable unfurl after the
   workspace installs your Clips Slack app.
+- **Capture browser logs with the Chrome extension.** Browser recordings can
+  attach redacted console logs and fetch/XHR metadata, which is helpful for
+  product bugs and browser-only repros.
 - **Paste Clips links into agents** so they can discover the agent-readable context: metadata, transcript segments, recommended frames, and timestamped frame images without receiving the raw video file.
 - **Smart library views.** Group by project, filter by speaker, auto-tag based on content.
 - **Edit the transcript through chat.** "Fix the mis-transcribed word at 1:42." "Pull three quotes for a blog post." The agent edits the transcript and the UI updates live.
 
+## Browser logs and developer diagnostics
+
+Use the Clips Chrome extension when you need a recording plus browser logs from
+the tab you are debugging. The extension starts an active-tab recording and can
+save redacted console logs, JavaScript exceptions, and fetch/XHR network
+metadata such as method, redacted URL, status, duration, and failure text. It
+does not save request bodies, response bodies, or headers.
+
+The regular browser recorder page can save diagnostics from the recorder page
+itself. The Chrome extension is the path for active-tab developer logs and
+browser-only repros. In the Clips UI, use the Chrome option for browser logs and
+the desktop app for the most seamless everyday capture path.
+
+If you host your own Clips server, keep the Chrome extension option hidden until
+your Web Store listing is live. Set `VITE_CLIPS_CHROME_EXTENSION_ENABLED=1` and
+`VITE_CLIPS_CHROME_EXTENSION_URL=<chrome-web-store-url>` after approval to show
+the extension beside desktop-app download prompts.
+
 ## Agent-readable clips
 
 Paste a normal public Clips share link into an agent. The share page advertises
@@ -143,7 +165,7 @@ Clips is a larger template with a native recorder (it ships a desktop companion
 
 1. **Video storage (required).** Connect a storage backend through the onboarding wizard. The easiest path is Builder.io (free during beta, one-click). For self-hosted storage, set `S3_ENDPOINT`, `S3_BUCKET`, `S3_ACCESS_KEY_ID`, `S3_SECRET_ACCESS_KEY`, and optionally `S3_REGION` and `S3_PUBLIC_BASE_URL`. Cloudflare R2 and DigitalOcean Spaces use the same env vars with the `R2_*` prefix.
 2. **Google Calendar (optional).** To sync upcoming meetings, connect a Google Calendar account from Settings. The OAuth callback URL in dev is `http://localhost:8094/_agent-native/google/callback`. Set up a Google OAuth client in [Google Cloud Console](https://console.cloud.google.com/) with the Gmail and Google Calendar APIs enabled.
-3. **Screen-capture permissions.** On macOS, grant Screen Recording permission to the browser (or the desktop companion app) in System Settings → Privacy & Security → Screen Recording.
+3. **Screen-capture permissions.** On macOS, grant Screen Recording permission to the browser (or the desktop companion app) in System Settings → Privacy & Security → Screen Recording. Browser recordings can save redacted console and fetch/XHR diagnostics from the recorder page. Once a deployment has a published Clips Chrome extension URL, enable `VITE_CLIPS_CHROME_EXTENSION_ENABLED=1` and set `VITE_CLIPS_CHROME_EXTENSION_URL` so users can choose the extension for active-tab browser logs or the desktop app for the smoothest native capture path.
 4. **Slack previews (optional).** Create a Slack app with `links:read`, `links:write`, and `links.embed:write`; subscribe to `link_shared`; add your Clips share domain under **App Unfurl Domains**; set the Request URL to `https://your-clips.example.com/api/slack/unfurl`; and add the OAuth redirect URL `https://your-clips.example.com/api/slack/oauth/callback`. Configure `SLACK_CLIENT_ID`, `SLACK_CLIENT_SECRET`, and `SLACK_SIGNING_SECRET`, then connect workspaces from Clips Settings.
 
 ### Host your own Clips server
@@ -185,7 +207,13 @@ tray app at your deployment.
    include that path, such as `https://example.com/clips`. Click **Connect**,
    then sign in with an account on that Clips server.
 
-5. **Connect optional integrations.** Google Calendar powers the Meetings tab,
+5. **Enable the Chrome extension after publishing.** Keep
+   `VITE_CLIPS_CHROME_EXTENSION_ENABLED` unset until the Chrome Web Store listing
+   is approved and you have a public extension URL. Then set it to `1` and set
+   `VITE_CLIPS_CHROME_EXTENSION_URL` to reveal the browser-log option beside the
+   desktop app prompts.
+
+6. **Connect optional integrations.** Google Calendar powers the Meetings tab,
    `GEMINI_API_KEY` or Builder.io Connect powers transcript cleanup and titles,
    `GROQ_API_KEY` can provide speech-to-text fallback, and the Slack OAuth
    connection in Settings enables playable Slack unfurls.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.68.1",
+  "version": "0.68.2",
   "type": "module",
   "engines": {
     "node": ">=22"