@agent-native/core 0.24.1 → 0.24.3

package/docs/content/template-brain.md

@@ -19,17 +19,40 @@ The product surface stays simple on purpose: **Ask** is the primary chat
 experience, while **Sources**, **Review**, and **Knowledge** are admin/support
 surfaces for connecting data, approving proposals, and inspecting cited memory.
 
+![Brain company chat with cited memory sources](https://cdn.builder.io/api/v1/image/assets%2FYJIGb4i01jvw0SRdL5Bt%2F9c9fe3b5b9494e33803cd3f494cba356?format=webp&width=1200)
+
 Use Brain when your team wants agents to answer questions like "why did we make
 this product decision?", "how does this in-development feature work?", or "what
 changed in this process?" with links back to the source conversation, meeting,
 or issue.
 
-Brain is intentionally on an open-source, Glean-shaped path, but it is not a
-complete Glean replacement today. V1 is company chat plus cited memory over
-reviewed knowledge. V1.5 adds Brain-wide search across knowledge,
-captures, and sources, plus reusable workspace connections for source
-credentials. V2 points toward federated app/source search, permission-aware
-result filtering, ranking, and an expertise graph as a future platform layer.
+Brain's shipped shape is company chat plus cited, reviewed memory over approved
+sources. The current template also includes Brain-wide search across knowledge,
+captures, and source records, plus reusable workspace connections for source
+credentials. Broader federated workspace search and expertise ranking are
+platform direction, not something you need to set up on day one.
+
+## Start Here
+
+1. **Try the demo.** Open Ask and choose **Start demo**. Brain seeds a small
+   product-decision corpus, runs the trust checks, and asks a cited question so
+   you can see answers, citations, review, and not-found behavior before adding
+   real company data.
+2. **Add one source.** Start with a single Slack channel, Granola Team-space
+   feed, GitHub repository, Clips export, or generic transcript webhook. Keep
+   the scope small until citations and review quality look right.
+3. **Review before publishing.** Use Review to inspect evidence, edit wording,
+   and approve only durable company memory.
+4. **Ask from the source.** Use Ask for questions that should be grounded in
+   approved knowledge, not raw chat logs.
+
+## Useful Prompts
+
+- "What did we decide about annual pricing, and where was that discussed?"
+- "Find the most recent onboarding-process change and cite the source."
+- "Summarize what this GitHub discussion means for the launch plan."
+- "Review the pending memory proposals and flag anything too vague to publish."
+- "Which sources are stale or failing sync?"
 
 ## What It Includes
 
@@ -402,7 +425,7 @@ workspaces and reveals Review, Knowledge, and **Run eval** follow-ups once the
 demo is ready.
 
 `run-retrieval-eval` checks an offline real-channel-style retrieval set. It
-uses existing workspace Brain data when #dev-fusion stale Fusion branch answers
+uses existing workspace Brain data when the expected branch-safety answers
 already have citation-backed support; otherwise, with `seedIfMissing` enabled,
 it seeds a small Slack-style fallback corpus and re-runs the same checks. The
 result covers Slack-style citations, branch-safety terms, and an unsupported
@@ -442,6 +465,6 @@ The template follows the agent-native four-area contract:
 - **Application state:** route, filters, and selected IDs mirror into `application_state` for agent context.
 
 See [Dispatch](/docs/dispatch) for the workspace control plane, the
-[Dispatch template](/templates/dispatch) for the scaffolded app,
+[Dispatch template](/docs/template-dispatch) for the scaffolded app,
 [Workspace](/docs/workspace) for shared resources, and
 [A2A Protocol](/docs/a2a-protocol) for cross-app delegation.

package/docs/content/template-clips.md

@@ -30,6 +30,25 @@ Think along the lines of Loom + Granola + Wisprflow rolled into one app — but
 - **Smart library views.** Group by project, filter by speaker, auto-tag based on content.
 - **Edit the transcript through chat.** "Fix the mis-transcribed word at 1:42." "Pull three quotes for a blog post." The agent edits the transcript and the UI updates live.
 
+## Start Here
+
+1. **Open Library.** Browse screen recordings, meeting recordings, dictations,
+   folders, and spaces from one place.
+2. **Record or import.** Capture a screen recording, start from a calendar
+   meeting, or use push-to-talk dictation.
+3. **Let the agent clean it up.** Generate a title, summary, chapters, action
+   items, or cleaned-up transcript text.
+4. **Search and reuse.** Ask for the clip, quote, action item, or decision you
+   need, then share the result with the right visibility.
+
+## Useful Prompts
+
+- "Summarize this clip for a product update."
+- "Find the meeting where we discussed the rollout plan."
+- "Pull three customer quotes from this transcript."
+- "Create action items from the last sales call."
+- "Clean up this dictation and turn it into a Linear ticket."
+
 ## Why it's interesting
 
 Three things make Clips a good showcase of what agent-native enables:

package/docs/content/template-design.md

@@ -9,6 +9,27 @@ Design is an agent-native HTML prototyping studio. Instead of a layered drawing
 
 Use it when you want a polished landing page concept, product UI direction, brand exploration, or interactive prototype that can leave the tool as real HTML.
 
+![Design studio showing generated HTML prototypes and tweak controls](https://cdn.builder.io/api/v1/image/assets%2F348da13fcd8b414c87de9066196f7266%2F961bedb713a94463b834c1f2f4643bcf?format=webp&width=1200)
+
+## Start Here
+
+1. **Describe the artifact.** Ask for the screen, flow, landing page, or visual
+   direction you want. Include audience, tone, and any product constraints.
+2. **Compare directions.** Generate a few variants, pick the strongest one, and
+   keep refining instead of starting over.
+3. **Tune the details.** Use tweak controls for common visual changes, or ask
+   the agent for layout, copy, responsive, and interaction changes.
+4. **Export when it is useful.** Download HTML, ZIP, or PDF once the prototype
+   is ready to hand to another tool or teammate.
+
+## Useful Prompts
+
+- "Create three landing-page directions for a technical analytics product."
+- "Make this dashboard denser and easier to scan for an operations team."
+- "Apply our saved design system and simplify the mobile layout."
+- "Export this prototype as a ZIP once the final variant is selected."
+- "Turn this HTML into a stronger pricing page without changing the brand colors."
+
 ## What You Can Do With It
 
 - **Generate complete prototypes.** Describe the screen or page you need and the agent creates a working HTML document with Tailwind styling and Alpine interactions.

package/docs/content/template-forms.md

@@ -28,6 +28,25 @@ When you open the app, you see your forms, the current editor, and a live previe
 - **Route submissions.** Send submission payloads to webhooks, Slack, Discord, or Google Sheets using the built-in integrations.
 - **Publish public forms.** Share a public form URL and show a thank-you message after submission.
 
+## Start Here
+
+1. **Create a form from a prompt.** Ask for the form you want, including the
+   audience and what should happen after submission.
+2. **Refine in the editor.** Adjust labels, validation, choices, and order in
+   the visual builder when direct editing is faster.
+3. **Publish and share.** Use the public form URL for respondents, then watch
+   results arrive in the Responses view.
+4. **Connect destinations.** Route new submissions to Slack, Discord, Google
+   Sheets, webhooks, or your own extension point.
+
+## Useful Prompts
+
+- "Create a beta signup form with role, team size, and priority use case."
+- "Add a required NPS question and a free-text follow-up."
+- "Post every new response to the product Slack channel."
+- "Summarize this week's submissions and group them by customer segment."
+- "Make this form shorter without losing the fields we need for routing."
+
 ## Why it's interesting
 
 The useful part of an agent-native form builder is that setup and iteration happen in the same place. You can ask the agent to add fields, adjust copy, connect Slack notifications, or inspect the submission data, while the UI remains the direct editor for the same SQL records.

package/package.json

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

package/src/templates/workspace-root/AGENTS.md

@@ -60,15 +60,16 @@ coding agents can discover the same workspace-wide guidance from the root.
 - Do not satisfy a new-app request by adding a route, page, component, or file
   to `apps/starter` or another existing app unless the user explicitly asks to
   modify that existing app.
-- Treat first-party apps such as Mail, Calendar, Analytics, Brain, and Dispatch as
+- Treat first-party apps such as Mail, Calendar, Analytics, Brain, Assets, and Dispatch as
   existing hosted/connected neighbors available through links and A2A/default
-  connected agents. For example, Mail, Calendar, Analytics, and Brain already exist at
+  connected agents. For example, Mail, Calendar, Analytics, Brain, and Assets already exist at
   `https://mail.agent-native.com`, `https://calendar.agent-native.com`, and
-  `https://analytics.agent-native.com`, and `https://brain.agent-native.com`.
-- If a new app needs to use Mail, Calendar, Analytics, Brain, or similar first-party
+  `https://analytics.agent-native.com`, `https://brain.agent-native.com`, and
+  `https://assets.agent-native.com`.
+- If a new app needs to use Mail, Calendar, Analytics, Brain, Assets, or similar first-party
   data/agents, build only the genuinely new workflow and delegate/link to those
   existing apps. Do not create wrapper apps, child apps, nested template copies,
-  or cloned Mail/Calendar/Analytics/Brain implementations inside the new app just to
+  or cloned Mail/Calendar/Analytics/Brain/Assets implementations inside the new app just to
   provide access.
 - Only create a first-party app copy when the user explicitly asks for a
   customized fork/copy of that app. Otherwise prefer the hosted/shared app so

package/src/templates/workspace-root/README.md

@@ -119,7 +119,7 @@ separate workspace app registry to edit. React Router apps must preserve
 For requests phrased as creating an "agent", classify the scope first: simple
 recurring Dispatch behavior can stay in Dispatch, while a robust app-like
 teammate should become a real workspace app listed with the rest of the apps.
-First-party apps such as Mail, Calendar, Analytics, Brain, and Dispatch should be
+First-party apps such as Mail, Calendar, Analytics, Brain, Assets, and Dispatch should be
 treated as existing hosted or connected neighbors. If a new app needs access to
 their data or agents, link/delegate to those apps through the workspace/A2A
 path rather than creating wrapper apps, child apps, or cloned template copies