@agent-native/core 0.120.0 → 0.120.2

package/corpus/README.md

@@ -28,6 +28,6 @@ rg -n "defineAction|useActionQuery" node_modules/@agent-native/core/corpus
 
 ## Generated Counts
 
-- core files: 1662
+- core files: 1663
 - toolkit files: 159
-- template files: 6334
+- template files: 6351

package/corpus/core/CHANGELOG.md

@@ -1,5 +1,21 @@
 # @agent-native/core
 
+## 0.120.2
+
+### Patch Changes
+
+- b00c38d: Emit the continuation handoff event after completion callbacks install server-driven continuations.
+- b00c38d: Keep generated chat template Settings and Manage agent links in the sidebar footer.
+- b00c38d: Move extension management into the shared Settings tabs and support embedded extension lists.
+- b00c38d: Preserve the full continuation reason when durable agent runs hand off to the next chunk.
+
+## 0.120.1
+
+### Patch Changes
+
+- 5477352: Keep Dispatch's overview composer, full-page chat, and side chat on the same selected model.
+- 5477352: Inject the configured Google Analytics tag into framework-owned login and signup pages.
+
 ## 0.120.0
 
 ### Minor Changes

package/corpus/core/docs/content/extensions.mdx

@@ -223,7 +223,7 @@ Pattern across all of these: extensions are about **the moment** the user is in
 
 The simple path:
 
-1. **Click "New Extension"** in the sidebar (or just ask in chat).
+1. Open **Settings → Extensions** (or just ask in chat), then click **New Extension**.
 2. **Describe what you want in one sentence.** "A sticky-note pad for the contact I'm emailing." "A KPI box for trials started this week."
 3. **The agent writes it and it appears in your Extensions list, ready to use.**
 
@@ -617,9 +617,23 @@ Extensions are private to the user who created them by default. To share:
 
 Shared extensions have their own URLs and plug into the same share dialog as documents, decks, and dashboards. Slot installs are always personal — sharing an extension means others _can_ install it; it doesn't auto-pin it to their UI.
 
-## Extensions vs. editing the app code {#vs-app-code}
+## Should I use an extension or edit the app code? {#vs-app-code}
 
-The framework lets the agent edit the app's source code directly — components, routes, styles. So when should you reach for an extension instead?
+The framework lets the agent edit the app's source code directly — components,
+routes, styles, and business logic. Use this question when either path could
+solve the request:
+
+- **Start with an extension** for a self-contained, relatively one-off widget:
+  a custom visualization or interaction, a dashboard tile, a standalone
+  utility, or an add-on in an existing slot. It is fast, requires no source
+  change, build, or deploy, and can be private or shared.
+- **Use app code** for a core feature of the template, a change to native UI,
+  layout, routes, or business logic, or anything that should be reused broadly
+  across dashboards or users. If the host has no suitable slot or the request
+  needs a new slot, use code.
+- **Promote repeated extensions.** If people keep rebuilding the same
+  extension, or maintaining copies in many places would be worse than one
+  shared implementation, move it into app code as a reusable native feature.
 
 |                       | Extension                                         | App code edit                        |
 | --------------------- | ------------------------------------------------- | ------------------------------------ |
@@ -630,7 +644,12 @@ The framework lets the agent edit the app's source code directly — components,
 | **Scope**             | One user (or shared with org)                     | The entire product, every user       |
 | **Best for**          | Personal widgets, custom KPIs, per-team utilities | Core features that ship to all users |
 
-Rule of thumb: **if it's for one user or one team, it's an extension.** If every user of the template should get it, ship it as a real feature.
+Rule of thumb: **if an extension can solve the problem, generally start there.**
+Use code when the extension boundary does not fit or when broad reuse and
+product-wide availability justify a native implementation. For example, a
+one-off custom visualization on a dashboard is a good extension; a new pie,
+multi-bar, or line chart type that should be available across dashboards
+belongs in the template code.
 
 If what you actually need is a cached, refreshable data source for an existing chart or table — not a new interactive widget — see [Data Programs](/docs/data-programs) instead; it shares this page's sandbox and security posture but has no UI of its own.
 

