@agent-native/core 0.169.1 → 0.171.0

package/docs/content/template-clips-capture-everywhere.mdx

@@ -1,14 +1,14 @@
 ---
-title: "Capturing Everywhere: Desktop, Mobile, and Screen Memory"
-description: "Every way to get a recording into Clips — the desktop tray app, the mobile companion, Rewind quick-save, local-only Screen Memory, and the Chrome extension for browser logs."
-search: "Clips desktop app mobile companion Rewind quick save Screen Memory Chrome extension browser logs"
+title: "Capturing Everywhere: Desktop, Mobile, and Rewind"
+description: "Every way to get a recording into Clips: the desktop tray app, the mobile companion, the local-only Rewind memory, and the Chrome extension for browser logs."
+search: "Clips desktop app mobile companion Rewind memory add what happened before Screen Memory Chrome extension browser logs"
 ---
 
 # Capturing everywhere
 
-Clips isn't only a browser recorder. This page covers every place you can start a capture — the desktop tray app, the mobile companion app, pulling in a moment you forgot to record, the local-only Screen Memory buffer, and the Chrome extension for browser logs — and who each one is for.
+Clips isn't only a browser recorder. This page covers every place you can start a capture, and who each one is for: the desktop tray app, the mobile companion app, the local-only Rewind memory, and the Chrome extension for browser logs.
 
