@agent-native/core 0.194.0-nightly-20260927082735 → 0.194.0

package/corpus/README.md

@@ -31,4 +31,4 @@ rg -n "defineAction|useActionQuery" node_modules/@agent-native/core/corpus
 
 ## Generated Counts
 
-- template files: 10317
+- template files: 10319

package/corpus/templates/analytics/.agents/skills/agent-native-toolkit/SKILL.md

@@ -61,10 +61,11 @@ The repeated app shell has two distinct navigation surfaces:
   recommendation, synthesis, visible progress, or steering, route the button
   to the AgentSidebar and let the agent call focused actions. Keep revisions in
   the same thread instead of adding a second freeform prompt box.
-- Standalone apps with `AgentSidebar` must resolve one assistant-ui runtime
-  context. Match direct assistant-ui pins to the installed core/toolkit peer
-  graph, use Vite dedupe/aliases when linked dependencies can split contexts,
-  and verify an AI handoff produces no stale-index console error.
+- Standalone apps with `AgentSidebar` must use the shared AgentKit chat surface
+  and one AgentKit controller/transport. Do not mount the legacy `AssistantChat`
+  renderer or create a second chat stream owner. Keep assistant-ui imports inside
+  the shared composer integration; when linked dependencies need Vite aliases,
+  resolve one `@agent-native/agentkit` context and verify a real handoff.
 
 Contextual agent UI is not a reason to expose every option at once. Start with
 the domain task's primary action, reveal review or configuration only when the

package/corpus/templates/analytics/.agents/skills/turn-into-app/SKILL.md

@@ -228,11 +228,12 @@ Generated apps must follow the shared Agent-Native surface model:
 - Choose a named visual direction in `DESIGN.md` before styling and build to it.
   Preserve existing brand tokens; a new unbranded app picks its own
   product-fitting palette rather than inheriting a sibling app's accent.
-- Standalone apps that render `AgentSidebar` must keep one assistant-ui runtime
-  context. Pin the versions compatible with the installed core/toolkit peer
-  graph, and add Vite dedupe/aliases when linked or transitive packages resolve
-  duplicate assistant-ui modules. Verify a fresh AI handoff has no
-  `AssistantUiStaleIndexErrorBoundary` or stale-index console error.
+- Standalone apps that render `AgentSidebar` must use the shared AgentKit chat
+  surface with one controller/transport. Do not add a legacy `AssistantChat`
+  renderer or a second stream owner. Keep assistant-ui usage inside the shared
+  composer integration; if linked dependencies need Vite aliases, resolve one
+  `@agent-native/agentkit` context and verify a real AgentKit handoff in the
+  browser.
 - Before handoff, inspect the first viewport and remove the text density,
   repeated cards, unrelated forms, and generic helper copy the user does not
   need until the next decision.

package/corpus/templates/analytics/CHANGELOG.md

@@ -5,6 +5,12 @@ time from the command menu (Cmd+K → "What's new") or from Settings.
 
 ## 2026-09-26
 
+### Improved
+
+- Human Review shows saved Analytics charts and analysis results inline.
+- Loading screens now reflect the app's home layout.
+- Saved dashboard charts can be previewed directly in Human Review.
+
 ### Changed
 
 - The app entry now opens the shared sign-in and sign-up screen instead of a separate marketing page.

package/corpus/templates/assets/.agents/skills/agent-native-toolkit/SKILL.md

@@ -61,10 +61,11 @@ The repeated app shell has two distinct navigation surfaces:
   recommendation, synthesis, visible progress, or steering, route the button
   to the AgentSidebar and let the agent call focused actions. Keep revisions in
   the same thread instead of adding a second freeform prompt box.
-- Standalone apps with `AgentSidebar` must resolve one assistant-ui runtime
-  context. Match direct assistant-ui pins to the installed core/toolkit peer
-  graph, use Vite dedupe/aliases when linked dependencies can split contexts,
-  and verify an AI handoff produces no stale-index console error.
+- Standalone apps with `AgentSidebar` must use the shared AgentKit chat surface
+  and one AgentKit controller/transport. Do not mount the legacy `AssistantChat`
+  renderer or create a second chat stream owner. Keep assistant-ui imports inside
+  the shared composer integration; when linked dependencies need Vite aliases,
+  resolve one `@agent-native/agentkit` context and verify a real handoff.
 
 Contextual agent UI is not a reason to expose every option at once. Start with
 the domain task's primary action, reveal review or configuration only when the

