@agent-native/core 0.207.0-nightly-20261011153008 → 0.207.0

package/dist/triggers/actions/manage-automation.d.ts

@@ -13,6 +13,8 @@ declare const _default: import("../../action.js").ActionDefinition<{
     executionEngine?: string;
     executionCwd?: string;
 }, {
+    deleted?: undefined;
+    enabled?: undefined;
     created: boolean;
     name: string;
     scope: "organization" | "personal";
@@ -23,33 +25,31 @@ declare const _default: import("../../action.js").ActionDefinition<{
     reasoningEffort: "auto" | "high" | "low" | "max" | "medium" | "minimal" | "none" | "xhigh";
     webhookPath: string;
     nextRun: string;
-    deleted?: undefined;
-    enabled?: undefined;
     executionHostId?: undefined;
     executionEngine?: undefined;
     executionCwd?: undefined;
 } | {
-    created?: undefined;
     scope?: undefined;
+    enabled?: undefined;
+    nextRun?: undefined;
+    created?: undefined;
     triggerType?: undefined;
     event?: undefined;
     deleted: boolean;
     name: string;
-    enabled?: undefined;
     schedule?: undefined;
     timezone?: undefined;
     reasoningEffort?: undefined;
     executionHostId?: undefined;
     executionEngine?: undefined;
     executionCwd?: undefined;
-    nextRun?: undefined;
     webhookPath?: undefined;
 } | {
-    created?: undefined;
     scope?: undefined;
+    deleted?: undefined;
+    created?: undefined;
     triggerType?: undefined;
     event?: undefined;
-    deleted?: undefined;
     name: string;
     enabled: boolean;
     schedule: string;

package/docs/content/environment-variables.mdx

@@ -15,13 +15,11 @@ most apps need.
 For a normal app, start with the [Agent-Native app configuration guide](/docs/agent-native-config),
 then use [Deployment: Environment Variables](/docs/deployment-environment-variables)
 and [Authentication](/docs/authentication) for the deliberate environment-only
-parts. LLM provider keys in environment variables are shared as an app-wide
-fallback by self-hosted deployments, including those with a remote database.
-Production Hosted-workspace runtimes block deployment provider-key fallbacks.
-Any signed-in user without a scoped key can use the deployment provider
-account, and usage is billed to that account. Configure these keys only when
-app-wide access and billing are intended. Keep user-, organization-, and
-workspace-scoped credentials in the database-backed secret or connection store.
+parts. LLM provider keys can be app-wide fallbacks on self-hosted deployments;
+production Hosted-workspace runtimes block that fallback. See [LLM provider
+keys](#llm-provider-keys) for local setup, scoped keys, and deployment sharing
+and billing. Keep user-, organization-, and workspace-scoped credentials in the
+database-backed secret or connection store.
 
 For committed, non-secret app defaults, use `agent-native.config.ts` first. If a
 public config value must vary by deployment, use its deterministic
@@ -83,7 +81,7 @@ public app behavior, use the config paths above instead.
 | `SECRETS_ENCRYPTION_KEY`                       | Legacy app-local/shared encryption fallback.                                                                                                                                   | A stable encryption key; prefer the workspace key for new shared vaults.                                                |
 | `WORKSPACE_SECRETS_ENCRYPTION_KEY`             | Stable encryption key for a workspace-shared secrets vault.                                                                                                                    | The same stable key in every app that reads the vault.                                                                  |
 | `WORKSPACE_SECRETS_ENCRYPTION_KEY_PREVIOUS`    | Previous workspace key during rotation.                                                                                                                                        | The old key only; remove it after migration.                                                                            |
-| `ANTHROPIC_API_KEY`                            | Shared fallback for self-hosted apps, including remote databases.                                                                                                              | An Anthropic API key; scoped user or organization keys take precedence.                                                 |
+| `ANTHROPIC_API_KEY`                            | Shared fallback for self-hosted apps, including remote databases.                                                                                                              | An Anthropic API key; saved personal, organization, or workspace-scoped keys take precedence.                           |
 | `AGENT_ENGINE`                                 | Explicitly selects the agent engine instead of auto-detecting from provider keys.                                                                                              | A registered engine name such as `anthropic`, `ai-sdk:openai`, `builder`, or `codex-cli`.                               |
 | `AGENT_BUILT_IN_ENGINES`                       | Restricts which built-in engines are registered at all, so the rest never appear in the model picker or resolve by name.                                                       | A comma-separated list of built-in engine names such as `ai-sdk:openai`; unset registers every built-in.                |
 | `AGENT_SOURCE_SWEEP_TOOL_CALL_THRESHOLD`       | Read-only source/search tool calls one turn may make before the agent is told to converge and answer from what it gathered.                                                    | A positive integer; defaults to 24. Raise it for research-shaped apps that legitimately inspect many records.           |
@@ -173,11 +171,38 @@ specific Google API integrations; they are not required for browser sign-in.
 
 ## Optional AI, search, and email fallbacks
 
-These are deploy-level fallbacks for self-hosted deployments. Any signed-in
-user or organization without a scoped key can use the deployment provider
-account, and usage is billed to that account. Configure these keys only when
-app-wide access and billing are intended. Production Hosted-workspace runtimes
-block deployment provider-key fallbacks.
+### LLM provider keys {#llm-provider-keys}
+
+For local development, put a supported provider key in the app's `.env` file
+before starting `pnpm dev`. For example:
+
+```dotenv
+ANTHROPIC_API_KEY=replace-with-your-key
+```
+
+For an app-wide fallback, set a supported provider key in the server-side
+environment of a self-hosted app. This also works with a remote PostgreSQL
+database. Any signed-in user without a personal, organization-scoped, or
+workspace-scoped provider key can use the deployment's provider account, and
+usage is billed to that account. Anonymous public runs and synthetic traffic do
+not receive this fallback. Personal, organization, and workspace-scoped keys
+take precedence. Setting a deployment key opts in to
+app-wide access and billing; no extra shared-key flag is needed. Production
+Hosted-workspace runtimes block deployment provider-key fallbacks.
+
+To keep a key scoped, select **Custom keys** in the app's LLM setup. In a
+PostgreSQL app, a personal key stays with its user; organization scope shares a
+key with the active organization and is available to admins. The app stores
+these saved keys in its encrypted database-backed credential store.
+
+To use Builder's managed provider, connect with **Use Builder.io** in the app's
+LLM setup. This uses the Builder connection instead of a provider API key from
+the table below.
+
+The table below lists optional deployment-level fallbacks for self-hosted apps.
+See the LLM guidance above for which users can use the deployment provider key
+and how usage is billed. Production Hosted-workspace runtimes block deployment
+provider-key fallbacks.
 
 Every provider key below selects its engine on its own: dropping one in is
 enough, and `AGENT_ENGINE` is only needed to pick between several.

package/docs/content/getting-started.mdx

@@ -20,8 +20,7 @@ In this guide, you'll create an agent with a chat UI and call its included
 - [Node.js](https://nodejs.org) 22.22 or later
 - [pnpm](https://pnpm.io) available on your `PATH` (run `corepack enable` in
   the generated app if it is not)
-- An LLM connection for the agent: Builder.io, an Anthropic or OpenAI API key,
-  or a local Ollama model
+- Optional while setting up; required to run the agent: Builder.io, an Anthropic/OpenAI key, or local Ollama
 
 ## Create an agent
 
@@ -64,33 +63,12 @@ enter an email or password for local development.
 
 </Callout>
 
-## Connect an LLM {#connect-an-llm}
+## Connect an LLM (optional) {#connect-an-llm}
 
-The app opens on the **Get started** page. For local development, add a
-provider key to the app's `.env` file before starting `pnpm dev`:
-
-```dotenv
-ANTHROPIC_API_KEY=replace-with-your-key
-```
-
-Self-hosted apps use this as a deployment-wide fallback, so users do not need
-to add a key in the UI. Hosted-workspace production runtimes block deployment
-provider-key sharing. Scoped user or organization keys take precedence.
-
-Setting this provider key is the operator's opt-in to app-wide access and
-billing; no separate shared-key flag is needed. Any signed-in user without a
-scoped key can use the deployment provider account across all organizations in
-the app, and usage is billed to that account. Use scoped keys when tenants need
-separate credentials or billing.
-
-With PostgreSQL, users can also save a key through **Custom keys**. Choose
-Personal scope to keep it to your account; admins can choose Organization scope
-to share it with the workspace. The app stores saved keys in its encrypted
-database-backed credential store.
-
-To use Builder's managed provider instead, select **Use Builder.io** in the
-composer. See [Environment Variables](/docs/environment-variables#optional-ai-search-and-email-fallbacks)
-for supported provider keys and their deployment scope.
+Connect with **Use Builder.io**, add a personal or organization key through
+**Custom keys**, or set a provider key in `.env` for local development and in
+the deployment environment for app-wide use on self-hosted apps. See the [LLM
+provider setup](/docs/environment-variables#llm-provider-keys).
 
 ## Run the action from the agent
 

package/docs/content/multi-app-workspace.mdx

@@ -260,7 +260,10 @@ By default every workspace can reach the hosted first-party apps (Mail, Calendar
     "workspaceCore": "@my-company-platform/shared",
     "builtinAgents": {
       "mode": "selected",
-      "include": ["mail", "calendar"]
+      "include": ["mail", "calendar", "design"],
+      "urls": {
+        "design": "https://design.example.test"
+      }
     }
   }
 }
@@ -268,10 +271,11 @@ By default every workspace can reach the hosted first-party apps (Mail, Calendar
 
 - `mode`: `"all"` (default, every public first-party app), `"none"` (no built-ins), or `"selected"` (only `include`).
 - `include`: the built-ins this workspace offers when `mode` is `"selected"`. Anything else stays unknown to the workspace.
+- `urls` (optional): maps built-in IDs to HTTPS base URL overrides for offered built-ins without changing the offered agents. It replaces the canonical hosted URL, including in a seeded manifest that still uses that default, while custom connected remote-agent URLs and workspace-app overlays retain priority. Unknown IDs and invalid URLs fail parsing. Each value must be a trimmed absolute HTTPS URL with no credentials, query, or fragment. Local-development routing keeps priority and uses local URLs.
 
-Unknown ids log a warning and are ignored. A standalone app can use the same key in its own `package.json`. `agent-native dev` and workspace deploys pass the value to every app as `AGENT_NATIVE_BUILTIN_AGENTS_JSON`.
+Unknown IDs in `include` log a warning and are ignored. A standalone app can use the same key in its own `package.json`. `agent-native dev` and workspace deploys pass the value to every app as `AGENT_NATIVE_BUILTIN_AGENTS_JSON`.
 
-This config controls the app list, agent discovery, and agent-to-agent calls. Mounted workspace apps and connected remote agents are unaffected, and MCP app access stays a separate routing permission.
+This config controls the app list, agent discovery, and agent-to-agent calls. Mounted workspace apps and custom connected remote-agent URLs retain priority, and MCP app access stays a separate routing permission.
 
 ## Shared MCP servers {#shared-mcp}
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.207.0-nightly-20261011153008",
+  "version": "0.207.0",
   "description": "The agentic application framework for building autonomous agents with intuitive UIs",
   "homepage": "https://github.com/BuilderIO/agent-native#readme",
   "bugs": {
@@ -694,8 +694,8 @@
     "yaml": "^2.9.0",
     "yjs": "^13.6.33",
     "zod": "^4.3.6",
-    "@agent-native/agentkit": "^0.207.0-nightly-20261011153008",
-    "@agent-native/recap-cli": "^0.5.68"
+    "@agent-native/recap-cli": "^0.5.69",
+    "@agent-native/agentkit": "^0.207.0"
   },
   "devDependencies": {
     "@ai-sdk/anthropic": "^3.0.71",
@@ -765,7 +765,7 @@
     "xlsx": "^0.18.5"
   },
   "peerDependencies": {
-    "@agent-native/core-corpus": "0.207.0-nightly-20261011153008",
+    "@agent-native/core-corpus": ">=0.196.0",
     "@ai-sdk/anthropic": ">=3",
     "@ai-sdk/cohere": ">=3",
     "@ai-sdk/google": ">=3",

package/src/templates/chat/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 All notable user-facing changes to this app are documented here.
 
+## 2026-10-10
+
+### Fixed
+
+- Large prompts with full context remain available to retry when sending fails.
+
 ## 2026-09-30
 
 ### Improved

package/src/templates/chat/app/components/home/HomePage.tsx

@@ -284,7 +284,7 @@ export default function HomePage() {
         </p>
         <Button asChild variant="link" size="sm" className="h-auto px-0">
           <a
-            href={`${DOCS_URL}/getting-started#connect-an-llm`}
+            href={`${DOCS_URL}/environment-variables#llm-provider-keys`}
             target="_blank"
             rel="noreferrer"
           >

package/src/templates/chat/app/i18n/ar-SA.ts

@@ -61,7 +61,7 @@ const messages = {
     editHint: "عدّل {{file}} واحفظه، ثم اسأل مجددًا لترى التحية الجديدة.",
     lead: "تتشارك واجهة تطبيقك ووكيله الإجراءات نفسها.",
     leadTry: "اطلب من الوكيل استدعاء الإجراء hello.",
-    llmSetupLink: "إعداد مفتاح LLM للتطبيق بالكامل",
+    llmSetupLink: "إعداد موفّر LLM",
     title: "ابدأ الآن",
   },
   navigation: {

package/src/templates/chat/app/i18n/de-DE.ts

@@ -64,7 +64,7 @@ const messages = {
       "Bearbeite {{file}}, speichere und frag erneut, um die neue Begrüßung zu sehen.",
     lead: "Die Oberfläche deiner App und ihr Agent nutzen dieselben Aktionen.",
     leadTry: "Bitte den Agenten, die Aktion hello aufzurufen.",
-    llmSetupLink: "App-weiten LLM-Schlüssel einrichten",
+    llmSetupLink: "LLM-Anbieter einrichten",
     title: "Loslegen",
   },
   navigation: {

package/src/templates/chat/app/i18n/en-US.ts

@@ -62,7 +62,7 @@ const messages = {
     editHint: "Edit {{file}} and save, then ask again to see the new greeting.",
     lead: "Your app's UI and its agent share one set of actions.",
     leadTry: "Ask the agent to call the hello action.",
-    llmSetupLink: "Set up an app-wide LLM key",
+    llmSetupLink: "LLM provider setup",
     title: "Get started",
   },
   navigation: {

package/src/templates/chat/app/i18n/es-ES.ts

@@ -64,7 +64,7 @@ const messages = {
       "Edita {{file}}, guarda y vuelve a preguntar para ver el nuevo saludo.",
     lead: "La interfaz de tu app y su agente comparten las mismas acciones.",
     leadTry: "Pide al agente que llame a la acción hello.",
-    llmSetupLink: "Configurar una clave de LLM para toda la app",
+    llmSetupLink: "Configuración del proveedor LLM",
     title: "Empieza aquí",
   },
   navigation: {

package/src/templates/chat/app/i18n/fr-FR.ts

@@ -64,7 +64,7 @@ const messages = {
       "Modifiez {{file}}, enregistrez, puis redemandez pour voir le nouveau message.",
     lead: "L’interface de votre app et son agent partagent les mêmes actions.",
     leadTry: "Demandez à l’agent d’appeler l’action hello.",
-    llmSetupLink: "Configurer une clé LLM pour toute l’app",
+    llmSetupLink: "Configuration du fournisseur LLM",
     title: "Commencer",
   },
   navigation: {

package/src/templates/chat/app/i18n/hi-IN.ts

@@ -63,7 +63,7 @@ const messages = {
       "{{file}} में बदलाव करके सेव करें, फिर नया अभिवादन देखने के लिए दोबारा पूछें।",
     lead: "आपके ऐप का UI और उसका एजेंट एक ही क्रियाएं साझा करते हैं।",
     leadTry: "एजेंट से hello क्रिया कॉल करने को कहें।",
-    llmSetupLink: "पूरे ऐप के लिए LLM कुंजी सेट करें",
+    llmSetupLink: "LLM प्रदाता सेटअप",
     title: "शुरू करें",
   },
   navigation: {

package/src/templates/chat/app/i18n/ja-JP.ts

@@ -63,7 +63,7 @@ const messages = {
       "{{file}} を編集して保存し、もう一度頼むと新しいあいさつが表示されます。",
     lead: "アプリの UI とエージェントは同じアクションを共有しています。",
     leadTry: "エージェントに hello アクションを呼び出してもらいましょう。",
-    llmSetupLink: "アプリ全体で使う LLM キーを設定",
+    llmSetupLink: "LLM プロバイダーの設定",
     title: "はじめに",
   },
   navigation: {

package/src/templates/chat/app/i18n/ko-KR.ts

@@ -64,7 +64,7 @@ const messages = {
       "{{file}} 파일을 수정하고 저장한 다음 다시 요청하면 새 인사말이 보입니다.",
     lead: "앱의 UI와 에이전트는 같은 작업을 공유합니다.",
     leadTry: "에이전트에게 hello 작업을 호출해 달라고 요청해 보세요.",
-    llmSetupLink: "앱 전체에서 사용할 LLM 키 설정",
+    llmSetupLink: "LLM 제공자 설정",
     title: "시작하기",
   },
   navigation: {

package/src/templates/chat/app/i18n/pt-BR.ts

@@ -64,7 +64,7 @@ const messages = {
       "Edite {{file}}, salve e pergunte de novo para ver a nova saudação.",
     lead: "A interface do seu app e o agente dele compartilham as mesmas ações.",
     leadTry: "Peça ao agente para chamar a ação hello.",
-    llmSetupLink: "Configurar uma chave de LLM para todo o app",
+    llmSetupLink: "Configuração do provedor LLM",
     title: "Comece aqui",
   },
   navigation: {

package/src/templates/chat/app/i18n/zh-CN.ts

@@ -59,7 +59,7 @@ const messages = {
     editHint: "编辑 {{file}} 并保存，再问一次就能看到新的问候语。",
     lead: "应用的界面和代理共用同一组操作。",
     leadTry: "让代理调用 hello 操作试试。",
-    llmSetupLink: "设置应用级 LLM 密钥",
+    llmSetupLink: "LLM 提供商设置",
     title: "开始使用",
   },
   navigation: {

package/src/templates/chat/app/i18n/zh-TW.ts

@@ -59,7 +59,7 @@ const messages = {
     editHint: "編輯 {{file}} 並儲存，再問一次就能看到新的問候語。",
     lead: "應用程式的介面和代理共用同一組操作。",
     leadTry: "讓代理呼叫 hello 操作試試。",
-    llmSetupLink: "設定應用程式共用的 LLM 金鑰",
+    llmSetupLink: "LLM 提供者設定",
     title: "開始使用",
   },
   navigation: {