-<Diagram id="doc-block-clips1" title="Capture surfaces" summary={"Desktop, mobile, and the Chrome extension all land in your shared Clips library. Screen Memory is the one exception — it never leaves your machine."}>
+<Diagram id="doc-block-clips1" title="Capture surfaces" summary={"Desktop, mobile, and the Chrome extension all land in your shared Clips library. Rewind is the one exception. It never leaves your device unless you approve it."}>
 
 ```html
 <div class="diagram-flow">
@@ -20,17 +20,17 @@ Clips isn't only a browser recorder. This page covers every place you can start
   <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
   <div class="diagram-box" data-rough>
     Clips library<br /><small class="diagram-muted"
-      >hosted, SQL — searchable and shareable</small
+      >hosted, SQL, searchable and shareable</small
     >
   </div>
 </div>
 <div class="diagram-flow" style="margin-top: 14px">
-  <div class="diagram-node">Screen Memory</div>
+  <div class="diagram-node">Rewind</div>
   <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
   <div class="diagram-panel center">
-    <span class="diagram-pill">Your machine only</span
+    <span class="diagram-pill">Your device only</span
     ><small class="diagram-muted"
-      >local files, off by default, never uploaded</small
+      >local files, off by default, shared only when you approve it</small
     >
   </div>
 </div>
@@ -64,50 +64,49 @@ Clips isn't only a browser recorder. This page covers every place you can start
 
 ## Desktop recorder and the desktop tray app
 
-Clips ships a desktop companion built for the smoothest everyday capture path: screen and webcam recording with a draggable camera bubble, live transcription while you record, calendar meeting reminders, and Hold-Fn dictation — all without keeping a browser tab open.
+Clips ships a desktop companion built for the smoothest everyday capture path: screen and webcam recording with a draggable camera bubble, live transcription while you record, calendar meeting reminders, and Hold-Fn dictation, all without keeping a browser tab open.
 
 The first time you record your screen, your operating system will ask you to grant Screen Recording permission (on a Mac: System Settings → Privacy & Security → Screen Recording). That's an OS-level permission, not a Clips setting, and Clips can't record without it.
 
-While a meeting app like Zoom or Microsoft Teams is in the foreground, the desktop app can also offer a quick "Take notes?" prompt so you don't have to remember to start a recording yourself — see [Recording, importing, and meetings](/docs/template-clips#recording-importing-and-meetings) for what happens once you accept.
+While a meeting app like Zoom or Microsoft Teams is in the foreground, the desktop app can also offer a quick "Take notes?" prompt so you don't have to remember to start a recording yourself. See [Recording, importing, and meetings](/docs/template-clips#recording-importing-and-meetings) for what happens once you accept.
 
 ## Mobile companion capture
 
-The Agent Native mobile app (iOS/Android) brings capture to your phone: dictate, join or record a meeting, shoot a quick video, or import a clip — from the phone's home screen or an OS quick action.
+The Agent Native mobile app (iOS/Android) brings capture to your phone: dictate, join or record a meeting, shoot a quick video, or import a clip, all from the phone's home screen or an OS quick action.
 
 A few things are different from desktop:
 
 - **Meeting audio is microphone-only.** Phones can't capture another app's call audio the way a desktop can, so mobile meeting recordings don't get the same per-attendee action-item attribution as a desktop capture with both mic and system audio. Mobile is a good fit for in-person rooms or for capturing audio playing from a separate device.
 - **Dictation is tap-to-start/stop**, not press-and-hold like the desktop Fn-hold flow.
-- **Uploads are durable.** The audio or video file saves to your phone before any network request, so a dropped connection never loses the capture — it resumes the upload automatically once you're back online. You don't need to keep the app open or re-record after a failed upload.
+- **Uploads are durable.** The audio or video file saves to your phone before any network request, so a dropped connection never loses the capture. The upload resumes automatically once you're back online. You don't need to keep the app open or re-record after a failed upload.
 
-## Rewind quick-save
+## Rewind
 
-If you use [Rewind](https://www.rewind.ai) (a local screen-recall app) on your Mac and realize, after the fact, that a moment was worth keeping, Clips can pull in the last 30 seconds or 5 minutes of your local Rewind history and prepend it to a private clip.
+Rewind is an optional local memory that keeps a rolling recording of your screen (and audio, if you turn it on), stored locally on your device.
 
-A few rules keep this predictable:
-
-- Only the clip's owner can request it, and only on a **private** clip with no one else already granted direct access — removing anyone else's access first keeps the pulled-in Rewind footage from being retroactively shared.
-- It replaces the clip's media with the combined recording. The transcript, chapters, comments, and reactions all shift automatically so their timestamps still line up with the new, earlier start time.
-- It's explicit and per-clip — Rewind quick-save never runs automatically in the background.
+<Callout id="doc-block-clips2" tone="info">
+  Rewind is off by default. Nothing is captured until you turn it on in the
+  desktop tray's settings, and nothing leaves your device unless you approve it
+  (per-request review is on by default and can be turned off in Rewind's
+  settings). You can export, search, or clear the buffer yourself at any time.
+</Callout>
 
-## Screen Memory
+The feature can be enabled under the Rewind tab in Settings. When enabled, you can ask the agent things like "what was I looking at 20 minutes ago?" and the agent reads the text excerpts from the local buffer of on-screen text, app and window context, and transcript snippets. The agent never receives the recordings themselves. The only exception is a request you review and approve, which turns an exact range into a private Clip (see below).
 
-Screen Memory is a different, optional feature: a local-only buffer that quietly notes which app or window was in front of you recently, entirely on your own machine.
+### Add what happened before
 
-<Callout id="doc-block-clips2" tone="info">
-  Screen Memory is off by default. Nothing is captured until you turn it on, and
-  nothing ever leaves your machine automatically — you export or clear it
-  yourself from the desktop tray's settings.
-</Callout>
+In the clip's editor, **Add what happened before** pulls the previous 30 seconds or 5 minutes from your local Rewind history and adds it to the start of the clip. The clip must have been recorded on this device while Rewind was on, and the moments must still be within Rewind's retained history.
 
-When it's enabled, you can ask the agent things like "what was I looking at 20 minutes ago?" and it checks the local buffer before answering. It is never a hosted or shareable Clips recording, and it never exposes raw screen images to the agent — only bounded text snippets of app and window context.
+- The clip must be private, with no one else granted direct access. Rewind history can contain context from before you chose to record, so Clips makes the clip private first and stops if anyone else still has access.
+- The clip's media is replaced with the combined recording. The transcript, chapters, comments, and reactions shift so their timestamps still line up, and the timeline marks where the original clip started.
+- It runs once per clip and only when you ask. Nothing is added from Rewind automatically.
 
 ## Browser logs with the Chrome extension
 
-Install the Clips Chrome extension when you want a recording plus the browser logs and network activity from the tab you're debugging — useful for reporting product bugs and browser-only repros.
+Install the Clips Chrome extension when you want a recording plus the browser logs and network activity from the tab you're debugging. It's useful for reporting product bugs and browser-only repros.
 
 - It only watches the tab you're actively recording, and only while the recording is running.
-- It saves console messages and basic per-request info (method, a redacted URL, status, duration, and whether a request failed) — never request or response bodies, headers, or cookies.
+- It saves console messages and basic per-request info (method, a redacted URL, status, duration, and whether a request failed). It never saves request or response bodies, headers, or cookies.
 - Use the desktop app for the smoothest everyday recording; reach for the Chrome extension specifically when you need those browser logs attached.
 
 See [Extending Clips](/docs/template-clips-developers) for the extension's install link and how to configure it on a self-hosted deployment.

package/docs/content/template-clips-developers.mdx

@@ -100,7 +100,7 @@ This pilot requires the reporter to already have an active session in the Clips
 
 All data lives in SQL via Drizzle ORM. Schema: `templates/clips/server/db/schema.ts`. Recordings, meetings, dictations, calendar accounts, and vocabulary all carry the standard `ownableColumns` and have a matching framework shares table, so they slot into the per-user / per-org sharing model.
 
-Two things live outside this schema on purpose: organization/member/invitation rows are framework-owned tables (`organizations`, `org_members`, `org_invitations`), with `organization_settings` as the Clips-specific sidecar keyed by organization id; and the Rewind quick-save request lifecycle and mobile-capture-state live in `application_state`, not a SQL table, since they're short-lived, per-session status rather than durable app data.
+Two things live outside this schema on purpose: organization/member/invitation rows are framework-owned tables (`organizations`, `org_members`, `org_invitations`), with `organization_settings` as the Clips-specific sidecar keyed by organization id; and the "Add what happened before" (Rewind pre-roll) request lifecycle and mobile-capture-state live in `application_state`, not a SQL table, since they're short-lived, per-session status rather than durable app data.
 
 <DataModel
   id="doc-block-oitg2"
@@ -313,7 +313,7 @@ Recordings and transcripts are intentionally separate tables so the library and
     },
     {
       path: "actions/request-rewind-extension.ts",
-      note: "Local Rewind quick-save request lifecycle",
+      note: "Add-what-happened-before (Rewind pre-roll) request lifecycle",
     },
     {
       path: "app/routes/",
@@ -349,7 +349,7 @@ Every agent-callable operation is a TypeScript file in `templates/clips/actions/
 - **Sharing, comments & engagement** — framework sharing actions (`share-resource`, `set-resource-visibility`, `list-resource-shares`) plus `build-embed-url`, `create-recording-agent-link`, `create-cta` / `update-cta` / `delete-cta`, `add-comment` / `reply-to-comment` / `resolve-comment` / `react-to-comment` / `delete-comment`, `react-to-recording`, `list-viewers`, `list-clip-views`.
 - **Organizations & members** — `create-organization`, `set-organization-branding`, `invite-member` / `accept-invite` / `decline-invite` / `get-invite`, `remove-member`, `update-member-role`, `list-organization-state`, `list-notifications`.
 - **Screen Memory** — `get-screen-memory-status`, `query-screen-memory-context`. Both read bounded local files on the current machine only; neither ever returns media bytes or images.
