@agent-native/core 0.8.2 → 0.10.0

package/docs/content/template-clips.md

@@ -52,7 +52,7 @@ Clips is a larger template with a native recorder (it ships a desktop companion
 
 ### Customize it
 
-Clips is a full cloneable SaaS — fork it and ask the agent to extend it. Some examples:
+Clips is a complete, cloneable template — fork it and ask the agent to extend it. Some examples:
 
 - "Add a filler-word removal button that strips ums and uhs from the transcript and re-stitches the video."
 - "Auto-post my standup notes to Slack #eng whenever a meeting ends." (Connect Slack first via [Messaging](/docs/messaging).)
@@ -61,10 +61,10 @@ Clips is a full cloneable SaaS — fork it and ask the agent to extend it. Some
 - "Add a 'Generate blog post from this clip' button that drafts a post from the transcript and saves it as a draft."
 - "Let viewers leave timestamped reactions on a shared clip."
 
-The agent edits routes, components, the transcript pipeline, and the schema as needed. See [Cloneable SaaS](/docs/cloneable-saas) for the full clone, customize, deploy flow, and [Getting Started](/docs/getting-started) if this is your first agent-native template.
+The agent edits routes, components, the transcript pipeline, and the schema as needed. See [Templates](/docs/cloneable-saas) for the full clone, customize, deploy flow, and [Getting Started](/docs/getting-started) if this is your first agent-native template.
 
 ## What's next
 
-- [**Cloneable SaaS**](/docs/cloneable-saas) — the clone-and-own model
+- [**Templates**](/docs/cloneable-saas) — the clone-and-own model
 - [**Context Awareness**](/docs/context-awareness) — how the agent knows the current clip and playhead
 - [**Agent Teams**](/docs/agent-teams) — delegate transcript cleanup to a specialist sub-agent

package/docs/content/template-design.md

@@ -36,7 +36,7 @@ pnpm dlx @agent-native/core create my-design --template design --standalone
 
 ### Customize It
 
-Design is a cloneable SaaS template. Some practical extension ideas:
+Design is a complete, cloneable template. Some practical extension ideas:
 
 - "Add a reusable ecommerce design system with our tokens and sample components."
 - "Add an export step that uploads the ZIP to our internal review system."
@@ -44,10 +44,10 @@ Design is a cloneable SaaS template. Some practical extension ideas:
 - "Add a saved prompt library for product-page, dashboard, and onboarding-screen briefs."
 - "Add a custom PDF export preset for stakeholder review."
 
-The agent edits routes, components, actions, and SQL-backed models as needed. See [Cloneable SaaS](/docs/cloneable-saas) for the full clone, customize, deploy flow, and [Getting Started](/docs/getting-started) if this is your first agent-native template.
+The agent edits routes, components, actions, and SQL-backed models as needed. See [Templates](/docs/cloneable-saas) for the full clone, customize, deploy flow, and [Getting Started](/docs/getting-started) if this is your first agent-native template.
 
 ## What's Next
 
-- [**Cloneable SaaS**](/docs/cloneable-saas) — the clone-and-own model
+- [**Templates**](/docs/cloneable-saas) — the clone-and-own model
 - [**Context Awareness**](/docs/context-awareness) — how the agent knows what the user is viewing
 - [**Creating Templates**](/docs/creating-templates) — current build patterns for agent-native templates

package/docs/content/template-dispatch.md

@@ -73,7 +73,7 @@ Dispatch is usually scaffolded into a workspace alongside the apps it coordinate
 
 ## Customize it {#customize}
 
-Dispatch is a full cloneable SaaS like any other template — see [Cloneable SaaS](/docs/cloneable-saas). Ask the agent to "add a new integration for Datadog" or "route Slack DMs from channel X to the issues agent" and it'll edit the routing config, add the webhook handler, and wire it up.
+Dispatch is a full template like any other — see [Templates](/docs/cloneable-saas). Ask the agent to "add a new integration for Datadog" or "route Slack DMs from channel X to the issues agent" and it'll edit the routing config, add the webhook handler, and wire it up.
 
 For workspace-specific management screens, add local React Router pages and
 register them in `app/dispatch-extensions.tsx`. The generated workspace owns

package/docs/content/template-forms.md

@@ -64,6 +64,6 @@ If you need new capabilities such as file uploads, signatures, or custom field w
 
 ## What's Next
 
-- [**Cloneable SaaS**](/docs/cloneable-saas) — the clone-and-own model
+- [**Templates**](/docs/cloneable-saas) — the clone-and-own model
 - [**Actions**](/docs/actions) — the action system powering the builder
 - [**Messaging**](/docs/messaging) — Slack and other submission destinations

package/docs/content/template-mail.md

@@ -98,7 +98,7 @@ pnpm dev
 Or add Mail to an existing agent-native workspace:
 
 ```bash
-agent-native add-app
+npx @agent-native/core add-app
 ```
 
 ### Key features (technical)

package/docs/content/what-is-agent-native.md

@@ -61,7 +61,7 @@ Even when the agent does all the heavy lifting, humans still need to:
 - **Inspect its work** — review drafts, audit history, roll back mistakes
 - **Share its output** — dashboards, reports, forms, links to send to teammates
 
-At minimum, "a UI for the agent" is an observability and management dashboard. At maximum, it's a full SaaS app with the agent embedded as a co-pilot. Both ends count as agent-native — see [Pure-Agent Apps](/docs/pure-agent-apps) for the minimal end and [Cloneable SaaS](/docs/cloneable-saas) for the maximal end.
+At minimum, "a UI for the agent" is an observability and management dashboard. At maximum, it's a full SaaS app with the agent embedded as a co-pilot. Both ends count as agent-native — see [Pure-Agent Apps](/docs/pure-agent-apps) for the minimal end and [Templates](/docs/cloneable-saas) for the maximal end.
 
 ## Why every app benefits from an agent {#why-every-app-benefits-from-an-agent}
 
@@ -120,7 +120,7 @@ The vision: fewer handoffs, one person doing the work of a small team.
 
 ## Fork and customize {#fork-and-customize}
 
-Agent-native apps follow a fork-and-customize model. You start from a **cloneable SaaS** template — Mail, Calendar, Analytics, Slides, Clips, Design, Forms, Dispatch — and make it yours:
+Agent-native apps follow a fork-and-customize model. You start from a **template** — Mail, Calendar, Analytics, Slides, Clips, Design, Forms, Dispatch — and make it yours. Each one is a complete, working SaaS product you fork wholesale, not a blank scaffold:
 
 1. Pick a template on [agent-native.com/templates](/templates)
 2. Use it immediately as a hosted app (e.g. mail.agent-native.com)
@@ -128,7 +128,7 @@ Agent-native apps follow a fork-and-customize model. You start from a **cloneabl
 4. The agent modifies the code to match your needs
 5. Deploy your fork to your own domain — or stay on agent-native.com
 
-Because it's _your_ app, not shared infrastructure, the agent can safely evolve the code. Your app keeps improving as you use it. See [Cloneable SaaS](/docs/cloneable-saas) for the full story.
+Because it's _your_ app, not shared infrastructure, the agent can safely evolve the code. Your app keeps improving as you use it. See [Templates](/docs/cloneable-saas) for the full story.
 
 ## Composable agents {#composable-agents}
 
@@ -176,7 +176,7 @@ One action, four surfaces: the agent calls it as a tool, the UI calls it as a ty
 
 - [**Getting Started**](/docs) — pick a template and run it
 - [**Key Concepts**](/docs/key-concepts) — the architecture: SQL, actions, polling sync, context awareness, portability
-- [**Cloneable SaaS**](/docs/cloneable-saas) — templates as complete products you own
+- [**Templates**](/docs/cloneable-saas) — templates as complete products you own
 - [**Workspace**](/docs/workspace) — the per-user customization layer (skills, memory, instructions, MCP) backed by SQL, not files
 - [**Dispatch**](/docs/dispatch) — the workspace control plane: secrets vault, Slack/email inbox, cross-app delegation
 - [**Extensions**](/docs/extensions) — sandboxed mini-apps the agent creates instantly without code changes

package/docs/content/workspace.md

@@ -20,7 +20,7 @@ The twist: **it's SQL rows, not filesystem files.** Each user gets their own wor
 | Per-project `CLAUDE.md` / skills | Per-app `AGENTS.md` + workspace memory resources   |
 | MCP config in a JSON file        | MCP config in JSON _or_ the settings UI, per scope |
 
-Same capabilities. Different economics. See [Cloneable SaaS](/docs/cloneable-saas) for why this matters for SaaS.
+Same capabilities. Different economics. See [Templates](/docs/cloneable-saas) for why this matters for SaaS.
 
 ## The Workspace tab {#the-tab}
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.8.2",
+  "version": "0.10.0",
   "type": "module",
   "description": "Framework for agent-native application development — where AI agents and UI share state via files",
   "license": "MIT",