package/corpus/templates/assets/.agents/skills/turn-into-app/SKILL.md

@@ -228,11 +228,12 @@ Generated apps must follow the shared Agent-Native surface model:
 - Choose a named visual direction in `DESIGN.md` before styling and build to it.
   Preserve existing brand tokens; a new unbranded app picks its own
   product-fitting palette rather than inheriting a sibling app's accent.
-- Standalone apps that render `AgentSidebar` must keep one assistant-ui runtime
-  context. Pin the versions compatible with the installed core/toolkit peer
-  graph, and add Vite dedupe/aliases when linked or transitive packages resolve
-  duplicate assistant-ui modules. Verify a fresh AI handoff has no
-  `AssistantUiStaleIndexErrorBoundary` or stale-index console error.
+- Standalone apps that render `AgentSidebar` must use the shared AgentKit chat
+  surface with one controller/transport. Do not add a legacy `AssistantChat`
+  renderer or a second stream owner. Keep assistant-ui usage inside the shared
+  composer integration; if linked dependencies need Vite aliases, resolve one
+  `@agent-native/agentkit` context and verify a real AgentKit handoff in the
+  browser.
 - Before handoff, inspect the first viewport and remove the text density,
   repeated cards, unrelated forms, and generic helper copy the user does not
   need until the next decision.

package/corpus/templates/assets/CHANGELOG.md

@@ -5,6 +5,15 @@ time from the command menu (Cmd+K → "What's new") or from Settings.
 
 ## 2026-09-26
 
+### Improved
+
+- Assets prompts for storage only when you choose to upload files.
+- Loading screens now reflect the app's home layout.
+
+### Fixed
+
+- Dismissing storage setup now cancels queued uploads.
+
 ### Changed
 
 - The app entry now opens the shared sign-in and sign-up screen instead of a separate marketing page.

package/corpus/templates/brain/.agents/skills/agent-native-toolkit/SKILL.md

@@ -61,10 +61,11 @@ The repeated app shell has two distinct navigation surfaces:
   recommendation, synthesis, visible progress, or steering, route the button
   to the AgentSidebar and let the agent call focused actions. Keep revisions in
   the same thread instead of adding a second freeform prompt box.
-- Standalone apps with `AgentSidebar` must resolve one assistant-ui runtime
-  context. Match direct assistant-ui pins to the installed core/toolkit peer
-  graph, use Vite dedupe/aliases when linked dependencies can split contexts,
-  and verify an AI handoff produces no stale-index console error.
+- Standalone apps with `AgentSidebar` must use the shared AgentKit chat surface
+  and one AgentKit controller/transport. Do not mount the legacy `AssistantChat`
+  renderer or create a second chat stream owner. Keep assistant-ui imports inside
+  the shared composer integration; when linked dependencies need Vite aliases,
+  resolve one `@agent-native/agentkit` context and verify a real handoff.
 
 Contextual agent UI is not a reason to expose every option at once. Start with
 the domain task's primary action, reveal review or configuration only when the

package/corpus/templates/brain/.agents/skills/turn-into-app/SKILL.md

@@ -228,11 +228,12 @@ Generated apps must follow the shared Agent-Native surface model:
 - Choose a named visual direction in `DESIGN.md` before styling and build to it.
   Preserve existing brand tokens; a new unbranded app picks its own
   product-fitting palette rather than inheriting a sibling app's accent.
-- Standalone apps that render `AgentSidebar` must keep one assistant-ui runtime
-  context. Pin the versions compatible with the installed core/toolkit peer
-  graph, and add Vite dedupe/aliases when linked or transitive packages resolve
-  duplicate assistant-ui modules. Verify a fresh AI handoff has no
-  `AssistantUiStaleIndexErrorBoundary` or stale-index console error.
+- Standalone apps that render `AgentSidebar` must use the shared AgentKit chat
+  surface with one controller/transport. Do not add a legacy `AssistantChat`
+  renderer or a second stream owner. Keep assistant-ui usage inside the shared
+  composer integration; if linked dependencies need Vite aliases, resolve one
+  `@agent-native/agentkit` context and verify a real AgentKit handoff in the
+  browser.
 - Before handoff, inspect the first viewport and remove the text density,
   repeated cards, unrelated forms, and generic helper copy the user does not
   need until the next decision.

package/corpus/templates/brain/app/lib/brain-chat-readiness.ts