-- **Rewind quick-save** — `request-rewind-extension`, `get-rewind-extension-request`, `list-rewind-extension-requests`, `update-rewind-extension-request`, `make-recording-private-for-rewind`, `apply-rewind-extension`.
+- **Add what happened before (Rewind pre-roll)** — `request-rewind-extension`, `get-rewind-extension-request`, `list-rewind-extension-requests`, `update-rewind-extension-request`, `make-recording-private-for-rewind`, `apply-rewind-extension`.
 - **Mobile companion** — `set-mobile-capture-state` records the privacy-safe view/phase of the mobile capture UI; it's not agent-callable (`agentTool: false`).
 - **CRM & Brain export** — `prepare-crm-call-evidence`, `export-to-brain`.
 - **Search & insights** — `search-recordings` (matches titles, descriptions, transcript text, and comments, with timestamps), `get-recording-insights`, `get-organization-insights`, `export-insights-csv`, `list-ai-requests` / `update-ai-request-status`.
@@ -372,7 +372,7 @@ The agent edits routes, components, the transcript pipeline, and the schema as n
 ## What's next
 
 - [**Clips**](/docs/template-clips) — the overview
-- [**Capturing Everywhere**](/docs/template-clips-capture-everywhere) — desktop, mobile, Rewind, Screen Memory, and the Chrome extension from a user's perspective
+- [**Capturing Everywhere**](/docs/template-clips-capture-everywhere) — desktop, mobile, Rewind, and the Chrome extension from a user's perspective
 - [**Sharing, Teams, and Agent-Readable Clips**](/docs/template-clips-sharing-and-teams) — the sharing model this data model backs
 - [**AI Pipeline, Editing, and Insights**](/docs/template-clips-ai-and-editing) — the transcription and editing pipeline these actions power
 - [**Templates**](/docs/cloneable-saas) — the Cloneable SaaS model

