@agent-native/core 0.124.3 → 0.124.4

package/README.md

@@ -27,7 +27,7 @@ https://github.com/user-attachments/assets/ef51644b-6506-46d8-8083-0af7b7e5b65c
 
 ## Try an Agent-Native app
 
-Fork a working app and let the agent evolve it. **You can customize everything.**
+Start from a working app and let the agent evolve it. **You can customize everything.**
 
 <table>
 <tr>

package/corpus/README.md

@@ -28,6 +28,6 @@ rg -n "defineAction|useActionQuery" node_modules/@agent-native/core/corpus
 
 ## Generated Counts
 
-- core files: 1736
+- core files: 1737
 - toolkit files: 160
-- template files: 6791
+- template files: 6803

package/corpus/core/CHANGELOG.md

@@ -1,5 +1,15 @@
 # @agent-native/core
 
+## 0.124.4
+
+### Patch Changes
+
+- c849ba0: Recover clicked routes in the desktop app when a stale lazy route chunk is encountered.
+- c849ba0: Label final-response-guard corrective retries as framework directives. They are
+  appended as user-role messages, so an unlabeled one reads like an injected user
+  turn — models were refusing them out loud to the real user ("this message looks
+  like a prompt injection attempt") instead of revising the draft.
+
 ## 0.124.3
 
 ### Patch Changes

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

@@ -1,13 +1,13 @@
 ---
 title: "Templates"
-description: "Fork a working SaaS product and make it yours — agent included."
+description: "Start from a working SaaS product and make it yours — agent included."
 ---
 
 # Templates
 
 Want to ship your own AI-powered analytics tool? Mail client? Forms builder? Pick a template, and you've got a working SaaS in minutes — agent, database, auth, and deploy pipeline already wired up.
 
-Most starter templates give you a blank scaffold and a long TODO list. Agent-native flips that. Each template is a **complete, SaaS-grade product** — already runnable on day one, already shippable, and entirely yours to customize, brand, and deploy. Think of them as cloneable SaaS, not starter kits: you're forking a finished product, not staring at boilerplate.
+Most starter templates give you a blank scaffold and a long TODO list. Agent-native flips that. Each template is a **complete, SaaS-grade product** — already runnable on day one, already shippable, and entirely yours to customize, brand, and deploy. Think of them as Cloneable SaaS, not starter kits: you're starting from a finished product, not staring at boilerplate.
 
 Building a workflow with no browser UI at all — a Slack bot, a nightly report, a webhook responder? See [Automation-First Apps](/docs/pure-agent-apps) instead; the templates on this page all ship a full browser UI alongside the agent.
 
@@ -52,7 +52,7 @@ This isn't a theoretical claim. The framework's author runs his actual inbox on
 
 The path from "I want my own SaaS" to "I have my own SaaS" is short:
 
-<Diagram id="doc-block-1ab5jb9" title="Fork and customize" summary="Pick a finished product, brand it, evolve it in plain English, and ship it to your own domain.">
+<Diagram id="doc-block-1ab5jb9" title="Start from a working app" summary="Pick a finished product, brand it, evolve it in plain English, and ship it to your own domain.">
 
 ```html
 <div class="diagram-fork">
@@ -105,18 +105,18 @@ The path from "I want my own SaaS" to "I have my own SaaS" is short:
 3. **Customize it.** Ask the agent to add the column you need, change how the inbox groups, connect to your internal API, add a new view. The agent edits the code; you review the diff.
 4. **Ship it.** Run the deploy command. You now have your own production SaaS at your own domain.
 
-Steps 2–4 typically take days, not months. Step 3 is open-ended — your forked SaaS evolves over time, in plain English, by talking to the agent.
+Steps 2–4 typically take days, not months. Step 3 is open-ended — your customized SaaS evolves over time, in plain English, by talking to the agent.
 
 ## Why this is practical {#why}
 
-A traditional fork-the-codebase model breaks down at scale: every user maintaining their own inbox sounds like a maintenance nightmare. Two framework decisions make it work:
+A separate-codebase-per-user model breaks down at scale: every user maintaining their own inbox sounds like a maintenance nightmare. Two framework decisions make it work:
 
-1. **The agent does the maintenance.** You don't write code to add a column or wire a new integration — you ask the agent. So "your own forked inbox" is a feature, not a burden.
+1. **The agent does the maintenance.** You don't write code to add a column or wire a new integration — you ask the agent. So "your own customized inbox" is a feature, not a burden.
 2. **Per-user customization without per-user code.** Skills, memory, instructions, connected MCP servers, and sub-agents all live in SQL. Every user gets their own customization layer; the shared codebase hosts all of them at once.
 
 The result: Claude-Code-level flexibility for each user, with normal SaaS deployment economics.
 
-<Diagram id="doc-block-bhg7mw" title="Why per-user forks scale" summary={"Two ideas keep the fork-and-customize model practical: the agent does the maintenance, and per-user customization lives in SQL — not in per-user code."}>
+<Diagram id="doc-block-bhg7mw" title="Why per-user customization scales" summary={"Two ideas keep the start-from-a-working-app model practical: the agent does the maintenance, and per-user customization lives in SQL — not in per-user code."}>
 
 ```html
 <div class="diagram-why">
@@ -159,9 +159,9 @@ The result: Claude-Code-level flexibility for each user, with normal SaaS deploy
 
 </Diagram>
 
-## Don't want to fork? {#hosted}
+## Don't want to customize? {#hosted}
 
-You don't have to. Every example app is also available as a hosted app on `agent-native.com` — `mail.agent-native.com`, `calendar.agent-native.com`, and so on. Use the hosted version for free or paid; fork only when you want to change something the hosted version doesn't expose.
+You don't have to. Every example app is also available as a hosted app on `agent-native.com` — `mail.agent-native.com`, `calendar.agent-native.com`, and so on. Use the hosted version for free or paid; create your own app from a template when you want to change something the hosted version doesn't expose.
 
 ## Try it with a skill {#try-with-a-skill}
 

package/corpus/core/docs/content/creating-templates.mdx

@@ -5,7 +5,7 @@ description: "How to create and publish your own agent-native app templates."
 
 # Creating Templates
 
-Templates are complete, forkable agent-native apps that solve a real workflow. The first-party templates are built with the same framework surface you use: React routes for the UI, Drizzle SQL for data, actions for operations, workspace resources for agent behavior, and polling sync so the agent and UI stay aligned.
+Templates are complete, cloneable agent-native apps that solve a real workflow. The first-party templates are built with the same framework surface you use: React routes for the UI, Drizzle SQL for data, actions for operations, workspace resources for agent behavior, and polling sync so the agent and UI stay aligned.
 
 Use `@agent-native/core` for the runtime contract: actions, server plugins,
 database helpers, app state, routing helpers, and agent chat. Use
@@ -536,6 +536,6 @@ workspace pointed at current build output.
 - [**Multi-App Workspace**](/docs/multi-app-workspace) — make the template fit
   naturally alongside sibling apps and Dispatch.
 - [**Syncing Template Changes**](/docs/syncing-template-changes) — pull later
-  upstream template fixes into an app that already forked from it.
+  upstream template fixes into an app that was already created from it.
 - [**Templates**](/docs/cloneable-saas) — turn a template into a
   publishable product you can share and deploy.

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

@@ -441,6 +441,29 @@ export default defineConfig({
 });
 ```
 
+## Cloudflare Workers {#cloudflare-workers}
+
+Use Nitro's native module output for a Cloudflare Worker. This keeps SSR
+enabled and emits the Worker entry point plus static assets under
+`.output/server` and `.output/public`:
+
+```ts filename="vite.config.ts"
+export default defineConfig({
+  plugins: [agentNative({ nitro: { preset: "cloudflare_module" } })],
+});
+```
+
+Build and deploy the generated Worker with Wrangler:
+
+```bash
+npx @agent-native/core@latest build
+npx wrangler deploy --config .output/server/wrangler.json
+```
+
+You can also select the preset explicitly with
+`NITRO_PRESET=cloudflare_module`. Configure a durable external SQL database
+before deploying; a Worker filesystem is not a persistent application store.
+
 ## AWS Lambda {#aws-lambda}
 
 ```ts filename="vite.config.ts"

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

@@ -20,7 +20,7 @@ Agent-native is for people who want a real app and an AI agent to work from the
 - **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 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).
