@agent-native/core 0.84.35 → 0.84.37

package/README.md

@@ -2,10 +2,10 @@
 
 ## The framework for agent-native apps
 
-Agent-Native is an open-source framework for building robust agents that act inside real apps, not just chat next to them. It gives you primitives for product-grade agentic software: shared actions, SQL-backed state, identity, tools, skills, jobs, observability, and UI surfaces that all work together. Bring your own database, hosting provider, model stack, and app code.
+Agent-Native is an open-source framework for apps where agents and UI share the same actions, state, and context.
 
 ```ts
-// One action powers UI, agent, HTTP, MCP, A2A, and CLI.
+// One action powers every app surface: UI, agent, HTTP, MCP, A2A, and CLI.
 export default defineAction({
   schema: z.object({
     emailId: z.string(),
@@ -17,13 +17,13 @@ export default defineAction({
 });
 ```
 
-- **Actions**: Define work once. Use it from UI, agent, API, MCP, A2A, and CLI.
+- **Actions**: Define work once. Use it from every app surface: UI, agent, HTTP, MCP, A2A, and CLI.
 - **Agent runtime**: Chat, tools, skills, memory, jobs, observability, and handoffs ship together.
 - **Backend agnostic**: Plug in any Drizzle-supported SQL database and Nitro-compatible host.
 
-## Templates
+## Apps
 
-Start with a full featured template. Each one is a complete, 100% free and open-source SaaS app: cloneable, not scaffolded, except you own the code and can customize everything.
+Fork a working app and let the agent evolve it. **You can customize everything.**
 
 <table>
 <tr>
@@ -31,7 +31,7 @@ Start with a full featured template. Each one is a complete, 100% free and open-
 
 **Clips**
 
-<a href="https://agent-native.com/templates/clips"><img src="https://cdn.builder.io/api/v1/image/assets%2FYJIGb4i01jvw0SRdL5Bt%2F189ebd9b2f2b4f0ead3b33138d4e4c10?format=webp&width=800" alt="Clips template" width="100%" /></a>
+<a href="https://agent-native.com/templates/clips"><img src="https://cdn.builder.io/api/v1/image/assets%2FYJIGb4i01jvw0SRdL5Bt%2F189ebd9b2f2b4f0ead3b33138d4e4c10?format=webp&width=800" alt="Clips app" width="100%" /></a>
 
 **Agent-Native Loom + Jam**
 
@@ -42,7 +42,7 @@ Record your screen with auto-transcripts and captured browser debug logs, share
 
 **Plans**
 
-<a href="https://agent-native.com/templates/plan"><img src="https://cdn.builder.io/api/v1/image/assets%2FYJIGb4i01jvw0SRdL5Bt%2Fefc6a3ac908149fa92e2b9392c0bb372?format=webp&width=800" alt="Plans template" width="100%" /></a>
+<a href="https://agent-native.com/templates/plan"><img src="https://cdn.builder.io/api/v1/image/assets%2FYJIGb4i01jvw0SRdL5Bt%2Fefc6a3ac908149fa92e2b9392c0bb372?format=webp&width=800" alt="Plans app" width="100%" /></a>
 
 **Visual plan mode for coding agents**
 
@@ -53,7 +53,7 @@ Install `/visual-plan` and `/visual-recap` so your coding agent can plan before
 
 **Design**
 
-<a href="https://agent-native.com/templates/design"><img src="https://cdn.builder.io/api/v1/image/assets%2FYJIGb4i01jvw0SRdL5Bt%2Fe2c86908c2fa4f119ee4aa90b4823944?format=webp&width=800" alt="Design template" width="100%" /></a>
+<a href="https://agent-native.com/templates/design"><img src="https://cdn.builder.io/api/v1/image/assets%2FYJIGb4i01jvw0SRdL5Bt%2Fe2c86908c2fa4f119ee4aa90b4823944?format=webp&width=800" alt="Design app" width="100%" /></a>
 
 **Agent-Native design prototyping**
 
@@ -66,7 +66,7 @@ Generate interactive HTML prototypes, compare variants, refine controls, and exp
 
 **Content**
 