package/docs/content/template-clips.mdx

@@ -110,7 +110,9 @@ Live demo: [clips.agent-native.com](https://clips.agent-native.com).
 
 ## What's next
 
-- [**Capturing Everywhere**](/docs/template-clips-capture-everywhere) — the desktop app, the mobile companion, Rewind quick-save, Screen Memory, and the Chrome extension.
+{/* i18n-copy-ignore: formatting-only line break; localized copies predate this link list, so no translated prose changed. */}
+
+- [**Capturing Everywhere**](/docs/template-clips-capture-everywhere) — the desktop app, the mobile companion, Rewind, and the Chrome extension.
 - [**Sharing, Teams, and Agent-Readable Clips**](/docs/template-clips-sharing-and-teams) — visibility, passwords, organizations, and pasting a clip link into an agent.
 - [**AI Pipeline, Editing, and Insights**](/docs/template-clips-ai-and-editing) — transcription, non-destructive editing, and view analytics.
 - [**Extending Clips**](/docs/template-clips-developers) — for anyone customizing or extending the template.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.169.1",
+  "version": "0.171.0",
   "description": "Framework for agent-native application development — where AI agents and UI share SQL state, actions, and context",
   "homepage": "https://github.com/BuilderIO/agent-native#readme",
   "bugs": {
@@ -429,7 +429,7 @@
     "yjs": "^13.6.32",
     "zod": "^4.3.6",
     "@agent-native/recap-cli": "0.5.8",
-    "@agent-native/toolkit": "^0.16.10"
+    "@agent-native/toolkit": "^0.16.11"
   },
   "devDependencies": {
     "@ai-sdk/anthropic": "^3.0.71",

package/src/eject/workspace-connections.ts

@@ -17,7 +17,11 @@ export const WORKSPACE_CONNECTION_PROVIDERS: WorkspaceConnectionProvider[] = [
   "figma",
   "notion",
   "gmail",
+  "google_calendar",
   "google_drive",
+  "google_docs",
+  "google_sheets",
+  "google_slides",
   "hubspot",
   "salesforce",
   "jira",

package/src/templates/chat/.agents/skills/secrets/SKILL.md

@@ -19,10 +19,17 @@ data, and generated extension/app content may mention credential **names** such
 as `OPENAI_API_KEY`, but must not contain real API keys, tokens, webhook URLs,
 signing secrets, OAuth refresh tokens, or private Builder/customer data.
 
-Secret values are supplied at runtime through deployment configuration, the
-encrypted `app_secrets` vault, `saveCredential` / `resolveCredential`, OAuth, or
-`${keys.NAME}` substitution. Examples must use obvious placeholders such as
-`<OPENAI_API_KEY>` or `${keys.SLACK_WEBHOOK}`, not real-looking copied values.
+Provider secret values are supplied at runtime through the encrypted
+`app_secrets` vault, `saveCredential` / `resolveCredential`, OAuth, or
+`${keys.NAME}` substitution. Deployment configuration is reserved for
+deploy-level secrets and non-provider configuration. Examples must use obvious
+placeholders such as `<OPENAI_API_KEY>` or `${keys.SLACK_WEBHOOK}`, not
+real-looking copied values.
+
+Provider credentials and provider account identifiers are workspace data. Use
+standard workspace connections and org/workspace vault scopes; never put them
+in `.env` or deployment environment variables, and never add a provider-specific
+action or startup bootstrap just to write a credential for one organization.
 
 ## Credential Modeling Preflight
 

package/src/templates/chat/app/routes.ts

@@ -1,4 +1,6 @@
 import { type RouteConfig } from "@react-router/dev/routes";
 import { flatRoutes } from "@react-router/fs-routes";
 
-export default flatRoutes() satisfies RouteConfig;
+export default flatRoutes({
+  ignoredRouteFiles: ["**/*.test.{ts,tsx}", "**/*.spec.{ts,tsx}"],
+}) satisfies RouteConfig;

package/src/templates/chat/vitest.config.ts

@@ -11,4 +11,12 @@ export default defineConfig({
       "@shared": path.resolve(__dirname, "./shared"),
     },
   },
+  test: {
+    exclude: [
+      "**/node_modules/**",
+      "**/.git/**",
+      "**/dist/**",
+      "**/.react-router/**",
+    ],
+  },
 });

package/src/templates/default/.agents/skills/secrets/SKILL.md

@@ -19,10 +19,17 @@ data, and generated extension/app content may mention credential **names** such
 as `OPENAI_API_KEY`, but must not contain real API keys, tokens, webhook URLs,
 signing secrets, OAuth refresh tokens, or private Builder/customer data.
 
-Secret values are supplied at runtime through deployment configuration, the
-encrypted `app_secrets` vault, `saveCredential` / `resolveCredential`, OAuth, or
-`${keys.NAME}` substitution. Examples must use obvious placeholders such as
-`<OPENAI_API_KEY>` or `${keys.SLACK_WEBHOOK}`, not real-looking copied values.
+Provider secret values are supplied at runtime through the encrypted
+`app_secrets` vault, `saveCredential` / `resolveCredential`, OAuth, or
+`${keys.NAME}` substitution. Deployment configuration is reserved for
+deploy-level secrets and non-provider configuration. Examples must use obvious
+placeholders such as `<OPENAI_API_KEY>` or `${keys.SLACK_WEBHOOK}`, not
+real-looking copied values.
+
+Provider credentials and provider account identifiers are workspace data. Use
+standard workspace connections and org/workspace vault scopes; never put them
+in `.env` or deployment environment variables, and never add a provider-specific
+action or startup bootstrap just to write a credential for one organization.
 
 ## Credential Modeling Preflight
 

package/src/templates/default/app/routes.ts

@@ -1,4 +1,6 @@
 import { type RouteConfig } from "@react-router/dev/routes";
 import { flatRoutes } from "@react-router/fs-routes";
 
-export default flatRoutes() satisfies RouteConfig;
+export default flatRoutes({
+  ignoredRouteFiles: ["**/*.test.{ts,tsx}", "**/*.spec.{ts,tsx}"],
+}) satisfies RouteConfig;

package/src/templates/headless/.agents/skills/secrets/SKILL.md

@@ -19,10 +19,17 @@ data, and generated extension/app content may mention credential **names** such
 as `OPENAI_API_KEY`, but must not contain real API keys, tokens, webhook URLs,
 signing secrets, OAuth refresh tokens, or private Builder/customer data.
 
-Secret values are supplied at runtime through deployment configuration, the
-encrypted `app_secrets` vault, `saveCredential` / `resolveCredential`, OAuth, or
-`${keys.NAME}` substitution. Examples must use obvious placeholders such as
-`<OPENAI_API_KEY>` or `${keys.SLACK_WEBHOOK}`, not real-looking copied values.
+Provider secret values are supplied at runtime through the encrypted
+`app_secrets` vault, `saveCredential` / `resolveCredential`, OAuth, or
+`${keys.NAME}` substitution. Deployment configuration is reserved for
+deploy-level secrets and non-provider configuration. Examples must use obvious
+placeholders such as `<OPENAI_API_KEY>` or `${keys.SLACK_WEBHOOK}`, not
+real-looking copied values.
+
+Provider credentials and provider account identifiers are workspace data. Use
+standard workspace connections and org/workspace vault scopes; never put them
+in `.env` or deployment environment variables, and never add a provider-specific
+action or startup bootstrap just to write a credential for one organization.
 
 ## Credential Modeling Preflight
 

package/src/templates/workspace-core/.agents/skills/secrets/SKILL.md

@@ -19,10 +19,17 @@ data, and generated extension/app content may mention credential **names** such
 as `OPENAI_API_KEY`, but must not contain real API keys, tokens, webhook URLs,
 signing secrets, OAuth refresh tokens, or private Builder/customer data.
 
-Secret values are supplied at runtime through deployment configuration, the
-encrypted `app_secrets` vault, `saveCredential` / `resolveCredential`, OAuth, or
-`${keys.NAME}` substitution. Examples must use obvious placeholders such as
-`<OPENAI_API_KEY>` or `${keys.SLACK_WEBHOOK}`, not real-looking copied values.
+Provider secret values are supplied at runtime through the encrypted
+`app_secrets` vault, `saveCredential` / `resolveCredential`, OAuth, or
+`${keys.NAME}` substitution. Deployment configuration is reserved for
+deploy-level secrets and non-provider configuration. Examples must use obvious
+placeholders such as `<OPENAI_API_KEY>` or `${keys.SLACK_WEBHOOK}`, not
+real-looking copied values.
+
+Provider credentials and provider account identifiers are workspace data. Use
+standard workspace connections and org/workspace vault scopes; never put them
+in `.env` or deployment environment variables, and never add a provider-specific
+action or startup bootstrap just to write a credential for one organization.
 
 ## Credential Modeling Preflight