@@ -1,6 +1,4 @@
-export function shouldEnableBrainProviderStatusChecks(
-  builderConfigured: boolean,
-  builderStatusStale: boolean,
-): boolean {
-  return !builderConfigured || builderStatusStale;
+export function shouldEnableBrainProviderStatusChecks(): boolean {
+  // Builder's broader configured flag does not establish chat eligibility.
+  return true;
 }

package/corpus/templates/brain/app/routes/home.tsx

@@ -3,7 +3,6 @@ import {
   markAgentChatHomeHandoff,
 } from "@agent-native/core/client/agent-chat";
 import { useT } from "@agent-native/core/client/i18n";
-import { useBuilderStatus } from "@agent-native/core/client/settings";
 import { useEffect } from "react";
 
 import { shouldEnableBrainProviderStatusChecks } from "@/lib/brain-chat-readiness";
@@ -27,8 +26,6 @@ export function meta() {
 
 export default function AskRoute() {
   const t = useT();
-  const { status: builderStatus, stale: builderStatusStale } =
-    useBuilderStatus();
 
   useEffect(() => {
     function handleChatRunning(event: Event) {
@@ -59,10 +56,7 @@ export default function AskRoute() {
         centerComposerWhenEmpty
         composerLayoutVariant="hero"
         composerPlaceholder={t("ask.composerPlaceholder")}
-        providerStatusChecksEnabled={shouldEnableBrainProviderStatusChecks(
-          builderStatus?.configured === true,
-          builderStatusStale,
-        )}
+        providerStatusChecksEnabled={shouldEnableBrainProviderStatusChecks()}
         composerSlot={
           <div className="brain-chat-intro">
             <h1>{t("ask.heroTitle")}</h1>

package/corpus/templates/calendar/.agents/skills/agent-native-toolkit/SKILL.md

@@ -61,10 +61,11 @@ The repeated app shell has two distinct navigation surfaces:
   recommendation, synthesis, visible progress, or steering, route the button
   to the AgentSidebar and let the agent call focused actions. Keep revisions in
   the same thread instead of adding a second freeform prompt box.
-- Standalone apps with `AgentSidebar` must resolve one assistant-ui runtime
-  context. Match direct assistant-ui pins to the installed core/toolkit peer
-  graph, use Vite dedupe/aliases when linked dependencies can split contexts,
-  and verify an AI handoff produces no stale-index console error.
+- Standalone apps with `AgentSidebar` must use the shared AgentKit chat surface
+  and one AgentKit controller/transport. Do not mount the legacy `AssistantChat`
+  renderer or create a second chat stream owner. Keep assistant-ui imports inside
+  the shared composer integration; when linked dependencies need Vite aliases,
+  resolve one `@agent-native/agentkit` context and verify a real handoff.
 
 Contextual agent UI is not a reason to expose every option at once. Start with
 the domain task's primary action, reveal review or configuration only when the

package/corpus/templates/calendar/.agents/skills/turn-into-app/SKILL.md

@@ -228,11 +228,12 @@ Generated apps must follow the shared Agent-Native surface model:
 - Choose a named visual direction in `DESIGN.md` before styling and build to it.
   Preserve existing brand tokens; a new unbranded app picks its own
   product-fitting palette rather than inheriting a sibling app's accent.
-- Standalone apps that render `AgentSidebar` must keep one assistant-ui runtime
-  context. Pin the versions compatible with the installed core/toolkit peer
-  graph, and add Vite dedupe/aliases when linked or transitive packages resolve
-  duplicate assistant-ui modules. Verify a fresh AI handoff has no
-  `AssistantUiStaleIndexErrorBoundary` or stale-index console error.
+- Standalone apps that render `AgentSidebar` must use the shared AgentKit chat
+  surface with one controller/transport. Do not add a legacy `AssistantChat`
+  renderer or a second stream owner. Keep assistant-ui usage inside the shared
+  composer integration; if linked dependencies need Vite aliases, resolve one
+  `@agent-native/agentkit` context and verify a real AgentKit handoff in the
+  browser.
 - Before handoff, inspect the first viewport and remove the text density,
   repeated cards, unrelated forms, and generic helper copy the user does not
   need until the next decision.

package/corpus/templates/calendar/CHANGELOG.md

@@ -5,10 +5,25 @@ time from the command menu (Cmd+K → "What's new") or from Settings.
 
 ## 2026-09-26
 
+### Improved
+
+- Calendar confirms created events in chat with the time and links to open or join them
+- Loading screens now reflect the app's home layout.
+- Manage AI invitation rules and recent activity in separate tabs, with Jev connection options
+
+### Fixed
+
+- Calendar users can clear saved invitation rules after Jev is disconnected
+- Cancellation emails now send guests back to the correct Calendar booking page.
+
 ### Changed
 
 - The app entry now opens the shared sign-in and sign-up screen instead of a separate marketing page.
 
+### Security
+
+- Signing out clears lingering sign-in sessions so another account cannot reappear.
+
 ## 2026-09-25
 
 ### Added

package/corpus/templates/chat/.agents/skills/agent-native-toolkit/SKILL.md

@@ -61,10 +61,11 @@ The repeated app shell has two distinct navigation surfaces:
   recommendation, synthesis, visible progress, or steering, route the button
   to the AgentSidebar and let the agent call focused actions. Keep revisions in
   the same thread instead of adding a second freeform prompt box.
-- Standalone apps with `AgentSidebar` must resolve one assistant-ui runtime
-  context. Match direct assistant-ui pins to the installed core/toolkit peer
-  graph, use Vite dedupe/aliases when linked dependencies can split contexts,
-  and verify an AI handoff produces no stale-index console error.
+- Standalone apps with `AgentSidebar` must use the shared AgentKit chat surface
+  and one AgentKit controller/transport. Do not mount the legacy `AssistantChat`
+  renderer or create a second chat stream owner. Keep assistant-ui imports inside
+  the shared composer integration; when linked dependencies need Vite aliases,
+  resolve one `@agent-native/agentkit` context and verify a real handoff.
 
 Contextual agent UI is not a reason to expose every option at once. Start with
 the domain task's primary action, reveal review or configuration only when the

package/corpus/templates/chat/.agents/skills/turn-into-app/SKILL.md

@@ -228,11 +228,12 @@ Generated apps must follow the shared Agent-Native surface model:
 - Choose a named visual direction in `DESIGN.md` before styling and build to it.
   Preserve existing brand tokens; a new unbranded app picks its own
   product-fitting palette rather than inheriting a sibling app's accent.
-- Standalone apps that render `AgentSidebar` must keep one assistant-ui runtime
-  context. Pin the versions compatible with the installed core/toolkit peer
-  graph, and add Vite dedupe/aliases when linked or transitive packages resolve
-  duplicate assistant-ui modules. Verify a fresh AI handoff has no
-  `AssistantUiStaleIndexErrorBoundary` or stale-index console error.
+- Standalone apps that render `AgentSidebar` must use the shared AgentKit chat
+  surface with one controller/transport. Do not add a legacy `AssistantChat`
+  renderer or a second stream owner. Keep assistant-ui usage inside the shared
+  composer integration; if linked dependencies need Vite aliases, resolve one
+  `@agent-native/agentkit` context and verify a real AgentKit handoff in the
+  browser.
 - Before handoff, inspect the first viewport and remove the text density,
   repeated cards, unrelated forms, and generic helper copy the user does not
   need until the next decision.

package/corpus/templates/chat/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 All notable user-facing changes to this app are documented here.
 
+## 2026-09-27
+
+### Fixed
+
+- Chat retries the original request with its attachments after model setup.
+
 ## 2026-08-27
 
 ### Fixed

package/corpus/templates/chat/app/components/layout/AgentInspector.tsx

@@ -15,6 +15,7 @@ interface AgentInspectorProps {
   chatHomeHandoffPending: boolean;
 }
 
+/** Contextual inspector shell used on secondary chat routes. */
 export function AgentInspector({
   children,
   chatHomeHandoffActive,

package/corpus/templates/chat/app/global.css

@@ -3,7 +3,6 @@
 @import "tailwindcss";
 @import "@agent-native/core/styles/agent-native.css";
 @import "@agent-native/toolkit/styles.css";
-@import "@agent-native/agentkit/react/styles.css";
 
 @source "./**/*.{ts,tsx}";
 

package/corpus/templates/clips/.agents/skills/agent-native-toolkit/SKILL.md

@@ -61,10 +61,11 @@ The repeated app shell has two distinct navigation surfaces:
   recommendation, synthesis, visible progress, or steering, route the button
   to the AgentSidebar and let the agent call focused actions. Keep revisions in
   the same thread instead of adding a second freeform prompt box.
-- Standalone apps with `AgentSidebar` must resolve one assistant-ui runtime
-  context. Match direct assistant-ui pins to the installed core/toolkit peer
-  graph, use Vite dedupe/aliases when linked dependencies can split contexts,
-  and verify an AI handoff produces no stale-index console error.
+- Standalone apps with `AgentSidebar` must use the shared AgentKit chat surface
+  and one AgentKit controller/transport. Do not mount the legacy `AssistantChat`
+  renderer or create a second chat stream owner. Keep assistant-ui imports inside
+  the shared composer integration; when linked dependencies need Vite aliases,
+  resolve one `@agent-native/agentkit` context and verify a real handoff.
 
 Contextual agent UI is not a reason to expose every option at once. Start with
 the domain task's primary action, reveal review or configuration only when the

package/corpus/templates/clips/.agents/skills/turn-into-app/SKILL.md

@@ -228,11 +228,12 @@ Generated apps must follow the shared Agent-Native surface model:
 - Choose a named visual direction in `DESIGN.md` before styling and build to it.
   Preserve existing brand tokens; a new unbranded app picks its own
   product-fitting palette rather than inheriting a sibling app's accent.
-- Standalone apps that render `AgentSidebar` must keep one assistant-ui runtime
-  context. Pin the versions compatible with the installed core/toolkit peer
-  graph, and add Vite dedupe/aliases when linked or transitive packages resolve
-  duplicate assistant-ui modules. Verify a fresh AI handoff has no
-  `AssistantUiStaleIndexErrorBoundary` or stale-index console error.
+- Standalone apps that render `AgentSidebar` must use the shared AgentKit chat
+  surface with one controller/transport. Do not add a legacy `AssistantChat`
+  renderer or a second stream owner. Keep assistant-ui usage inside the shared
+  composer integration; if linked dependencies need Vite aliases, resolve one
+  `@agent-native/agentkit` context and verify a real AgentKit handoff in the
+  browser.
 - Before handoff, inspect the first viewport and remove the text density,
   repeated cards, unrelated forms, and generic helper copy the user does not
   need until the next decision.

package/corpus/templates/clips/CHANGELOG.md

@@ -7,11 +7,22 @@ from the command menu (Cmd+K → "What's new") or from Settings.
 
 ### Improved
 
+- Ask about a live meeting from the recording pill, with transcript context and AI-generated next-step suggestions.
+- Clips asks you to connect storage only when an upload needs it.
 - See the desktop app for your platform at a glance.
 - The comments signup headline now wraps more evenly.
 - The empty comments state now explains how screen recordings help AI agents.
 - The empty comments view has a clearer headline and a focused signup action.
 
+### Fixed
+
+- Clips asks you to connect storage only when you choose an upload
+- Clips can play recordings from public S3-compatible storage in more hosted environments.
+- Dismissing storage setup now cancels queued uploads.
+- Meeting chat waits for interactive AI access before sending, and its answer panel has a localized resize and dismiss label.
+- Stopping a recording with its keyboard shortcut now shows the completion card.
+- Video uploads only ask for storage when you choose Upload video, then offer a fresh upload action after storage connects.
+
 ### Changed
 
 - The app entry now opens the shared sign-in and sign-up screen instead of a separate marketing page.
@@ -42,6 +53,7 @@ from the command menu (Cmd+K → "What's new") or from Settings.
 
 ### Improved
 
+- Sharing recordings now uses a joined Share and quick-copy control with People and Agents tabs
 - Recording actions are easier to find and align clearly.
 - Share links appear after uploads finish, when clips are ready to view.
 

package/corpus/templates/clips/app/i18n/en-US.ts

@@ -1,4 +1,5 @@
 const messages = {
+  meetingAsk: { resizeOrDismissAnswers: "Resize or dismiss answers" },
   agentChat: {
     setup: {
       checkingProvider: "Checking AI connection…",

package/corpus/templates/clips/changelog/2026-09-26-ask-about-a-live-meeting-from-the-recording-pill-with-transc.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-09-26
+---
+
+Ask about a live meeting from the recording pill, with transcript context and AI-generated next-step suggestions.

package/corpus/templates/clips/changelog/2026-09-26-meeting-chat-waits-for-interactive-ai-access-before-sending-.md

@@ -0,0 +1,6 @@
+---
+type: fixed
+date: 2026-09-26
+---
+
+Meeting chat waits for interactive AI access before sending, and its answer panel has a localized resize and dismiss label.