-<a href="https://agent-native.com/templates/content"><img src="https://cdn.builder.io/api/v1/image/assets%2FYJIGb4i01jvw0SRdL5Bt%2F89bcfc6106304bfbaf8ec8a7ccd721eb?format=webp&width=800" alt="Content template" width="100%" /></a>
+<a href="https://agent-native.com/templates/content"><img src="https://cdn.builder.io/api/v1/image/assets%2FYJIGb4i01jvw0SRdL5Bt%2F89bcfc6106304bfbaf8ec8a7ccd721eb?format=webp&width=800" alt="Content app" width="100%" /></a>
 
 **Open-source Obsidian for MDX**
 
@@ -77,7 +77,7 @@ Edit local Markdown/MDX files, generate rich interactive custom blocks, and draf
 
 **Slides**
 
-<a href="https://agent-native.com/templates/slides"><img src="https://cdn.builder.io/api/v1/image/assets%2FYJIGb4i01jvw0SRdL5Bt%2F2c09b451d40c4a74a89a38d69170c2d8?format=webp&width=800" alt="Slides template" width="100%" /></a>
+<a href="https://agent-native.com/templates/slides"><img src="https://cdn.builder.io/api/v1/image/assets%2FYJIGb4i01jvw0SRdL5Bt%2F2c09b451d40c4a74a89a38d69170c2d8?format=webp&width=800" alt="Slides app" width="100%" /></a>
 
 **Agent-Native Google Slides, Pitch**
 
@@ -88,7 +88,7 @@ Generate and edit React-based presentations via prompt or point-and-click.
 
 **Analytics**
 
-<a href="https://agent-native.com/templates/analytics"><img src="https://cdn.builder.io/api/v1/image/assets%2FYJIGb4i01jvw0SRdL5Bt%2F4933a80cc3134d7e874631f688be828a?format=webp&width=800" alt="Analytics template" width="100%" /></a>
+<a href="https://agent-native.com/templates/analytics"><img src="https://cdn.builder.io/api/v1/image/assets%2FYJIGb4i01jvw0SRdL5Bt%2F4933a80cc3134d7e874631f688be828a?format=webp&width=800" alt="Analytics app" width="100%" /></a>
 
 **Agent-Native Amplitude, Mixpanel**
 
@@ -98,40 +98,11 @@ Connect analytics data sources, prompt for real charts, and build reusable dashb
 </tr>
 </table>
 
