@agent-native/core 0.165.0 → 0.165.2

package/corpus/templates/clips/chrome-extension/src/background.ts

@@ -6,6 +6,10 @@ import {
   shouldReconcilePersistedRecording,
   type OffscreenRecordingState,
 } from "./native-recording-state";
+import {
+  sendWithInjectionFallback,
+  shouldFollowOverlay,
+} from "./overlay-follow";
 import { captureExtensionError, initExtensionSentry } from "./sentry";
 
 initExtensionSentry("background");
@@ -276,16 +280,11 @@ let overlayBaseEpochMs = 0;
 // up, for both camera-only AND screen+camera recording (recordingShowsBubble).
 let overlayShowsBubble = false;
 let recordingShowsBubble = false;
-// Cross-tab follow: when true, the overlay is pushed to whatever tab the user
-// switches to mid-recording. That requires "<all_urls>" + a declarative content
-// script, which triggers Chrome's broad-host in-depth review. Shipped OFF
-// (activeTab-only: the overlay lives on the launch tab the user invoked the
-// extension from). Capture is unaffected — it runs in the offscreen document via
-// getDisplayMedia regardless. See PERMISSIONS.md to re-enable.
-// Typed `boolean` (not inferred literal `false`) so the cross-tab branches below
-// don't read as unreachable code; flip the value to re-enable. See PERMISSIONS.md.
-const CROSS_TAB_FOLLOW: boolean = false;
-// The tab the recording was launched from — the only tab activeTab lets us touch.
+// Cross-tab follow stays enabled for the next release. It needs the manifest's
+// broad-host review path (`<all_urls>` + declarative content script coverage) so
+// the face bubble and controls keep following the user across tabs and reloads.
+const CROSS_TAB_FOLLOW: boolean = true;
+// The launch tab stays the anchor for the explicit reload recovery path.
 let overlayTabId: number | null = null;
 let countdownEndsAtMs = 0;
 let armingNativeRecordingSessionId: string | null = null;