+- **Start from a template and customize it** 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).
 
@@ -126,13 +126,13 @@ The framework ships with production-ready templates including [Chat](/docs/templ
 
 ### Can I customize templates? {#can-i-customize-templates}
 
-That's the whole point. Fork a template and customize it by asking the agent. "Add a priority field to forms." "Connect to our Salesforce instance." "Change the color scheme to match our brand." The agent modifies the code, and your app evolves over time.
+That's the whole point. Start from a template and customize it by asking the agent. "Add a priority field to forms." "Connect to our Salesforce instance." "Change the color scheme to match our brand." The agent modifies the code, and your app evolves over time.
 
 ### Can I build something the templates don't cover? {#build-from-scratch}
 
 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}
+### Can I try it without starting from a template? {#try-with-a-skill}
 
 Yes — install a skill into a coding agent you already use with one command and no scaffold required. See the [Skills Guide](/docs/skills-guide#app-backed-skills) for the walkthrough.
 
@@ -252,6 +252,6 @@ The shared database, live sync, actions system, and application state only work
 
 - [**Getting Started**](/docs/getting-started) — build your first action and render it inline in chat
 - [**What Is Agent-Native?**](/docs/what-is-agent-native) — the full explanation behind the answers above
-- [**Templates**](/docs/cloneable-saas) — fork a complete SaaS product instead of starting from scratch
+- [**Templates**](/docs/cloneable-saas) — start from a complete SaaS product instead of starting from scratch
 - [**Key Concepts**](/docs/key-concepts) — the architecture: SQL, actions, polling sync, and portability
 - [**Deployment**](/docs/deployment) — host on your own domain or any Nitro-compatible provider

package/corpus/core/docs/content/key-concepts.mdx

@@ -403,7 +403,7 @@ This is a feature, not a bug. The agent can safely edit the app's source code: c
 
 There's no shared codebase to break. You own the app, and the agent evolves it for you over time:
 
-1. Fork a template (e.g. the analytics template)
+1. Start from a template (e.g. the analytics template)
 2. Customize it by asking the agent
 3. "Add a new chart type for cohort analysis" — the agent builds it
 4. "Connect to our Stripe account" — the agent writes the integration

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

@@ -35,7 +35,7 @@ Anything every app in your org should agree on can live in `packages/shared`:
 
 Each individual app becomes _just a set of screens_ — routes, dashboards, views, domain-specific actions. Framework defaults cover the rest until you add a real workspace customization.
 
-That same boundary applies when your app wants to use another first-party app. A new workspace dashboard that needs email, calendar, analytics, and company-memory context should use the existing Mail, Calendar, Analytics, and Brain apps as connected neighbors over links or A2A. It should not clone those templates, create a wrapper app that nests them, or scaffold child apps inside itself just to get access to their data or agents. Fork or scaffold a copy only when you explicitly want to customize that app.
+That same boundary applies when your app wants to use another first-party app. A new workspace dashboard that needs email, calendar, analytics, and company-memory context should use the existing Mail, Calendar, Analytics, and Brain apps as connected neighbors over links or A2A. It should not create wrapper apps that nest them or scaffold child apps inside itself just to get access to their data or agents. Start from a template only when you explicitly want to customize that app.
 
 ## Getting started {#getting-started}
 

package/corpus/core/docs/content/syncing-template-changes.mdx

@@ -5,7 +5,7 @@ description: "agent-native template pulls later upstream first-party template ch
 
 # Syncing Template Changes
 
-`agent-native create` copies a first-party template into your app and then makes it yours — substituting the app name, renaming `_gitignore`, rewriting `package.json`, pinning `workspace:*` and `catalog:` dependencies to concrete versions, and (in a workspace) swapping in inherited auth and chat plugins. From that moment the app is a fork. Fixes and improvements that land in the template upstream do not reach it.
+`agent-native create` copies a first-party template into your app and then makes it yours — substituting the app name, renaming `_gitignore`, rewriting `package.json`, pinning `workspace:*` and `catalog:` dependencies to concrete versions, and (in a workspace) swapping in inherited auth and chat plugins. From that moment the app is an independent app derived from the template. Fixes and improvements that land in the template upstream do not reach it.
 
 `agent-native upgrade` does not close that gap. It moves package versions, runs import codemods, and refreshes skill directories — it never touches a file that was copied out of a template.
 

package/corpus/core/docs/content/template-analytics-developers.mdx

@@ -1,11 +1,11 @@
 ---
 title: "Analytics: Extending the Template"
-description: "The data model, action reference, and customization points for forking and extending the Analytics template — dashboards, monitoring, errors, session replay, and the /agents admin surface."
+description: "The data model, action reference, and customization points for customizing and extending the Analytics template — dashboards, monitoring, errors, session replay, and the /agents admin surface."
 ---
 
 # Extending Analytics
 
-This page is for anyone forking the Analytics template or building on it directly: the data model, the action surface, and the places meant to be extended.
+This page is for anyone customizing the Analytics template or building on it directly: the data model, the action surface, and the places meant to be extended.
 
 ## Quick start
 

package/corpus/core/docs/content/template-analytics.mdx

@@ -115,7 +115,7 @@ Analytics is more than dashboards and the dictionary — here's everywhere you'l
 
 ## For developers
 
-Fork the Analytics template from the CLI:
+Create an Analytics app from the template via the CLI:
 
 ```bash
 npx @agent-native/core@latest create my-analytics --standalone --template analytics
@@ -129,6 +129,6 @@ See [Getting Started](/docs/getting-started) for the rest of the setup (installi
 - [**Monitoring, Errors, and Session Replay**](/docs/template-analytics-monitoring-and-sessions) — uptime, error triage, and replay
 - [**Connecting and Extending Data Sources**](/docs/template-analytics-connectors) — the full connector catalog and the escape hatches
 - [**Extending Analytics**](/docs/template-analytics-developers) — data model, actions, and customizing the template
-- [**Templates**](/docs/cloneable-saas) — the clone-and-own model, and every other domain template to start from
+- [**Templates**](/docs/cloneable-saas) — the Cloneable SaaS model, and every other domain template to start from
 - [**Getting Started**](/docs/getting-started) — the framework fundamentals: actions, application state, and live sync
 - [**Sharing**](/docs/sharing) — the share-grant model dashboards and analyses build on

package/corpus/core/docs/content/template-assets-developers.mdx

@@ -1,11 +1,11 @@
 ---
 title: "Assets — architecture and data model"
-description: "The SQL schema, access-control model, and action reference for developers forking or extending the Assets template."
+description: "The SQL schema, access-control model, and action reference for developers customizing or extending the Assets template."
 ---
 
 # Assets — architecture and data model
 
-This page is for anyone forking the [Assets](/docs/template-assets) template or extending it: the action inventory, data model, access-control rules, and the places to start when you want to change how Assets works.
+This page is for anyone customizing the [Assets](/docs/template-assets) template or extending it: the action inventory, data model, access-control rules, and the places to start when you want to change how Assets works.
 
 ## Quick start
 
@@ -384,7 +384,7 @@ needed:
 
 <FileTree
   id="doc-block-assets11"
-  title="Where to look when forking Assets"
+  title="Where to look when customizing Assets"
   entries={[
     {
       path: "templates/assets/server/db/schema.ts",

package/corpus/core/docs/content/template-assets.mdx

@@ -94,7 +94,7 @@ When you open the app, the selected library, prompt, references, and generated c
 - **Generate, refine, and review through chat or a library** — candidates, feedback, designer handoff, and the admin audit log all live in [Generating, refining, and reviewing assets](/docs/template-assets-generation).
 - **Build a preset once and let everyone else run it** — a locked prompt template, model, aspect ratio, reference board, and logo policy, so a marketer just pastes a brief and tags the preset. See [Presets: design once, run everywhere](/docs/template-assets-presets).
 - **Use Assets from another app or agent** — embed the picker, call Assets over A2A or MCP, reuse governed Creative Context, or install the Assets skill in a coding agent. See [Using Assets from other apps and agents](/docs/template-assets-integrations).
-- **Fork and extend the template** — the SQL schema, access control, and extension points live in [Assets — architecture and data model](/docs/template-assets-developers).
+- **Create your own app from the template and extend it** — the SQL schema, access control, and extension points live in [Assets — architecture and data model](/docs/template-assets-developers).
 
 ## Getting started
 
@@ -126,6 +126,6 @@ To run your own copy: `npx @agent-native/core@latest create my-assets --standalo
 - [**Generating, refining, and reviewing assets**](/docs/template-assets-generation) — candidates, feedback, designer handoff, and the audit log
 - [**Using Assets from other apps and agents**](/docs/template-assets-integrations) — the embedded picker, A2A, Creative Context, and coding-agent install
 - [**Assets — architecture and data model**](/docs/template-assets-developers) — the SQL schema, access control, and action reference
-- [**Templates**](/docs/cloneable-saas) — the clone-and-own model
+- [**Templates**](/docs/cloneable-saas) — the Cloneable SaaS model
 - [**A2A Protocol**](/docs/a2a-protocol) — how other apps call Assets
 - [**Sharing & Privacy**](/docs/sharing) — library-level access control

package/corpus/core/docs/content/template-brain-developers.mdx

@@ -1,11 +1,11 @@
 ---
 title: "Brain: Developer Guide"
-description: "Data model, action reference, and extension points for forking or self-hosting the Brain institutional-memory template."
+description: "Data model, action reference, and extension points for customizing or self-hosting the Brain institutional-memory template."
 ---
 
 # Brain: Developer Guide
 
-This page is for anyone forking the Brain template, running it as a service, or wiring another app to call it. It covers the data model, the full action inventory, how source credentials resolve, and where to make changes.
+This page is for anyone customizing the Brain template, running it as a service, or wiring another app to call it. It covers the data model, the full action inventory, how source credentials resolve, and where to make changes.
 
 ## Quick start
 

package/corpus/core/docs/content/template-brain.mdx

@@ -191,5 +191,5 @@ action reference.
 - [**Dispatch**](/docs/dispatch) — the workspace control plane
 - [**Dispatch template**](/docs/template-dispatch) — the scaffolded coordination app
 - [**A2A Protocol**](/docs/a2a-protocol) — cross-app delegation
-- [**Templates**](/docs/cloneable-saas) — the clone-and-own model, and every other domain template to start from
+- [**Templates**](/docs/cloneable-saas) — the Cloneable SaaS model, and every other domain template to start from
 - [**Getting Started**](/docs/getting-started) — the framework fundamentals: actions, application state, and live sync

package/corpus/core/docs/content/template-calendar-developers.mdx

@@ -5,7 +5,7 @@ description: "Quick start, the full action inventory, data model, routes, and ho
 
 # Developer Guide
 
-This page is for anyone forking the Calendar template or extending it: the quick start, every action, the data model, the route surface, and how to add to it. See [Calendar](/docs/template-calendar) for what the app does.
+This page is for anyone customizing the Calendar template or extending it: the quick start, every action, the data model, the route surface, and how to add to it. See [Calendar](/docs/template-calendar) for what the app does.
 
 ## Quick start
 

package/corpus/core/docs/content/template-calendar.mdx

@@ -131,7 +131,7 @@ The agent will query Google Calendar live for any schedule question — it never
 - [**Booking Links**](/docs/template-calendar-booking-links) — creating, sharing, and managing Calendly-style booking pages
 - [**Talking to the Agent**](/docs/template-calendar-agent) — prompts by task, application state, and Extensions
 - [**Developer Guide**](/docs/template-calendar-developers) — quick start, actions, data model, and routes
-- [**Templates**](/docs/cloneable-saas) — the clone-and-own model, and every other domain template to start from
+- [**Templates**](/docs/cloneable-saas) — the Cloneable SaaS model, and every other domain template to start from
 - [**Getting Started**](/docs/getting-started) — the framework fundamentals: actions, application state, and live sync
 - [**Mail**](/docs/template-mail) — a sibling domain template covering inbox and automations
 - [**Automations**](/docs/automations) — trigger jobs off calendar and booking events

package/corpus/core/docs/content/template-chat.mdx

@@ -130,7 +130,7 @@ Use it for scheduled jobs, queues, CLI loops, or external-agent workflows where
 - [**Your first feature in Chat**](/docs/template-chat-first-edits) — the starter chat route, annotated, plus a full walkthrough of adding a real feature
 - [**Chat — runtime and admin surfaces**](/docs/template-chat-developers) — core tables, auth, and the Database/Observability/Extensions pages that ship by default
 - [**Getting Started**](/docs/getting-started) — build the chat-first path from action to inline result to app page
-- [**Templates**](/docs/cloneable-saas) — the clone-and-own model, and every domain template to start from instead
+- [**Templates**](/docs/cloneable-saas) — the Cloneable SaaS model, and every domain template to start from instead
 - [**Agent Surfaces**](/docs/agent-surfaces) — chat, inline UI, app pages, embedded, automation, and external-agent patterns
 - [**Actions**](/docs/actions) — the action system chat and UI both call
 - [**Native Chat UI**](/docs/native-chat-ui) — chat surface primitives and runtime options

package/corpus/core/docs/content/template-clips-developers.mdx

@@ -1,12 +1,12 @@
 ---
 title: "Extending Clips"
-description: "Data model, action reference, and setup steps for forking, self-hosting, or extending the Clips template — recordings, transcripts, meetings, organizations, and the Chrome extension/bug-report embed."
+description: "Data model, action reference, and setup steps for customizing, self-hosting, or extending the Clips template — recordings, transcripts, meetings, organizations, and the Chrome extension/bug-report embed."
 search: "Clips developers data model actions schema self-host Chrome extension bug report embed"
 ---
 
 # Extending Clips
 
-The rest of this doc is for anyone forking the Clips template, self-hosting it, or extending it with new capabilities.
+The rest of this doc is for anyone customizing the Clips template, self-hosting it, or extending it with new capabilities.
 
 ## Quick start
 
@@ -351,7 +351,7 @@ Every agent-callable operation is a TypeScript file in `templates/clips/actions/
 
 ## Customizing it
 
-Clips is a complete, cloneable template — fork it and ask the agent to extend it. Some examples:
+Clips is a complete, cloneable template — start from 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).)
@@ -368,6 +368,6 @@ The agent edits routes, components, the transcript pipeline, and the schema as n
 - [**Capturing Everywhere**](/docs/template-clips-capture-everywhere) — desktop, mobile, Rewind, Screen Memory, and the Chrome extension from a user's perspective
 - [**Sharing, Teams, and Agent-Readable Clips**](/docs/template-clips-sharing-and-teams) — the sharing model this data model backs
 - [**AI Pipeline, Editing, and Insights**](/docs/template-clips-ai-and-editing) — the transcription and editing pipeline these actions power
-- [**Templates**](/docs/cloneable-saas) — the clone-and-own model
+- [**Templates**](/docs/cloneable-saas) — the Cloneable SaaS 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/corpus/core/docs/content/template-clips.mdx

@@ -113,7 +113,7 @@ Live demo: [clips.agent-native.com](https://clips.agent-native.com).
 - [**Capturing Everywhere**](/docs/template-clips-capture-everywhere) — the desktop app, the mobile companion, Rewind quick-save, Screen Memory, and the Chrome extension.
 - [**Sharing, Teams, and Agent-Readable Clips**](/docs/template-clips-sharing-and-teams) — visibility, passwords, organizations, and pasting a clip link into an agent.
 - [**AI Pipeline, Editing, and Insights**](/docs/template-clips-ai-and-editing) — transcription, non-destructive editing, and view analytics.
-- [**Extending Clips**](/docs/template-clips-developers) — for anyone forking or extending the template.
-- [**Templates**](/docs/cloneable-saas) — the clone-and-own model
+- [**Extending Clips**](/docs/template-clips-developers) — for anyone customizing or extending the template.
+- [**Templates**](/docs/cloneable-saas) — the Cloneable SaaS 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/corpus/core/docs/content/template-content-developers.mdx

@@ -1,11 +1,11 @@
 ---
 title: "Content: Developer Guide"
-description: "Data model, action inventory, routes, and extension points for forking or extending the Content template."
+description: "Data model, action inventory, routes, and extension points for customizing or extending the Content template."
 ---
 
 # Content: Developer Guide
 
-This page is for anyone forking the Content template or building on it: the full data model, every action grouped by area, the route surface, and the places to look when adding a feature. If you're looking for how to use the app day to day, see the [Content overview](/docs/template-content) and its linked pages instead.
+This page is for anyone customizing the Content template or building on it: the full data model, every action grouped by area, the route surface, and the places to look when adding a feature. If you're looking for how to use the app day to day, see the [Content overview](/docs/template-content) and its linked pages instead.
 
 ## Quick start
 

package/corpus/core/docs/content/template-content.mdx

@@ -117,7 +117,7 @@ See [Getting started](/docs/getting-started) for the rest of the setup (`cd`, `p
 - [**Databases, properties & forms**](/docs/template-content-databases) — inline databases, property types, views, external sources, and intake forms
 - [**Local files, Notion & Builder CMS sync**](/docs/template-content-sync) — the Obsidian-style folder workflow plus Notion and Builder CMS round-trips
 - [**Developer Guide**](/docs/template-content-developers) — data model, action inventory, routes, and how to extend the template
-- [**Templates**](/docs/cloneable-saas) — the clone-and-own model, and every other domain template to start from
+- [**Templates**](/docs/cloneable-saas) — the Cloneable SaaS model, and every other domain template to start from
 - [**Getting Started**](/docs/getting-started) — the framework fundamentals: actions, application state, and live sync
 - [**Real-Time Collaboration**](/docs/real-time-collaboration) — the Yjs pipeline documents share with other collaborative surfaces
 - [**Sharing**](/docs/sharing) — the share-grant model documents build on

package/corpus/core/docs/content/template-design-brand-and-figma.mdx

@@ -18,7 +18,7 @@ Every design system also carries an optional set of custom instructions and a de
 - **Website** — paste a URL and Design pulls colors, fonts, the favicon, and the social preview image straight off the live site.
 - **GitHub repo or code files** — Design indexes the actual CSS and tokens from your codebase, so the system matches what's really deployed rather than a guess.
 - **Documents** — DOCX, PPTX, or PDF uploads; presentations are usually the strongest signal for brand colors and fonts.
-- **An existing design or design system** — fork one you already have instead of starting over.
+- **An existing design or design system** — start from one you already have instead of starting over.
 
 When several sources come in together, Design cross-references them — code sources are the most trustworthy, the website confirms what's actually shipped, documents fill in gaps — before merging everything into one system.
 

package/corpus/core/docs/content/template-design-developers.mdx

@@ -1,11 +1,11 @@
 ---
 title: "Extending Design"
-description: "The data model, action reference, and editor extension points for forking or building on the Design template."
+description: "The data model, action reference, and editor extension points for customizing or building on the Design template."
 ---
 
 # Extending Design
 
-This page is for anyone forking the Design template or building on top of it directly: the data model, the full action surface, and how the editor's overview canvas and extension points fit together.
+This page is for anyone customizing the Design template or building on top of it directly: the data model, the full action surface, and how the editor's overview canvas and extension points fit together.
 
 ### Quick start
 

package/corpus/core/docs/content/template-design.mdx

@@ -118,7 +118,7 @@ Live demo: [design.agent-native.com](https://design.agent-native.com).
 - "Turn this repeated card into a reusable component."
 - "Export this prototype as a ZIP once the final variant is selected."
 
-Building on Design or forking the template? See [Extending Design](/docs/template-design-developers).
+Building on Design or customizing the template? See [Extending Design](/docs/template-design-developers).
 
 ## What's next
 
@@ -126,5 +126,5 @@ Building on Design or forking the template? See [Extending Design](/docs/templat
 - [**Quality Passes and Components**](/docs/template-design-quality-and-components) — the audit/screenshot pass, reusable components, motion, shaders
 - [**Review, Handoff, and Full Apps**](/docs/template-design-collaboration-and-full-apps) — visual editing, review feedback, export, and fusion mode
 - [**Extending Design**](/docs/template-design-developers) — data model, actions, and editor extension points
-- [**Templates**](/docs/cloneable-saas) — the clone-and-own model
+- [**Templates**](/docs/cloneable-saas) — the Cloneable SaaS model
 - [**Context Awareness**](/docs/context-awareness) — how the agent knows what the user is viewing

package/corpus/core/docs/content/template-dispatch-developers.mdx

@@ -1,11 +1,11 @@
 ---
 title: "Dispatch — architecture for developers"
-description: "How Dispatch's package and generated-app source are split, the orchestrator's remote agent registry, scaffolding a workspace with Dispatch, and customizing or remixing a curated workspace template."
+description: "How Dispatch's package and generated-app source are split, the orchestrator's remote agent registry, scaffolding a workspace with Dispatch, and customizing a curated workspace template."
 ---
 
 # Dispatch — architecture for developers
 
-This page is for engineers extending Dispatch or forking the template: how the orchestrator finds other agents, how the published package and your generated app source are split, and how to add your own management screens or spin up a private remix of another template.
+This page is for engineers extending Dispatch or customizing the template: how the orchestrator finds other agents, how the published package and your generated app source are split, and how to add your own management screens or create a private app from another template.
 
 ## Orchestrator agent and remote agent registry {#orchestrator}
 
@@ -104,12 +104,12 @@ For workspace-specific management screens, add local React Router pages and regi
   ]}
 />
 
-## Curated workspace template remix {#remix}
+## Create an app from a curated workspace template {#remix}
 
-Curated workspace templates are private remix sources for spinning up an independent app from a reviewed template — mail, calendar, analytics, slides, content, clips, brain, assets, forms, or design.
+Curated workspace templates are reviewed sources for creating an independent private app — mail, calendar, analytics, slides, content, clips, brain, assets, forms, or design.
 
 - **`list-curated-workspace-templates`** returns the reviewed catalog: stable metadata, the live product URL, setup guidance, and whether each source template is already installed in the current workspace.
-- **`remix-workspace-template`** creates a private, independent copy. In a local runtime it scaffolds the template directly; in a hosted workspace it starts a Builder app-creation branch instead. Either way, the remix defaults to a `<template>-remix` app id, and the request is required to use empty or synthetic seed data only — it must never copy the source app's records, credentials, secrets, or private configuration.
+- **`remix-workspace-template`** creates a private, independent app. In a local runtime it scaffolds the template directly; in a hosted workspace it starts a Builder app-creation branch instead. The existing action and `<template>-remix` app id remain stable for compatibility, while the request is required to use empty or synthetic seed data only — it must never copy the source app's records, credentials, secrets, or private configuration.
 
 ## What's next
 

package/corpus/core/docs/content/template-forms-developers.mdx

@@ -5,7 +5,7 @@ description: "The Forms template's SQL schema, its full action reference, and ho
 
 # Forms — data model and actions
 
-This page is for developers forking or extending the Forms template. It covers the SQL schema, every action the agent and UI call, and how to add new capabilities. For what the app does day to day, see [Forms](/docs/template-forms); for field types, publishing, and public-form protections, see [Building and publishing a form](/docs/template-forms-building-publishing); for response handling, see [Responses, insights, and destinations](/docs/template-forms-responses).
+This page is for developers customizing or extending the Forms template. It covers the SQL schema, every action the agent and UI call, and how to add new capabilities. For what the app does day to day, see [Forms](/docs/template-forms); for field types, publishing, and public-form protections, see [Building and publishing a form](/docs/template-forms-building-publishing); for response handling, see [Responses, insights, and destinations](/docs/template-forms-responses).
 
 ### Quick start
 

package/corpus/core/docs/content/template-forms.mdx

@@ -115,6 +115,6 @@ Live demo: [forms.agent-native.com](https://forms.agent-native.com).
 - [**Building and publishing a form**](/docs/template-forms-building-publishing) — field types, conditional logic, and public-form protections
 - [**Responses, insights, and destinations**](/docs/template-forms-responses) — analyzing, exporting, and routing submissions
 - [**Forms — data model and actions**](/docs/template-forms-developers) — the SQL schema and action reference, for developers
-- [**Templates**](/docs/cloneable-saas) — the clone-and-own model
+- [**Templates**](/docs/cloneable-saas) — the Cloneable SaaS model
 - [**Actions**](/docs/actions) — the action system powering the builder
 - [**Messaging**](/docs/messaging) — Slack and other submission destinations

package/corpus/core/docs/content/template-mail-developers.mdx

@@ -1,11 +1,11 @@
 ---
 title: "Mail: Developer Guide"
-description: "Actions, data model, routes, and customization points for the Mail template — everything you need to fork or extend the agent-native Gmail client."
+description: "Actions, data model, routes, and customization points for the Mail template — everything you need to customize or extend the agent-native Gmail client."
 ---
 
 # Developer Guide
 
-This page is for anyone forking the [Mail](/docs/template-mail) template or extending it: the action inventory, data model, route map, and the places to start when you want to change how Mail works.
+This page is for anyone customizing the [Mail](/docs/template-mail) template or extending it: the action inventory, data model, route map, and the places to start when you want to change how Mail works.
 
 ## Quick start
 

package/corpus/core/docs/content/template-mail.mdx

@@ -93,7 +93,7 @@ When you open the app, the keyboard-first inbox and thread view stay focused on
 - **Draft, schedule, and send** in your own voice, and let a teammate queue a draft for you to review before it goes out — see [Drafting, Scheduling & the Draft Queue](/docs/template-mail-drafts-and-queue).
 - **Pull CRM context onto a thread.** Look up a sender's HubSpot contact, deals, and tickets without leaving Mail.
 - **Talk to the agent directly** from a full-page Agent tab, with the same screen awareness as chat — see [Talking to the Agent](/docs/template-mail-agent).
-- **Extend Mail** with a custom sidebar widget, or fork the whole template — see the [Developer Guide](/docs/template-mail-developers).
+- **Extend Mail** with a custom sidebar widget, or create your own app from the template — see the [Developer Guide](/docs/template-mail-developers).
 
 ## Getting started
 
@@ -120,6 +120,6 @@ Without a Google account connected, the app runs against an empty local mailbox
 - [**Drafting, Scheduling & the Draft Queue**](/docs/template-mail-drafts-and-queue) — composing, scheduled sends, and teammate-requested drafts
 - [**Talking to the Agent**](/docs/template-mail-agent) — useful prompts, screen awareness, and when to escalate to a raw provider call
 - [**Developer Guide**](/docs/template-mail-developers) — actions, data model, routes, and how to customize Mail
-- [**Templates**](/docs/cloneable-saas) — the clone-and-own model, and every other domain template to start from
+- [**Templates**](/docs/cloneable-saas) — the Cloneable SaaS model, and every other domain template to start from
 - [**Calendar**](/docs/template-calendar) — a sibling domain template covering scheduling and booking
 - [**Getting Started**](/docs/getting-started) — the framework fundamentals: actions, application state, and live sync

package/corpus/core/docs/content/template-plan-developers.mdx

@@ -1,11 +1,11 @@
 ---
 title: "Extending Plan"
-description: "The Plan template's data model, action surface, custom MDX block system, and route map — for anyone forking or self-hosting Agent-Native Plan."
+description: "The Plan template's data model, action surface, custom MDX block system, and route map — for anyone customizing or self-hosting Agent-Native Plan."
 ---
 
 # Extending Plan
 
-This page is for anyone forking or self-hosting the Plan template, or writing
+This page is for anyone customizing or self-hosting the Plan template, or writing
 a coding agent integration against its actions directly. Most users should
 install the skill with the CLI instead of scaffolding the app — see
 [Visual Plans](/docs/template-plan).
@@ -700,4 +700,4 @@ a separate, advanced path — not the default hosted flow.
 - [**Local-Files Mode and Desktop Sync**](/docs/template-plan-local-and-desktop) — the MDX source-sync actions in practice
 - [**Events and Automations**](/docs/template-plan-automations) — the event bus these actions write to
 - [**Extensions**](/docs/extensions) — the shared mini-app system Plan installs
-- [**Templates**](/docs/cloneable-saas) — the clone-and-own model
+- [**Templates**](/docs/cloneable-saas) — the Cloneable SaaS model

package/corpus/core/docs/content/template-plan.mdx

@@ -11,7 +11,7 @@ description: "Agent-Native Plans turns your coding agent's plan into a structure
 adds the `/visual-plan`, `/visual-recap`, and `/visualize-repo` skills plus
 the hosted Plan connector to your coding agent — see
 [Plan plugin & marketplace](/docs/plan-plugin) for the plugin and marketplace
-routes. Forking the Plan template (covered under [Extending Plan](/docs/template-plan-developers))
+routes. Customizing the Plan template (covered under [Extending Plan](/docs/template-plan-developers))
 is the secondary path, for self-hosting or building on Plan itself.
 
 </Callout>
@@ -279,9 +279,9 @@ registry to update.
 - [**Reviewing and Commenting on Plans**](/docs/template-plan-review-workflow) — comment types, resolving feedback, sharing, and deleting plans
 - [**Local-Files Mode and Desktop Sync**](/docs/template-plan-local-and-desktop) — keep plan content off the hosted database, or mirror it to a folder
 - [**Events and Automations**](/docs/template-plan-automations) — the plan event bus and automation recipes
-- [**Extending Plan**](/docs/template-plan-developers) — data model, actions, and custom MDX blocks for forking or self-hosting Plan
+- [**Extending Plan**](/docs/template-plan-developers) — data model, actions, and custom MDX blocks for customizing or self-hosting Plan
 - [**PR Visual Recap**](/docs/pr-visual-recap) — run `/visual-recap` automatically on every pull request
 - [**Plan plugin & marketplace**](/docs/plan-plugin) — install the Plan skills as a Claude Code or Codex plugin
 - [**Skills**](/docs/skills-guide) — how Agent-Native installs skills
 - [**MCP Clients**](/docs/mcp-clients) — configuring hosted MCP connectors
-- [**Templates**](/docs/cloneable-saas) — the clone-and-own model
+- [**Templates**](/docs/cloneable-saas) — the Cloneable SaaS model