@agent-native/core 0.49.13 → 0.49.15

package/docs/content/local-file-mode.md

@@ -228,6 +228,24 @@ components render inside the editor and appear in the slash menu under
 **Local components**. Slash insertion creates a minimal tag such as
 `<ImpactCounter />`; add props in the MDX source when needed.
 
+Component execution is intentionally a local-dev/Desktop bridge capability, not
+plain hosted browser folder access. If you open `content.agent-native.com`,
+choose **Local files**, and pick a folder in Chrome, the app can read and write
+the `.md` and `.mdx` files through the browser File System Access API, but
+Chrome does not expose an absolute folder path for Vite to compile
+`components/*.tsx`. To preview and hot reload custom React components, run
+Content locally or use Agent Native Desktop so the trusted local bridge can
+register the picked workspace with the local Content dev server. In that mode,
+edits to existing component files hot reload through Vite, and adding or
+removing component files reloads the component registry and slash menu.
+
+Agents can also work with those registered component files. Use
+`list-local-component-files` to find the registered workspace id, then
+`write-local-component-file` to create or update `.tsx`, `.jsx`, `.ts`, or
+`.js` files under the workspace's `components/` folder. The MDX files remain the
+source of truth for component usage; the component files remain normal repo
+source files reviewed with Git.
+
 If a component exports input metadata, selecting the component in the editor
 shows an edit button in the component's top-right corner. Supported input types
 are `string`, `textarea`, `number`, `boolean`, and `select`. The form writes

package/docs/content/template-content.md

@@ -205,6 +205,15 @@ menu under Local components. When input metadata is exported, selecting the
 component in the editor shows a corner edit button that rewrites the MDX props
 in the local file.
 
+The browser **Local files** picker can read and write `.md` and `.mdx` files on
+its own, but executable React component previews require a local compiler. Run
+Content locally or use Agent Native Desktop so the selected workspace path can
+be registered with the local Content dev server. Vite then imports
+`components/*.tsx`, hot reloads edits to existing component files, and reloads
+the component registry when files are added or removed. Agents can use
+`list-local-component-files` and `write-local-component-file` to inspect or
+update registered component files while the editor updates from the same source.
+
 ### Comments
 
 Threaded comments on documents with quoted-text anchors, replies, and resolve state. Backed by the `document_comments` table and `app/components/editor/CommentsSidebar.tsx`. Actions: `list-comments`, `add-comment`. Notion comments can sync both ways via `sync-notion-comments`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.49.13",
+  "version": "0.49.15",
   "type": "module",
   "engines": {
     "node": ">=22"