@@ -438,20 +437,19 @@ async function restoreRuntimeState(): Promise<void> {
 function sendTabMessage(
   tabId: number,
   message: Record<string, unknown>,
-): Promise<void> {
+): Promise<boolean> {
   return new Promise((resolve) => {
     try {
       chrome.tabs.sendMessage(tabId, message, () => {
-        void chrome.runtime.lastError;
-        resolve();
+        resolve(!chrome.runtime.lastError);
       });
     } catch {
-      resolve();
+      resolve(false);
     }
   });
 }
 
-async function ensureContentScript(tabId: number): Promise<void> {
+async function injectContentScript(tabId: number): Promise<boolean> {
   const scripting = (
     chrome as typeof chrome & {
       scripting?: {
@@ -462,18 +460,32 @@ async function ensureContentScript(tabId: number): Promise<void> {
       };
     }
   ).scripting;
-  if (!scripting) return;
-  await scripting
-    .executeScript({ target: { tabId }, files: ["assets/content-script.js"] })
-    .catch(() => undefined);
+  if (!scripting) return false;
+  try {
+    await scripting.executeScript({
+      target: { tabId },
+      files: ["assets/content-script.js"],
+    });
+    return true;
+  } catch {
+    // Unsupported pages (chrome://, the Chrome Web Store, and similar) reject
+    // injection. They still need to record without an in-page overlay.
+    return false;
+  }
 }
 
-async function mountOverlayOnTab(tabId: number): Promise<void> {
-  await ensureContentScript(tabId);
-  await sendTabMessage(tabId, {
-    type: "CLIPS_OVERLAY_MOUNT",
-    parts: desiredParts(),
-  });
+async function mountOverlayOnTab(
+  tabId: number,
+  parts: OverlayPart[] = desiredParts(),
+): Promise<boolean> {
+  return sendWithInjectionFallback(
+    () =>
+      sendTabMessage(tabId, {
+        type: "CLIPS_OVERLAY_MOUNT",
+        parts,
+      }),
+    () => injectContentScript(tabId),
+  );
 }
 
 function allTabs(): Promise<chrome.tabs.Tab[]> {
@@ -483,9 +495,8 @@ function allTabs(): Promise<chrome.tabs.Tab[]> {
 }
 
 async function broadcastMount(): Promise<void> {
-  // activeTab-only: keep the overlay on the launch tab (re-ensures the injected
-  // content script too, so it survives a worker suspend). Cross-tab broadcast is
-  // gated behind CROSS_TAB_FOLLOW because it needs broad host access.
+  // Cross-tab follow uses the declarative content script path, so every mounted
+  // tab can receive the current overlay parts and survive reloads.
   if (!CROSS_TAB_FOLLOW) {
     if (overlayTabId !== null) await mountOverlayOnTab(overlayTabId);
     return;
@@ -548,12 +559,9 @@ async function startPreview(wantsCamera: boolean): Promise<void> {
   if (!tab || typeof tab.id !== "number") return;
   if (previewTabId !== null && previewTabId !== tab.id) await stopPreview();
   previewTabId = tab.id;
-  await ensureContentScript(tab.id);
-  // Injection / send fail silently on unsupported pages (chrome://, etc.).
-  await sendTabMessage(tab.id, {
-    type: "CLIPS_OVERLAY_MOUNT",
-    parts: ["bubble"],
-  });
+  // Message delivery reuses the declarative script; fallback injection fails
+  // silently on unsupported pages (chrome://, the Web Store, and similar).
+  await mountOverlayOnTab(tab.id, ["bubble"]);
 }
 
 async function stopPreview(): Promise<void> {
@@ -2560,29 +2568,40 @@ async function dispatchRuntimeMessage(message: unknown): Promise<unknown> {
   }
 }
 
-// While a recording is active, keep the overlay following the user as they
-// switch tabs (programmatic injection covers tabs opened before the extension
-// loaded; declared content scripts cover navigations).
+// While a recording is active or arming, keep the overlay following the user as
+// they switch tabs. The message-first path reuses declarative scripts and only
+// injects for tabs that predate the extension or otherwise have no receiver.
 chrome.tabs.onActivated.addListener((info) => {
-  if (!CROSS_TAB_FOLLOW) return; // activeTab-only: overlay stays on the launch tab
+  if (!CROSS_TAB_FOLLOW) return;
   void (async () => {
     await ensureRestored();
-    if (overlayPhase === "idle" || !activeNativeRecording) return;
+    if (
+      !shouldFollowOverlay(
+        overlayPhase,
+        Boolean(activeNativeRecording),
+        Boolean(armingNativeRecordingSessionId),
+      )
+    )
+      return;
     await mountOverlayOnTab(info.tabId);
   })();
 });
 
-// The overlay content script is injected on demand (activeTab), so reloading the
-// launch tab wipes it — the camera bubble and toolbar would vanish for the rest
-// of the recording even though capture keeps running in the offscreen document.
-// Re-inject and re-mount once the launch tab finishes reloading while a recording
-// is active. Scoped to the launch tab (the only tab activeTab lets us touch); a
-// same-URL reload keeps that grant.
+// Keep the launch tab in sync after a reload. Declarative follow covers the
+// other tabs; this is the explicit recovery path for the tab that originally
+// started the recording.
 chrome.tabs.onUpdated.addListener((tabId, changeInfo) => {
   if (changeInfo.status !== "complete") return;
   void (async () => {
     await ensureRestored();
-    if (overlayPhase === "idle" || !activeNativeRecording) return;
+    if (
+      !shouldFollowOverlay(
+        overlayPhase,
+        Boolean(activeNativeRecording),
+        Boolean(armingNativeRecordingSessionId),
+      )
+    )
+      return;
     if (tabId !== overlayTabId) return;
     await mountOverlayOnTab(tabId);
     broadcastOverlayState();

package/corpus/templates/clips/chrome-extension/src/content-script.ts

@@ -1,12 +1,10 @@
-// Loom-style in-page overlay host. The background service worker injects this
-// into the LAUNCH TAB on demand via chrome.scripting.executeScript (covered by
-// the activeTab permission the user grants when they click the extension), NOT
-// declaratively on every page — that would need broad "<all_urls>" host access
-// and Chrome's in-depth review. So the overlay lives on the tab the recording
-// was started from; it does not follow across tabs unless CROSS_TAB_FOLLOW is
-// re-enabled in background.ts (see PERMISSIONS.md). Wrapped in an IIFE so it
-// emits a single self-contained classic script with no module imports/exports
-// and leaks no names into the shared global scope. Its only job is to
+// Loom-style in-page overlay host. The next release declares this on every page
+// so the face bubble and controls can survive tab switches and navigations; the
+// background worker can also inject it into the launch tab for immediate and
+// reload recovery. That broad "<all_urls>" host access is the Chrome Web Store
+// in-depth review boundary. Wrapped in an IIFE so it emits a single self-contained
+// classic script with no module imports/exports and leaks no names into the shared
+// global scope. Its only job is to
 // mount/unmount the overlay iframes; all UI and control logic lives inside the
 // extension-origin overlay pages (src/overlay.html). The worker is the source of
 // truth for which "parts" are visible and pushes them here.
@@ -18,6 +16,12 @@
   const ALL_PARTS: OverlayPart[] = ["bubble", "countdown", "toolbar", "saving"];
   const flags = window as unknown as { __clipsOverlayHostReady?: boolean };
 
+  // Declarative and recovery injection can target the same document. Return
+  // before any side effects so global listeners remain one-per-page.
+  if (flags.__clipsOverlayHostReady) return;
+  flags.__clipsOverlayHostReady = true;
+  let recordingActive = false;
+
   function errorPayload(error: unknown): {
     name: string;
     message: string;
@@ -40,6 +44,7 @@
     error: unknown,
     context: Record<string, unknown> = {},
   ): void {
+    if (!recordingActive) return;
     try {
       chrome.runtime.sendMessage(
         {
@@ -73,6 +78,15 @@
     });
   });
 
+  try {
+    chrome.storage.onChanged.addListener((changes, areaName) => {
+      if (areaName !== "local" || !changes.clipsRecordingActive) return;
+      recordingActive = changes.clipsRecordingActive.newValue === true;
+    });
+  } catch {
+    /* storage unavailable */
+  }
+
   // ----- Draggable, resizable camera bubble ---------------------------------
   // Size + position persist in storage so the bubble stays where the user put it
   // across pages and recordings (like the desktop app). The iframe can't move or
@@ -339,7 +353,8 @@
     try {
       chrome.storage.local.get("clipsRecordingActive", (value) => {
         if (chrome.runtime.lastError) return;
-        if (value && value.clipsRecordingActive) requestState();
+        recordingActive = value?.clipsRecordingActive === true;
+        if (recordingActive) requestState();
       });
     } catch {
       /* ignore */
@@ -593,13 +608,6 @@
     lastWantedParts = wanted;
   }
 
-  // Guard against rare double-injection (SPA soft-reloads re-running the script).
-  if (flags.__clipsOverlayHostReady) {
-    syncIfRecording();
-    return;
-  }
-  flags.__clipsOverlayHostReady = true;
-
   chrome.runtime.onMessage.addListener((message) => {
     if (!message || typeof message !== "object") return;
     const type = (message as { type?: unknown }).type;

package/corpus/templates/clips/chrome-extension/src/overlay-follow.ts

@@ -0,0 +1,25 @@
+export type OverlayFollowPhase =
+  | "idle"
+  | "countdown"
+  | "recording"
+  | "paused"
+  | "saving";
+
+export function shouldFollowOverlay(
+  phase: OverlayFollowPhase,
+  hasActiveNativeRecording: boolean,
+  hasArmingNativeRecording: boolean,
+): boolean {
+  return (
+    phase !== "idle" && (hasActiveNativeRecording || hasArmingNativeRecording)
+  );
+}
+
+export async function sendWithInjectionFallback(
+  sendMessage: () => Promise<boolean>,
+  injectContentScript: () => Promise<boolean>,
+): Promise<boolean> {
+  if (await sendMessage()) return true;
+  if (!(await injectContentScript())) return false;
+  return sendMessage();
+}

package/corpus/templates/content/CHANGELOG.md

@@ -3,8 +3,51 @@
 All notable user-facing changes to Agent-Native Content are documented here. Open it any
 time from the command menu (Cmd+K → "What's new").
 
-## 2026-06-23
+Older updates live in [the changelog folder](./changelog/) and are included in the in-app "What's new" view.
+
+## 2026-08-14
+
+### Fixed
+
+- Images fill the page width by default and remain visible when more images are added
+- Images inserted from the slash command stay saved after upload
+- SVG files can be selected reliably from the image picker
+
+## 2026-08-13
+
+### Fixed
+
+- Blocks field conflicts now keep the newer saved version visible instead of leaving a rejected edit on screen
+
+## 2026-08-12
+
+### Improved
+
+- Toggle blocks now follow Notion-style Enter and Shift-Tab behavior while preserving summaries and nested paragraphs.
+- Shared Content documents now keep viewers read-only and let commenters add comments without editing the document.
+
+### Fixed
+
+- Image uploads now confirm the image can be displayed before reporting success
+
+## 2026-08-11
+
+### Improved
+
+- Content opens your last page on return and gives new users a private welcome page.
+
+### Fixed
+
+- Chrome no longer offers to install Content as a desktop app.
+- Content mutations delegated from verified Slack DMs now use the member's exact Personal scope and return verified row receipts.
+
+## 2026-08-10
 
 ### Added
 
-- See what's new right inside Agent-Native Content — a changelog now lives in the command menu (Cmd+K).
+- Agents can safely insert, update, upsert, delete, and reorder one stable block in a database Blocks field.
+
+### Improved
+
+- Database Blocks fields now keep logical block identity through editing, reordering, deletion recovery, and reloads
+- Database row actions now validate exact schemas and safe retries before changing data.

package/corpus/templates/crm/CHANGELOG.md

@@ -1,25 +1,37 @@
 # CRM changelog
 
-## 2026-07-26
+Older updates live in [the changelog folder](./changelog/) and are included in the in-app "What's new" view.
 
-### Added
-
-- CRM connects to HubSpot for scoped account intelligence, saved views, follow-up tasks, evidence, and approval-gated write proposals.
-- CRM can prepare a record-scoped, default-off Clips review recipe while keeping media and transcripts in Clips.
-- CRM can now find and review evidence-grounded call signals without storing transcripts or media.
-- Approved sales automations can now update routine local CRM fields while provider changes remain reviewable proposals.
-- CRM can now run as a standalone Native SQL system for accounts, people, opportunities, views, tasks, and cadence without an external provider.
-- Pipeline now gives each CRM user a live, permission-aware view of opportunity value by stage.
-- CRM can now connect to Salesforce alongside HubSpot for scoped account intelligence and follow-up work.
+## 2026-08-11
 
 ### Improved
 
-- CRM can now manage keyword and smart call-signal trackers from Intelligence settings.
+- Full-page chat composers stay at a focused 750px width.
 
 ### Fixed
 
-- Pipeline dashboards now install correctly from the CRM action CLI.
-- CRM field validation now explains which fields cannot be edited instead of showing a generic error.
-- Fixed HubSpot contact syncs missing records updated after the sync cursor.
-- Fixed Pipeline dashboard panels so their opportunity data loads reliably.
-- Full-page chat keeps the active conversation when moving to and from the sidebar.
+- Chrome no longer offers to install CRM as a desktop app.
+
+## 2026-08-10
+
+### Improved
+
+- Full-page chat now uses the available width up to 1000px for more comfortable prompts and responses.
+
+## 2026-08-07
+
+### Improved
+
+- CRM settings show stable skeleton placeholders while lists, fields, connections, and intelligence trackers load.
+
+## 2026-08-06
+
+### Improved
+
+- CRM starts faster after a deploy or idle period — one-time data backfills now run once as tracked migrations instead of on every cold start.
+
+## 2026-07-29
+
+### Improved
+
+- Sidebar footers now keep Feedback, Search, and Collapse together, with language preferences available in Settings.

package/corpus/templates/design/CHANGELOG.md

@@ -3,8 +3,60 @@
 All notable user-facing changes to Design are documented here. Open it any time
 from the command menu (Cmd+K → "What's new") or from Settings.
 
-## 2026-06-23
+Older updates live in [the changelog folder](./changelog/) and are included in the in-app "What's new" view.
+
+## 2026-08-18
+
+### Improved
+
+- Design chat keeps context out of the composer and uses shorter completion summaries.
+
+### Changed
+
+- Advanced Design editor panels are hidden by default while they are refined.
+
+## 2026-08-13
 
 ### Added
 
-- See what's new right inside Design — a changelog now lives in the command menu (Cmd+K) and in Settings.
+- The design audit now catches a screen that renders behind a full-frame Alpine overlay — the failure a screenshot cannot show, because the capture waits for Alpine to settle and the overlay is gone by then.
+- The design audit now reports when a screen uses none of its linked design system's fonts, colors, or token names.
+
+### Improved
+
+- Attach a UI screenshot and the design is reproduced from it instead of being reinterpreted as three alternative directions.
+- The design system preview now shows how many named tokens were captured, so a large imported system no longer looks like a handful of colors.
+
+### Fixed
+
+- A screen whose Alpine overlay would cover it on load — `x-cloak` without its hiding rule, or a broken Alpine script URL — is now caught when it is saved instead of shipping as a blank or covered design.
+- Linking a design system means you never get generic direction cards: exploring variants without real HTML is now refused for that design rather than rendering placeholder screens that ignore your tokens.
+- Your design system, original prompt, and reference screenshots now reach the turn that actually generates the design, instead of being spent on the questions step.
+
+## 2026-08-12
+
+### Improved
+
+- Shared designs now keep viewers read-only and let commenters add review comments without editing the design.
+
+## 2026-08-11
+
+### Improved
+
+- Design sharing now identifies viewers who can add review comments
+- New designs now skip the intake questions and follow your existing work when Creative Context already holds closely related pieces.
+
+### Fixed
+
+- Chrome no longer offers to install Design as a desktop app.
+- Design agent prompts copy successfully in the desktop app.
+
+## 2026-08-10
+
+### Improved
+
+- The frame tool draws a plain frame by default, with Screen available in its dropdown
+
+### Fixed
+
+- Marquee-selecting layers far down a tall screen now selects the layers you dragged over

package/corpus/templates/dispatch/CHANGELOG.md

@@ -3,8 +3,57 @@
 All notable user-facing changes to Agent-Native Dispatch are documented here. Open it any
 time from the command menu (Cmd+K → "What's new").
 
-## 2026-06-23
+Older updates live in [the changelog folder](./changelog/) and are included in the in-app "What's new" view.
+
+## 2026-08-20
+
+### Fixed
+
+- Dispatch chat now loads its OpenRouter provider reliably in production.
+
+## 2026-08-12
+
+### Improved
+
+- Search and pin workspace apps from the app catalog
+- Workspace integration access now shows exactly which apps can reuse each connection.
+
+### Fixed
+
+- Dispatch now appears in authorized workspace app directories for fleet-wide administration
+
+## 2026-08-11
+
+### Added
+
+- Dispatch shows usage trends, recent prompts, and an agent review path
+
+### Improved
+
+- Dispatch no longer shows the generic Chat starter among default app launchers
+- Dispatch settings now link directly to Admin
+- New apps accept human-friendly names and convert them to URL-safe IDs automatically.
+- Integrations and scheduled work open as first-class Electron pages without a duplicate Dispatch navigation shell.
+- Sidebar text is slightly easier to read in light and dark mode.
+
+### Fixed
+
+- Chrome no longer offers to install Dispatch as a desktop app.
+- Clicking the Dispatch logo returns to the Overview page
+- Dispatch omits its own app entry from the app switcher.
+
+## 2026-08-10
+
+### Added
+
+- Desktop workspace sign-in can now be rolled out gradually while ordinary app sign-in remains unchanged by default.
+
+### Improved
+
+- Full-page chat now uses the available width up to 1000px for more comfortable prompts and responses.
+
+## 2026-08-08
 
 ### Added
 
-- See what's new right inside Agent-Native Dispatch — a changelog now lives in the command menu (Cmd+K).
+- Chat-first navigation keeps conversations central while opening workspace apps and watched sessions beside them.

package/corpus/templates/dispatch/changelog/2026-08-20-dispatch-chat-loads-openrouter-provider-reliably.md

@@ -0,0 +1,6 @@
+---
+type: fixed
+date: 2026-08-20
+---
+
+Dispatch chat now loads its OpenRouter provider reliably in production.

package/corpus/templates/dispatch/package.json

@@ -19,9 +19,11 @@
     "@agent-native/toolkit": "workspace:*",
     "@fontsource-variable/inter": "^5.2.8",
     "@libsql/client": "^0.15.8",
+    "@openrouter/ai-sdk-provider": "^2.9.1",
     "@radix-ui/react-tooltip": "^1.2.7",
     "@tabler/icons-react": "catalog:",
     "@tanstack/react-query": "^5.99.2",
+    "ai": "6.0.258",
     "h3": "catalog:",
     "isbot": "^5",
     "next-themes": "^0.4.6",

package/corpus/templates/factory/CHANGELOG.md

@@ -3,8 +3,34 @@
 All notable user-facing changes to Chat are documented here. Open it any
 time from the command menu (Cmd+K → "What's new").
 
-## 2026-06-23
+Older updates live in [the changelog folder](./changelog/) and are included in the in-app "What's new" view.
+
+## 2026-08-11
+
+### Fixed
+
+- Chrome no longer offers to install Factory as a desktop app.
+
+## 2026-08-10
+
+### Improved
+
+- Full-page chat now uses the available width up to 1000px for more comfortable prompts and responses.
+
+## 2026-08-08
+
+### Improved
+
+- Scheduler health now stays in Settings until diagnostics are needed.
+
+## 2026-08-07
 
 ### Added
 
-- See what's new right inside Chat — a changelog now lives in the command menu (Cmd+K).
+- Factory can keep Builder bot pull requests moving by requesting fixes for review feedback, CI failures, and merge conflicts.
+
+## 2026-08-05
+
+### Improved
+
+- Factory now keeps production automations running, shows scheduler health and run errors, and can email failure diagnostics.

package/corpus/templates/forms/CHANGELOG.md

@@ -3,8 +3,44 @@
 All notable user-facing changes to Agent-Native Forms are documented here. Open it any
 time from the command menu (Cmd+K → "What's new").
 
-## 2026-06-23
+Older updates live in [the changelog folder](./changelog/) and are included in the in-app "What's new" view.
 
-### Added
+## 2026-08-11
 
-- See what's new right inside Agent-Native Forms — a changelog now lives in the command menu (Cmd+K).
+### Improved
+
+- Full-page chat composers stay at a focused 750px width.
+
+### Fixed
+
+- Chrome no longer offers to install Forms as a desktop app.
+- Fixed public forms so conditional questions stay hidden until relevant and submissions retain a safe page link.
+
+## 2026-08-10
+
+### Improved
+
+- Full-page chat now uses the available width up to 1000px for more comfortable prompts and responses.
+
+### Fixed
+
+- Forms now keep agent-applied field changes visible after an edit
+- Published form links always use the working public form URL
+
+## 2026-08-06
+
+### Improved
+
+- Long-running form requests now continue in the background instead of stopping at the foreground time limit.
+
+## 2026-08-05
+
+### Fixed
+
+- Form links can now be Cmd-clicked to open in a new tab
+
+## 2026-07-31
+
+### Improved
+
+- The Agent Native logo stays visible when the sidebar is collapsed and toggles the sidebar when clicked.

package/corpus/templates/macros/CHANGELOG.md

@@ -3,8 +3,36 @@
 All notable user-facing changes to Agent-Native Macros are documented here. Open it any
 time from the command menu (Cmd+K → "What's new").
 
-## 2026-06-23
+Older updates live in [the changelog folder](./changelog/) and are included in the in-app "What's new" view.
+
+## 2026-07-29
+
+### Improved
+
+- Sidebar footers now keep Feedback, Search, and Collapse together without a separate language shortcut.
+
+## 2026-07-25
+
+### Improved
+
+- App branding now uses the product name without the Agent-Native prefix.
+- Settings navigation now keeps Manage agent as a dedicated linked destination at the bottom.
+
+## 2026-07-24
+
+### Improved
+
+- Secondary controls and dashboard surfaces now use quieter borderless styling.
+- Sidebar utility controls now follow a consistent footer order.
+
+## 2026-07-22
+
+### Improved
+
+- Manage agent navigation now uses the connected-nodes icon.
+
+## 2026-07-13
 
 ### Added
 
-- See what's new right inside Agent-Native Macros — a changelog now lives in the command menu (Cmd+K).
+- New Agent page: see and manage your agent's context, files, connections, jobs, and external access in one place