package/corpus/core/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.120.0",
+  "version": "0.120.2",
   "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": {

package/corpus/core/src/agent/production-agent.ts

@@ -6401,6 +6401,10 @@ export async function chainServerDrivenContinuation(opts: {
         terminalEvent: run.events.at(-1)?.event,
       })
       .catch(() => {});
+    run.continuationTerminalEvent = {
+      type: "auto_continue",
+      reason: continuationReason,
+    };
   } catch (chainErr) {
     // Chain dispatch failed — fail loud so the held row goes terminal
     // instead of spinning. The reaper would also catch it, but this is

package/corpus/core/src/agent/run-manager.ts

@@ -41,6 +41,16 @@ export interface ActiveRun {
   subscribers: Set<(event: RunEvent) => void>;
   abort: AbortController;
   abortReason?: string;
+  /**
+   * Terminal event to emit when a server-driven continuation has been handed
+   * off successfully. The continuation runs outside this process, so the
+   * normal loop-level auto_continue event is not sent through this run's
+   * `send` callback.
+   */
+  continuationTerminalEvent?: Extract<
+    AgentChatEvent,
+    { type: "auto_continue" }
+  >;
   startedAt: number;
 }
 
@@ -954,7 +964,17 @@ export function startRun(
       //    /runs/active check while we wait for SQL writes to land.
       let completionError: unknown = null;
       let terminalPersistenceError: unknown = null;
-      const terminalEvent = pendingTerminalEvent?.event ?? null;
+      const resolveTerminalEventForCompletion = () => {
+        const continuationTerminalEvent = run.continuationTerminalEvent
+          ? {
+              seq: run.events.length,
+              event: run.continuationTerminalEvent,
+            }
+          : null;
+        return continuationTerminalEvent ?? pendingTerminalEvent;
+      };
+      let terminalEventForCompletion = resolveTerminalEventForCompletion();
+      let terminalEvent = terminalEventForCompletion?.event ?? null;
       if (
         onComplete &&
         !(run.status === "aborted" && run.abortReason === "no_progress")
@@ -966,12 +986,12 @@ export function startRun(
               ? "errored"
               : run.status;
           const completionRun: ActiveRun =
-            pendingTerminalEvent || completionStatus !== run.status
+            terminalEventForCompletion || completionStatus !== run.status
               ? {
                   ...run,
                   status: completionStatus,
-                  events: pendingTerminalEvent
-                    ? [...run.events, pendingTerminalEvent]
+                  events: terminalEventForCompletion
+                    ? [...run.events, terminalEventForCompletion]
                     : run.events,
                 }
               : run;
@@ -986,6 +1006,12 @@ export function startRun(
         }
       }
 
+      // Server-driven continuation is installed by onComplete after the
+      // successor has been dispatched. Resolve the terminal event again so
+      // this chunk emits auto_continue instead of a misleading done event.
+      terminalEventForCompletion = resolveTerminalEventForCompletion();
+      terminalEvent = terminalEventForCompletion?.event ?? null;
+
       // 2. Compute final status. If the completion callback threw, we'd
       //    rather mark the run errored than claim success with incomplete
       //    thread_data.
@@ -1022,18 +1048,18 @@ export function startRun(
         // re-stamp the seq at emit time (max-seq+1) just below.
         const terminalEvent: AgentChatEvent =
           finalStatus === "completed"
-            ? (pendingTerminalEvent?.event ?? { type: "done" })
-            : pendingTerminalEvent?.event.type === "error" ||
-                pendingTerminalEvent?.event.type === "missing_api_key"
-              ? pendingTerminalEvent.event
-              : pendingTerminalEvent?.event.type === "auto_continue"
+            ? (terminalEventForCompletion?.event ?? { type: "done" })
+            : terminalEventForCompletion?.event.type === "error" ||
+                terminalEventForCompletion?.event.type === "missing_api_key"
+              ? terminalEventForCompletion.event
+              : terminalEventForCompletion?.event.type === "auto_continue"
                 ? // The run was checkpointed at a soft-timeout/loop boundary and
                   // is recoverable: the partial turn is in agent_run_events and
                   // the continuation run will re-attempt the thread_data save.
                   // Even though the completion save failed (finalStatus stays
                   // "errored" for SQL/diagnostics), re-emit the auto_continue so
                   // the client resumes instead of seeing a dead chat.
-                  pendingTerminalEvent.event
+                  terminalEventForCompletion.event
                 : {
                     type: "error",
                     error: completionError

package/corpus/core/src/agent/types.ts

@@ -167,6 +167,7 @@ export interface AgentChatRequest {
     continuationReason?:
       | "run_timeout"
       | "loop_limit"
+      | "max_tokens"
       | "no_progress"
       | "stream_ended"
       | "gateway_timeout"
@@ -371,6 +372,7 @@ export type AgentChatEvent =
       reason:
         | "run_timeout"
         | "loop_limit"
+        | "max_tokens"
         | "no_progress"
         | "stream_ended"
         | "gateway_timeout"

package/corpus/core/src/client/MultiTabAssistantChat.tsx

@@ -56,6 +56,7 @@ import { isTrustedFrameMessage } from "./frame.js";
 import { RunStuckBanner } from "./RunStuckBanner.js";
 import { callAction } from "./use-action.js";
 import { useChangeVersion } from "./use-change-version.js";
+import { CHAT_MODEL_SELECTION_CHANGED_EVENT } from "./use-chat-models.js";
 import {
   useChatThreads,
   type ChatThreadScope,
@@ -138,6 +139,13 @@ function writeStoredModelSelection(key: string, selection: ModelSelection) {
   if (typeof window === "undefined") return;
   try {
     window.localStorage.setItem(key, JSON.stringify(selection));
+    queueMicrotask(() => {
+      window.dispatchEvent(
+        new CustomEvent(CHAT_MODEL_SELECTION_CHANGED_EVENT, {
+          detail: { key },
+        }),
+      );
+    });
   } catch {}
 }
 
@@ -954,6 +962,43 @@ export function MultiTabAssistantChat({
   const bumpModelSelectionVersion = useCallback(() => {
     setModelSelectionVersion((version) => version + 1);
   }, []);
+
+  useEffect(() => {
+    if (typeof window === "undefined") return;
+
+    const syncPersistedSelection = (event?: Event) => {
+      const detail = (event as CustomEvent<{ key?: string }> | undefined)
+        ?.detail;
+      if (detail?.key && detail.key !== modelSelectionKey) return;
+
+      const next = readStoredModelSelection(modelSelectionKey);
+      if (!next) return;
+
+      const activeThreadId = activeThreadIdRef.current;
+      if (activeThreadId) {
+        threadModelRef.current.set(activeThreadId, next);
+      }
+      setPersistedModelSelection(next);
+      bumpModelSelectionVersion();
+    };
+    const handleStorage = (event: StorageEvent) => {
+      if (event.key === modelSelectionKey) syncPersistedSelection();
+    };
+
+    window.addEventListener(
+      CHAT_MODEL_SELECTION_CHANGED_EVENT,
+      syncPersistedSelection,
+    );
+    window.addEventListener("storage", handleStorage);
+    return () => {
+      window.removeEventListener(
+        CHAT_MODEL_SELECTION_CHANGED_EVENT,
+        syncPersistedSelection,
+      );
+      window.removeEventListener("storage", handleStorage);
+    };
+  }, [bumpModelSelectionVersion, modelSelectionKey]);
+
   const postMessageSubmissionsDisabled = props.composerDisabled === true;
 
   const setContextInTab = useCallback(

package/corpus/core/src/client/extensions/ExtensionsListPage.tsx

@@ -99,7 +99,14 @@ function CreateToolInput({ className }: { className?: string }) {
   );
 }
 
-export function ExtensionsListPage() {
+export interface ExtensionsListPageProps {
+  /** Skip the standalone extensions navigation state when embedded in Settings. */
+  embedded?: boolean;
+}
+
+export function ExtensionsListPage({
+  embedded = false,
+}: ExtensionsListPageProps = {}) {
   const t = useT();
   const [showCreate, setShowCreate] = useState(false);
   const [confirmDeleteId, setConfirmDeleteId] = useState<string | null>(null);
@@ -111,12 +118,13 @@ export function ExtensionsListPage() {
   );
 
   useEffect(() => {
+    if (embedded) return;
     fetch(agentNativePath("/_agent-native/application-state/navigation"), {
       method: "PUT",
       headers: { "Content-Type": "application/json" },
       body: JSON.stringify({ view: "extensions" }),
     }).catch(() => {});
-  }, []);
+  }, [embedded]);
 
   useEffect(() => {
     if (typeof window === "undefined") return;
@@ -189,7 +197,12 @@ export function ExtensionsListPage() {
   };
 
   return (
-    <div className="flex h-full w-full flex-col">
+    <div
+      className={cn(
+        "flex w-full flex-col",
+        embedded ? "min-h-[28rem]" : "h-full",
+      )}
+    >
       <header className="flex h-12 items-center justify-between border-b px-4 shrink-0">
         <div className="flex items-center gap-2">
           <h1 className="text-sm font-semibold">{t("extensions.title")}</h1>

package/corpus/core/src/client/settings/ExtensionsSettingsContent.tsx

@@ -0,0 +1,24 @@
+import { IconLoader2 } from "@tabler/icons-react";
+import { lazy, Suspense } from "react";
+
+const ExtensionsListPage = lazy(() =>
+  import("../extensions/ExtensionsListPage.js").then((module) => ({
+    default: module.ExtensionsListPage,
+  })),
+);
+
+export function ExtensionsSettingsContent() {
+  return (
+    <div className="mx-auto w-full max-w-5xl overflow-hidden rounded-lg border border-border bg-background">
+      <Suspense
+        fallback={
+          <div className="flex min-h-[28rem] items-center justify-center text-muted-foreground">
+            <IconLoader2 className="size-5 animate-spin" aria-label="Loading" />
+          </div>
+        }
+      >
+        <ExtensionsListPage embedded />
+      </Suspense>
+    </div>
+  );
+}

package/corpus/core/src/client/settings/SettingsPanel.tsx

@@ -29,6 +29,7 @@ import {
   IconGauge,
   IconApps,
   IconUsersGroup,
+  IconTool,
 } from "@tabler/icons-react";
 import React, {
   Suspense,
@@ -67,6 +68,7 @@ import {
 import { AgentsSection } from "./AgentsSection.js";
 import { AutomationsSection } from "./AutomationsSection.js";
 import { DemoModeSection } from "./DemoModeSection.js";
+import { ExtensionsSettingsContent } from "./ExtensionsSettingsContent.js";
 import { SecretsSection } from "./SecretsSection.js";
 import {
   SettingsSection,
@@ -3037,6 +3039,14 @@ export function useAgentSettingsTabs(): SettingsTabItem[] {
           />
         ),
       },
+      {
+        id: "extensions",
+        label: "Extensions",
+        icon: IconTool,
+        group: "workspace",
+        keywords: "extensions widgets mini apps tools sandboxed apps",
+        content: <ExtensionsSettingsContent />,
+      },
     ];
   }, [baseProps]);
 }

package/corpus/core/src/client/use-chat-models.ts

@@ -42,6 +42,8 @@ interface Options {
 }
 
 const DEFAULT_STORAGE_KEY = "agent-native:chat-models:selection";
+export const CHAT_MODEL_SELECTION_CHANGED_EVENT =
+  "agent-native:chat-model-selection-changed";
 
 interface PersistedSelection {
   model?: string;
@@ -63,6 +65,13 @@ function writePersisted(key: string | null, value: PersistedSelection) {
   if (!key || typeof window === "undefined") return;
   try {
     window.localStorage.setItem(key, JSON.stringify(value));
+    queueMicrotask(() => {
+      window.dispatchEvent(
+        new CustomEvent(CHAT_MODEL_SELECTION_CHANGED_EVENT, {
+          detail: { key },
+        }),
+      );
+    });
   } catch {}
 }
 
@@ -110,6 +119,42 @@ export function useChatModels({
     };
   }, [selectedEffort, selectedEngine, selectedModel]);
 
+  useEffect(() => {
+    if (!storageKey || typeof window === "undefined") return;
+
+    const syncPersistedSelection = (event?: Event) => {
+      const detail = (event as CustomEvent<{ key?: string }> | undefined)
+        ?.detail;
+      if (detail?.key && detail.key !== storageKey) return;
+
+      const next = readPersisted(storageKey);
+      if (!next.model) return;
+
+      hasExplicitSelectionRef.current = true;
+      setSelectedModel(next.model);
+      setSelectedEngine(next.engine ?? "");
+      setSelectedEffort(
+        resolveReasoningEffortSelection(next.model, next.effort),
+      );
+    };
+    const handleStorage = (event: StorageEvent) => {
+      if (event.key === storageKey) syncPersistedSelection();
+    };
+
+    window.addEventListener(
+      CHAT_MODEL_SELECTION_CHANGED_EVENT,
+      syncPersistedSelection,
+    );
+    window.addEventListener("storage", handleStorage);
+    return () => {
+      window.removeEventListener(
+        CHAT_MODEL_SELECTION_CHANGED_EVENT,
+        syncPersistedSelection,
+      );
+      window.removeEventListener("storage", handleStorage);
+    };
+  }, [storageKey]);
+
   const onModelChange = useCallback(
     (model: string, engine: string) => {
       hasExplicitSelectionRef.current = true;

package/corpus/core/src/deploy/build.ts

@@ -3708,6 +3708,9 @@ export default bundle;
       "process.env.AGENT_NATIVE_BUILD_GA_MEASUREMENT_ID": JSON.stringify(
         process.env.GA_MEASUREMENT_ID?.trim() || "",
       ),
+      "process.env.AGENT_NATIVE_BUILD_GTM_CONTAINER_ID": JSON.stringify(
+        process.env.GTM_CONTAINER_ID?.trim() || "",
+      ),
       "process.env.AGENT_NATIVE_BUILD_DEPLOY_CONTEXT": JSON.stringify(
         process.env.CONTEXT?.trim() || "",
       ),