-View the full template gallery at **[agent-native.com/templates](https://agent-native.com/templates)**.
-
-## Agents and UIs, Fully Connected
-
-The agent and the UI are equal citizens of one system. Every action works both ways: click it or ask for it.
-
-![Agents and UIs fully connected](https://cdn.builder.io/api/v1/file/assets%2FYJIGb4i01jvw0SRdL5Bt%2Fadc1e9e9368e4a8cb1b4dbb5aae5aaa2)
-
-- **Everything syncs**: One database, one state. Changes from either side show up instantly on the other.
-- **Real-time multiplayer**: Humans and agents edit the same document together, with the agent as a first-class peer.
-- **Context-aware**: The agent knows what you're looking at. Select text, hit Cmd+I, and tell it what to do.
-- **Agents call agents**: Tag another agent from any app and they coordinate over A2A.
-- **Self-improving**: The agent can add features, fix bugs, and refine the UI over time.
-
-## Try it with a skill
-
-Don't want to scaffold a whole app yet? Add visual planning and PR recaps to Claude Code, Codex, Cursor, Pi, OpenCode, GitHub Copilot / VS Code, and similar agents with one command:
-
-```bash
-npx @agent-native/core@latest skills add visual-plan
-```
-
-![Visual plan and recap in action](https://raw.githubusercontent.com/builderio/skills/main/media/visual-recap.gif)
-
-You get two slash commands:
-
-- **`/visual-plan`**: before the agent writes code, it opens a structured, reviewable plan with inline diagrams, UI wireframes, file-by-file implementation maps, and annotations you can comment on and approve.
-- **`/visual-recap`**: after changes land, it turns a PR or git diff into a high-altitude visual recap with a shareable review link instead of a raw diff.
-
-See the **[Skills Guide](https://agent-native.com/docs/skills-guide#app-backed-skills)** for more.
+View the full app gallery at **[agent-native.com/templates](https://agent-native.com/templates)**.
 
 ## Quick Start
 
-One command to start a new project locally.
+One command to start a new app locally.
 
 ```bash
 npx @agent-native/core@latest create my-app
@@ -142,20 +113,13 @@ pnpm dev
 
 `create` first asks how you want to start:
 
-- **Full template(s)**: clone one or more complete apps into a workspace. Pick Mail + Calendar + Forms and you get all three wired up and sharing auth.
+- **Full app(s)**: clone one or more complete apps into a workspace. Pick Mail + Calendar + Forms and you get all three wired up and sharing auth.
 - **Chat**: a single app with a minimal chat UI and the browser shell already wired, the simplest way to get a UI.
 - **Headless**: a single action-first app with no UI shell. The CLI walks you through calling your first action and agent, and you can add a UI later.
 
 Prefer flags? `create my-app --template mail`, `--headless`, or `--standalone` skip the prompt.
 
-## The Best of Both Worlds
-
-|                   | SaaS Tools         | Raw AI Agents           | Internal Tools             | Agent-Native            |
-| ----------------- | ------------------ | ----------------------- | -------------------------- | ----------------------- |
-| **UI**            | Polished but rigid | None                    | Mixed quality              | Full UI, fork & go      |
-| **AI**            | Bolted on          | Powerful                | Shallowly connected        | Agent-first, integrated |
-| **Customization** | Can't              | Instructions and skills | Full, but high maintenance | Agent modifies the app  |
-| **Ownership**     | Rented             | Somewhat yours          | You own the code           | You own the code        |
+See the full [getting started docs](https://agent-native.com/docs).
 
 ## Community
 

package/corpus/core/CHANGELOG.md

@@ -1,5 +1,23 @@
 # @agent-native/core
 
+## 0.84.37
+
+### Patch Changes
+
+- 885a0bd: Hide docs formatter guards from rendered content, refine assistant recovery status labels, and keep live background workers from being auto-retried as stuck.
+
+## 0.84.36
+
+### Patch Changes
+
+- 1cf5c2b: Remove the outer artboard outline and default backdrop fill from docs wireframe blocks while preserving rough outlines and fills for wireframe UI elements.
+- 11b8b66: Reframe getting-started and related docs around chat-first agentic applications, with no-browser apps repositioned as automation-first workflows.
+- 2d984a0: Add a portable Drizzle alias helper for backend-agnostic template queries.
+- 72a92af: Align docs wireframe status rows with labels on the left and values on the right.
+- 11b8b66: Automatically recover active chat runs that stop making real progress while the worker is still alive.
+- d04226c: Clarify the Getting Started inline result example with a shorter widget snippet and wireframe.
+- 51425d9: Render standard docs wireframe primitives and inline border dividers with sketchy rough outlines by default.
+
 ## 0.84.35
 
 ### Patch Changes

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

@@ -16,8 +16,9 @@ Actions are the single source of truth for anything your app does. Define an act
 - **A CLI command** — `pnpm action <name>` for scripting and dev loops.
 
 One definition, seven consumers. This is rung 3 of the [ladder](/docs/what-is-agent-native#the-ladder).
-If you are deciding whether to expose an operation headlessly, in chat, in an
-embedded sidecar, or as a full app screen, see [Agent Surfaces](/docs/agent-surfaces).
+In the default getting-started flow, the action first appears as an agent tool in
+chat, then as a native inline result, then as the operation behind a durable app
+page. For the full surface map, see [Agent Surfaces](/docs/agent-surfaces).
 
 <Diagram id="doc-block-xcp5x6" title="One definition, seven consumers" summary={"A single defineAction() fans out to every surface — agent, UI, HTTP, MCP, A2A, and CLI — with one validated schema and one run() body."}>
 
@@ -93,9 +94,8 @@ For App Operations](/docs/server#actions-first).
 
 ## Start with one action {#hello-action}
 
-The primitive-first on-ramp is one action, not a template. In a headless
-scaffold such as `agent-native create my-agent --headless`, this can be the
-whole first app:
+The first operation in a chat-first app can be tiny. In the Chat template,
+replace `actions/hello.ts` or add a new file beside it:
 
 ```ts
 // actions/hello.ts
@@ -477,19 +477,19 @@ and use [MCP Apps](/docs/mcp-apps) for inline UI in external MCP hosts.
 
 ```ts
 import { defineAction } from "@agent-native/core/action";
-import { ACTION_CHAT_UI_DATA_INSIGHTS_RENDERER } from "@agent-native/core/action-ui";
+import { ACTION_CHAT_UI_DATA_CHART_RENDERER } from "@agent-native/core/action-ui";
 import {
-  createDataInsightsWidgetResult,
-  dataInsightsWidgetResultSchema,
+  createDataChartWidgetResult,
+  dataChartWidgetResultSchema,
 } from "@agent-native/core/data-widgets";
 
 export default defineAction({
   description: "Summarize response trends.",
   readOnly: true,
-  outputSchema: dataInsightsWidgetResultSchema,
-  chatUI: { renderer: ACTION_CHAT_UI_DATA_INSIGHTS_RENDERER },
+  outputSchema: dataChartWidgetResultSchema,
+  chatUI: { renderer: ACTION_CHAT_UI_DATA_CHART_RENDERER },
   run: async () =>
-    createDataInsightsWidgetResult({
+    createDataChartWidgetResult({
       title: "Response trends",
       chartSeries: {
         type: "line",
@@ -500,26 +500,19 @@ export default defineAction({
           { day: "Tue", responses: 18 },
         ],
       },
-      table: {
-        columns: [
-          { key: "day", label: "Day" },
-          { key: "responses", label: "Responses", align: "right" },
-        ],
-        rows: [
-          { day: "Mon", responses: 12 },
-          { day: "Tue", responses: 18 },
-        ],
-      },
     }),
 });
 ```
 
 The built-in discriminants are `"data-table"`, `"data-chart"`, and
 `"data-insights"`, with server-safe builders and schemas in
-`@agent-native/core/data-widgets`. See [Native Chat UI](/docs/native-chat-ui)
-for the full result contract and BYO runtime guidance, or
+`@agent-native/core/data-widgets`. Use `data-chart` for chart-only answers,
+`data-table` for SQL/list results, and `data-insights` only when a combined
+summary/chart/table card is the right output. See
+[Native Chat UI](/docs/native-chat-ui) for the full result contract and BYO
+runtime guidance, or
 [Agent Surfaces](/docs/agent-surfaces) for how the same action can stay
-headless, render in chat, or grow into a full screen.
+automation-friendly, render in chat, or grow into a full screen.
 
 ## Calling it from the CLI {#cli}
 

package/corpus/core/docs/content/agent-surfaces.mdx

@@ -1,54 +1,56 @@
 ---
 title: "Agent Surfaces"
-description: "Use Agent-Native headlessly, as rich chat, inside an existing app, or as a full agent-native application."
-search: "headless agent rich chat full app BYO agent runtime AgentChatRuntime embed actions MCP A2A HTTP CLI"
+description: "Choose how an agentic app grows from chat to inline UI, durable app pages, embedded sidecars, automation, and external agent access."
+search: "agentic app rich chat native chat UI full app automation headless BYO agent runtime AgentChatRuntime embed actions MCP A2A HTTP CLI"
 ---
 
 # Agent Surfaces
 
-Agent-Native is deliberately composable. You can use the agent without much UI,
-use the UI without the built-in agent runtime, or use both together as a full
-application.
+Agent-Native is deliberately composable. Most apps start with chat, add actions,
+render structured results inline, and then grow durable pages around the same
+SQL state. The same action surface can also power embedded sidecars,
+automation-first jobs, external agents, and custom chat runtimes.
 
 The useful way to choose is not by protocol first. Choose the product surface
 you want, then use the matching primitive.
 
 | Surface                       | Use it when                                                                                                 | Start with                                                                                  |
 | ----------------------------- | ----------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
-| **Headless agent**            | Code, jobs, scripts, another app, or another agent should call the work directly.                           | `agent-native create --headless`, `defineAction`, `agent-native agent`, HTTP, CLI, MCP, A2A |
 | **Rich chat on Agent-Native** | You want a standalone or embedded chat backed by the built-in agent loop.                                   | [Chat template](/docs/template-chat), `<AgentChatSurface>`, `<AssistantChat>`               |
+| **Native inline UI**          | Action results should render as first-party tables, charts, cards, approvals, or compact reports in chat.   | [Native Chat UI](/docs/native-chat-ui), `chatUI.renderer`, data widget helpers              |
 | **Generated inline UI**       | The agent should create temporary or reusable controls, pickers, calculators, or visualizers inside chat.   | [Generative UI](/docs/generative-ui), `render-inline-extension`, `create-extension`         |
-| **Rich chat on your agent**   | You built the agent elsewhere and want Agent-Native's composer, transcript, tool cards, and native widgets. | `AgentChatRuntime`, `<AssistantChat runtime={runtime}>`                                     |
-| **Embedded sidecar**          | You already have a SaaS app and want an agent beside it with page context and host commands.                | `createAgentNativeEmbeddedPlugin()`, `AgentNativeEmbedded`                                  |
 | **Full application**          | Humans and agents should share durable screens, data, navigation, and collaboration.                        | Templates, actions, SQL state, context awareness                                            |
+| **Embedded sidecar**          | You already have a SaaS app and want an agent beside it with page context and host commands.                | `createAgentNativeEmbeddedPlugin()`, `AgentNativeEmbedded`                                  |
+| **Automation-first app**      | Jobs, scripts, another app, or another agent should call the work directly without a browser UI.            | `agent-native create --headless`, `defineAction`, `agent-native agent`, HTTP, CLI, MCP, A2A |
+| **Rich chat on your agent**   | You built the agent elsewhere and want Agent-Native's composer, transcript, tool cards, and native widgets. | `AgentChatRuntime`, `<AssistantChat runtime={runtime}>`                                     |
 
-Those are stages, not separate products. A workflow can start as a headless
-agent with one action, appear in chat as a table or chart, and later become a
-full screen in an app without changing the operation the agent calls.
+Those are stages and deployment shapes, not separate products. A workflow can
+start in chat, appear as a native table or chart, become a durable page in the
+app, and still run from jobs, scripts, MCP, or A2A without changing the operation
+the agent calls.
 
 <Diagram id="doc-block-hvdxgh" title="The surface spectrum" summary={"One action surface, four product shapes — each adds UI without changing the operation underneath."}>
 
 ```html
 <div class="diagram-spectrum">
   <div class="diagram-card">
-    <strong>Headless</strong
-    ><small class="diagram-muted">actions, jobs, scripts, other agents</small>
+    <strong>Chat</strong
+    ><small class="diagram-muted">composer, transcript, tool calls</small>
   </div>
   <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
   <div class="diagram-card">
-    <strong>Rich chat</strong
-    ><small class="diagram-muted">composer, transcript, tool cards</small>
+    <strong>Inline UI</strong
+    ><small class="diagram-muted">tables, charts, cards</small>
   </div>
   <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
   <div class="diagram-card">
-    <strong>Embedded sidecar</strong
-    ><small class="diagram-muted">agent beside an existing app</small>
+    <strong>App page</strong
+    ><small class="diagram-muted">durable screens, SQL data</small>
   </div>
   <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
   <div class="diagram-card accent-card">
-    <span class="diagram-pill accent">most UI</span
-    ><strong>Full application</strong
-    ><small class="diagram-muted">durable screens, data, collaboration</small>
+    <span class="diagram-pill accent">most UI</span><strong>Automation</strong
+    ><small class="diagram-muted">jobs, scripts, external agents</small>
   </div>
 </div>
 <div class="diagram-base" data-rough>
@@ -85,27 +87,26 @@ full screen in an app without changing the operation the agent calls.
 
 </Diagram>
 
-## Headless agent {#headless}
+## Automation-first app {#headless}
 
-Use the headless path when no one needs to stare at a custom app screen while
+Use the automation-first path when no one needs a custom browser screen while
 the work runs: scheduled jobs, integrations, backend workflows, CLI loops,
 another agent, or an existing product calling into Agent-Native.
 
-This is also the shape to reach for when **the agent _is_ the product** — the
-app-agent loop is the front door, not a dashboard. You send a request from the
-terminal, Slack, email, a scheduled job, another agent, or Chat — "summarize my
-unread emails," "post the daily metrics to Slack," "find the candidates who
-replied last week" — and the agent acts and returns the result wherever it
-belongs. It is still a real app, not a stateless prompt: actions, auth sessions,
-app state, thread/run history, settings, credentials, and share records all live
-in SQL.
+This is the shape to reach for when automation is the product surface. You send
+a request from the terminal, Slack, email, a scheduled job, another agent, or
+Chat — "summarize my unread emails," "post the daily metrics to Slack," "find
+the candidates who replied last week" — and the agent acts and returns the
+result wherever it belongs. It is still a real app, not a stateless prompt:
+actions, auth sessions, app state, thread/run history, settings, credentials,
+and share records all live in SQL.
 
 Pick this pattern when:
 
 - **The work happens in the background.** Most of the value is created while the user isn't looking — triage agents, daily-report agents, on-call responders.
 - **The output leaves the app.** The agent posts to Slack, sends email, or updates a third-party system; there's nothing to browse in-app.
 - **The domain is one-shot.** Research bot, summary generator, report writer — no persistent object that needs a list view.
-- **You're prototyping.** Ship the agent now; add richer UI later if users want one.
+- **You're prototyping an automation.** Ship the operation now; add chat or app pages when users need to inspect and steer it.
 
 If your product is built around persistent objects users browse, pivot, and
 share — emails, events, documents, charts — pick a [full application](#full-application)
@@ -113,11 +114,11 @@ or a [template](/docs/cloneable-saas) instead; those add a full UI _plus_ the ag
 
 ### What ships in the box {#in-the-box}
 
-A headless app skips weeks of dashboard work, and it's channel-agnostic from day
-one — the same agent runs from the web, Slack, Telegram, email, and other agents
-because everything goes through the agent, not the UI. The trade-off is there's
-no "browse-everything-at-a-glance" view; if users need that, mix patterns and
-add a small status page or list view.
+An automation-first app skips dashboard work, and it is channel-agnostic from
+day one — the same agent runs from the web, Slack, Telegram, email, and other
+agents because everything goes through the same actions. The trade-off is there
+is no "browse-everything-at-a-glance" view; if users need that, start from
+[Chat](/docs/template-chat) or add a small status page or list view.
 
 When you add the built-in Chat shell, the framework provides five management
 surfaces you don't have to build: **Chat** (the main input), **Workspace**
@@ -128,7 +129,7 @@ enough — talk to it, see what it's done, configure how it behaves. Reach for
 [Dispatch template](/docs/template-dispatch) for a workspace-style starting
 point with Slack/Telegram, scheduled jobs, and shared secrets out of the box.
 
-The smallest local path is a headless agent scaffold plus one action:
+The smallest no-browser local path is a scaffold plus one action:
 
 ```bash
 npx @agent-native/core@latest create my-agent --headless
@@ -184,8 +185,8 @@ Every `defineAction` is auto-mounted at `/_agent-native/actions/<name>`. The JSO
 
 This is not a no-database or stateless mode. The app-agent loop stores sessions,
 threads, runs, settings, credentials, application state, and share records in
-SQL. Local development defaults to SQLite; hosted headless apps should use a
-persistent SQL database.
+SQL. Local development defaults to SQLite; hosted automation-first apps should
+use a persistent SQL database.
 
 If you need the whole agent loop headlessly from the project folder, use:
 
@@ -208,14 +209,14 @@ await runAgentLoop({ engine, model, systemPrompt, actions, messages, send });
 ```
 
 For most apps, scheduled prompts and integration webhooks already call this loop
-for you. Reach for it directly only when building a custom headless host, eval
+for you. Reach for it directly only when building a custom no-browser host, eval
 runner, or server-side orchestration surface — see [Server — Production agent
 handler](/docs/server#agent-handler) for the full signature.
 
 ### Running against a folder {#folder-loop}
 
 If your goal is "run an agent against this folder," start with the app-agent
-loop in that folder: scaffold the headless app, add actions/instructions, run
+loop in that folder: scaffold the automation-first app, add actions/instructions, run
 `pnpm agent "..."`. That keeps the work inside the same action/runtime/state
 contract the app will use in production.
 
@@ -226,7 +227,7 @@ start a local agent-native workflow.
 
 ### Cloud repo access {#cloud-repo-access}
 
-For cloud headless apps that need repository access, use the GitHub connector
+For cloud automation-first apps that need repository access, use the GitHub connector
 plus token CRUD model: list repositories, search files, read files, create or
 edit files, delete files, and revoke access through provider-scoped
 credentials. In local development, set the target repository explicitly:
@@ -242,11 +243,11 @@ through the connector layer.
 
 ### Sharing sessions and runs {#sharing-runs}
 
-Headless sessions and runs are durable objects. Shareability should be phased:
-read/share links first, so teammates can inspect sanitized prompts, outputs,
-and run status; permissioned writable collaboration later, so continuing a run,
-approving actions, editing schedules, or changing configuration goes through
-explicit access checks.
+Automation-first sessions and runs are durable objects. Shareability should be
+phased: read/share links first, so teammates can inspect sanitized prompts,
+outputs, and run status; permissioned writable collaboration later, so
+continuing a run, approving actions, editing schedules, or changing
+configuration goes through explicit access checks.
 
 ## Rich chat on Agent-Native {#rich-chat}
 
@@ -487,14 +488,15 @@ want a complete product shape.
 
 ## How to choose {#how-to-choose}
 
-| If you are thinking...                                          | Choose                    |
-| --------------------------------------------------------------- | ------------------------- |
-| "I just need a callable tool or workflow."                      | Headless agent            |
-| "I want the framework's agent, but chat should be the main UI." | Rich chat on Agent-Native |
-| "I want the agent to make an interactive control right now."    | Generated inline UI       |
-| "I already have an agent; I need a polished chat UI for it."    | Rich chat on your agent   |
-| "I already have a SaaS app; add an agent beside it."            | Embedded sidecar          |
-| "The agent and UI should evolve together as the product."       | Full application          |
+| If you are thinking...                                           | Choose                    |
+| ---------------------------------------------------------------- | ------------------------- |
+| "I want the framework's agent, but chat should be the main UI."  | Rich chat on Agent-Native |
+| "The action result should be a chart, table, or typed card."     | Native inline UI          |
+| "I want the agent to make an interactive control right now."     | Generated inline UI       |
+| "The agent and UI should evolve together as the product."        | Full application          |
+| "I already have a SaaS app; add an agent beside it."             | Embedded sidecar          |
+| "I need a callable workflow for jobs, scripts, or other agents." | Automation-first app      |
+| "I already have an agent; I need a polished chat UI for it."     | Rich chat on your agent   |
 
 Keep the contract small: define durable operations as actions, return explicit
 widget results when chat needs rich UI, and add full screens only when users
@@ -502,11 +504,12 @@ need to browse, compare, configure, or collaborate over persistent objects.
 
 ## Related docs {#related-docs}
 
-- [Actions](/docs/actions) — define the headless operation once.
+- [Actions](/docs/actions) — define the operation once.
 - [Native Chat UI](/docs/native-chat-ui) — render typed action results in chat.
 - [Generative UI](/docs/generative-ui) — generate transient or persisted sandboxed UI inline in chat.
 - [Drop-in Agent](/docs/drop-in-agent) — mount chat, sidebar, or panel surfaces.
 - [Component API](/docs/components) — lower-level React chat/composer pieces.
 - [Embedding SDK](/docs/embedding-sdk) — add Agent-Native to an existing app.
+- [Automation-First Apps](/docs/pure-agent-apps) — no-browser apps for jobs, queues, scripts, and external agents.
 - [External Agents](/docs/external-agents) — connect MCP-compatible hosts to an app.
 - [A2A Protocol](/docs/a2a-protocol) — call agents from other agents.

package/corpus/core/docs/content/cloneable-saas.mdx

@@ -30,7 +30,7 @@ Each one is a real app you could use today, and the launching pad for your own v
 | [**Plan**](/docs/template-plan)           | Visual plans and PR recaps with diagrams, wireframes, and annotations.                                         |
 | [**Dispatch**](/docs/template-dispatch)   | The workspace control plane: shared secrets, reusable integrations, Slack/Telegram, scheduled jobs.            |
 
-Don't want a domain app? Use [Chat](/docs/template-chat) when you want a basic app users can talk to immediately, or start with an action in [Pure-Agent Apps](/docs/pure-agent-apps).
+Don't want a domain app? Use [Chat](/docs/template-chat) when you want a basic app users can talk to immediately and extend with actions, native results, and screens. Use [Automation-First Apps](/docs/pure-agent-apps) only when the workflow truly does not need a browser UI yet.
 
 See the full catalog under [Apps](/apps), or jump straight to one — for example, [Dispatch](/docs/template-dispatch) is a great place to start if you want a workspace-style app.
 
@@ -168,7 +168,7 @@ Not ready to scaffold? You can add agent-native superpowers to a coding agent yo
 
 ## Building on this
 
-- [**Getting Started**](/docs/getting-started) — create a minimal chat app or headless agent
+- [**Getting Started**](/docs/getting-started) — create a chat-first app, add an action, render a structured result, and grow into a page
 - [**Messaging the agent**](/docs/messaging) — how users (and you) talk to the agent that ships with each template
 - [**Multi-App Workspace**](/docs/multi-app-workspace) — bundle several templates into one workspace that shares auth, brand, and agent
 - [**Dispatch**](/docs/template-dispatch) — the workspace control plane template
@@ -182,7 +182,7 @@ If you're scaffolding now, the CLI command is:
 npx @agent-native/core@latest create my-platform
 ```
 
-You'll get a multi-select picker. Pick one app (standalone) or several (workspace — apps share auth, brand, agent config, and database). Each picked template is scaffolded into `apps/<name>/` with every file you need. For an action-only app instead of a template UI, use `npx @agent-native/core@latest create my-agent --headless`.
+You'll get a multi-select picker. Pick one app (standalone) or several (workspace — apps share auth, brand, agent config, and database). Each picked template is scaffolded into `apps/<name>/` with every file you need. For a no-browser automation instead of a template UI, use `npx @agent-native/core@latest create my-agent --headless`.
 
 Fill in `.env` (mostly `ANTHROPIC_API_KEY` and `DATABASE_URL`), `pnpm install`, `pnpm dev`, and it works. No "TODO: implement login," no placeholder routes.
 

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

@@ -11,15 +11,15 @@ Common questions about agent-native, organized from "I'm just looking" to "I'm w
 
 ### What is agent-native? {#what-is-agent-native}
 
-Agent-native is a framework for building apps where the AI agent and the product surface around it are equal partners. That surface can start as a headless agent with one custom action, grow into rich chat, or become a full UI. The invariant is that agents and humans share the same actions, database, and state. See [What Is Agent-Native?](/docs/what-is-agent-native) for the full explanation.
+Agent-native is a framework for building apps where the AI agent and the product surface around it are equal partners. The usual path starts with chat, adds typed actions, renders structured results inline, and grows into durable pages around the same SQL state. The invariant is that agents and humans share the same actions, database, and state. See [What Is Agent-Native?](/docs/what-is-agent-native) for the full explanation.
 
 ### Who is this for? {#who-is-this-for}
 
 Agent-native is for people who want a real app and an AI agent to work from the same data and actions. The common paths are:
 
 - **Use a hosted app** if you want Mail, Calendar, Forms, Plan, or another finished template with no setup — start at the [template gallery](/templates).
-- **Start with Chat** if you want a basic app users can talk to immediately, then extend with actions and screens — start with [Getting Started](/docs/getting-started) or [Chat](/docs/template-chat).
-- **Start primitive-first** if you want one action and a headless app-agent loop before committing to UI — start with [Getting Started](/docs/getting-started).
+- **Start with Chat** if you want the default from-scratch path: users can talk to the agent immediately, then you extend with actions, native results, and screens — start with [Getting Started](/docs/getting-started) or [Chat](/docs/template-chat).
+- **Start automation-first** if you are building scheduled jobs, queues, scripts, integration workers, or external-agent workflows with no browser UI yet — start with [Automation-First Apps](/docs/pure-agent-apps).
 - **Fork and customize a template** if you want your own SaaS product with auth, database, UI, and agent actions already wired — see [Templates](/docs/cloneable-saas).
 - **Build from scratch** if you want the framework primitives for a new agent-driven product — start with [Getting Started](/docs/getting-started).
 - **Connect another agent or code tool** if you want Claude, ChatGPT, Codex, Cursor, or GitHub Copilot / VS Code to use an agent-native app — see [External Agents](/docs/external-agents) and [Skills Guide](/docs/skills-guide).
@@ -130,7 +130,7 @@ That's the whole point. Fork a template and customize it by asking the agent. "A
 
 ### Can I build something the templates don't cover? {#build-from-scratch}
 
-Yes. If you want a basic chat app, run `npx @agent-native/core@latest create my-chat-app --template chat`; you get durable chat threads, actions, auth, SQL-backed runtime state, and room to add your own screens. If you want the smallest action-first app with no UI, run `npx @agent-native/core@latest create my-agent --headless`. See [Getting Started](/docs/getting-started), [Pure-Agent Apps](/docs/pure-agent-apps), and [Chat](/docs/template-chat).
+Yes. If you want a basic agentic app, run `npx @agent-native/core@latest create my-chat-app --template chat`; you get durable chat threads, actions, auth, SQL-backed runtime state, native inline result rendering, and room to add your own screens. If you are building a no-browser automation, run `npx @agent-native/core@latest create my-agent --headless`. See [Getting Started](/docs/getting-started), [Automation-First Apps](/docs/pure-agent-apps), and [Chat](/docs/template-chat).
 
 ### Can I try it without forking a template? {#try-with-a-skill}