@agent-native/core 0.102.2 → 0.103.0

package/docs/content/template-content.mdx

@@ -91,9 +91,8 @@ When you open the app, you'll see a page tree next to the editor. The agent alwa
 - **Organize pages in a tree** — nest infinitely, drag to reorder, favorite pages you use often.
 - **Search across everything** with full-text search across titles and content.
 - **Edit local Markdown/MDX files like Obsidian.** Use the `/local-files` view
-  to export your workspace to files, edit them in your own tools, preview
-  changes, and import them back. In Local File Mode, Content writes straight to
-  the selected `.md` or `.mdx` file.
+  to connect a folder to a space's Files database, edit with your own tools,
+  sync changes, and review conflicts without leaving the database-backed app.
 - **Generate rich interactive custom blocks.** Register local React components,
   insert them as MDX, and let the agent create or update component files for
   your docs.
@@ -136,31 +135,23 @@ as the review surface. The hosted app remains the source of truth for sharing,
 comments, permissions, and live collaboration; the local folder is an explicit
 sync surface.
 
-Content can also run in **Local File Mode**, where files are the source of
-truth instead of SQL documents. Add `agent-native.json` to a repo, set
-`mode: "local-files"`, and configure roots such as `docs/`, `blog/`,
-`content/`, and `resources/`. The standard Content editor then populates its
-left sidebar from those local `.md`/`.mdx` files and writes edits back to the
-selected file through the normal document actions. Use this for repo-first docs,
-blogs, resource libraries, or an Obsidian-style personal MDX-powered notes vault; switch back to
-database mode when you want hosted collaboration and SQL-backed sharing. See [Local File Mode](/docs/local-file-mode) for the
-standalone repo layout, configuration, custom MDX components, local
-`extensions/` widgets, and production safety guide.
+Local folders now use the same database model as every other page. Each page
+belongs to a space and its system Files database; a folder is a source adapter
+on that database. You can attach a folder to an existing space or create a
+private folder-backed space, then use database properties and saved sidebar
+views on the imported pages. See [Local folder sources](/docs/local-file-mode)
+for configuration, truth policies, conflicts, custom MDX components, and local
+`extensions/` widgets.
 
-To install the Content local-files skill into an existing repo:
+To open Content for an existing repo:
 
 ```bash
-npx @agent-native/core@latest skills add content --mode local-files --scope project
+npx @agent-native/core@latest content .
 ```
 
-The installer copies the `content` skill for your coding agent and writes or
-updates `agent-native.json` with Content roots for `docs/`, `blog/`, `content/`,
-and `resources/`. When a local Content app, Agent Native Desktop, or trusted
-local bridge is running, agents should use Content actions such as
-`list-documents`, `get-document`, `edit-document`, `update-document`, and
-`share-local-file-document` instead of raw filesystem writes. Without that local
-bridge, the installed skill still gives the agent the repo-editing contract for
-safe Markdown/MDX edits.
+The CLI starts normal database-backed Content, registers an opaque local-folder
+connection in `agent-native.json`, and opens the connection screen. It does not
+set a local-mode environment variable.
 
 ## For developers
 
@@ -189,28 +180,21 @@ Open `http://localhost:8083` and create your first page. Then ask the agent to "
 
 **Search and comments.** Full-text search, anchored comments, version history, and restore flows are built into the document surface.
 
-**Sync surfaces.** Documents can sync with Notion or local Markdown/MDX folders, with SQL acting as the collaborative cache/history layer.
+**Sync surfaces.** Documents can sync with Notion or local Markdown/MDX folders, while SQL remains the canonical collaborative data model.
 
 ### Local file sync
 
 The protected `/local-files` route uses the browser File System Access API, or a
-guarded native folder bridge inside Agent Native Desktop, to read and write
-Markdown/MDX files from a user-chosen folder. After the folder is linked and
-imported, the selected file is treated as the authority: opening the page reads
-the file, and normal editor saves write the file first. SQL is then updated as a
-cache/history layer for the existing document UI, search, and version panel, not
-as the source of truth. The top-right page menu exposes the local source path:
-relative path is always available, absolute path is available in true local-file
-mode and Agent Native Desktop, and Reveal in Finder is available through the
-desktop bridge or server-backed local-file mode.
-
-The bulk sync route calls:
-
-- `export-content-source` — reads the accessible document tree and returns a
-  deterministic `content/` file bundle.
-- `import-content-source` — validates files, creates new private documents,
-  updates documents where the caller has editor access, preserves version
-  history, and rejects invalid parent cycles.
+guarded native folder bridge inside Agent Native Desktop, to connect a folder to
+a Files database. SQL stores only an opaque connection ID, relative paths,
+hashes, and source metadata. Sync materializes ordinary database pages and
+records concurrent edits as reviewable change sets instead of silently
+overwriting either side. Disconnecting preserves both database pages and files.
+
+The folder workflow calls `connect-local-folder-source`,
+`sync-local-folder-source`, `resolve-local-folder-conflict`, and
+`disconnect-local-folder-source`. `export-content-source` can export one source
+using its original relative paths.
 
 The source format lives in `shared/content-source.ts`. Keep that file as the
 single contract for filenames, frontmatter, parsing, and serialization.
@@ -674,6 +658,6 @@ The agent can make all of these changes itself — ask it to "add a tags column
 
 - [**Templates**](/docs/cloneable-saas) — the clone-and-own model, and every other domain template to start from
 - [**Getting Started**](/docs/getting-started) — the framework fundamentals: actions, application state, and live sync
-- [**Local File Mode**](/docs/local-file-mode) — the standalone repo layout, config, and production safety guide
+- [**Local folder sources**](/docs/local-file-mode) — spaces, Files databases, folder adapters, migration, and safety
 - [**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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.102.2",
+  "version": "0.103.0",
   "description": "Framework for agent-native application development — where AI agents and UI share SQL state, actions, and context",
   "homepage": "https://github.com/BuilderIO/agent-native#readme",
   "bugs": {

package/corpus/templates/assets/app/components/library/EditLibraryDialog.tsx

@@ -1,126 +0,0 @@
-import { useActionMutation, useT } from "@agent-native/core/client";
-import { useEffect, useState } from "react";
-import { toast } from "sonner";
-
-import { Button } from "@/components/ui/button";
-import {
-  Dialog,
-  DialogContent,
-  DialogFooter,
-  DialogHeader,
-  DialogTitle,
-} from "@/components/ui/dialog";
-import { Input } from "@/components/ui/input";
-import { Label } from "@/components/ui/label";
-import { Textarea } from "@/components/ui/textarea";
-
-type EditableLibrary = {
-  id: string;
-  title: string;
-  description?: string | null;
-};
-
-export function EditLibraryDialog({
-  library,
-  open,
-  onOpenChange,
-}: {
-  library: EditableLibrary | null;
-  open: boolean;
-  onOpenChange: (open: boolean) => void;
-}) {
-  const t = useT();
-  const updateLibrary = useActionMutation("update-library");
-  const [title, setTitle] = useState("");
-  const [description, setDescription] = useState("");
-
-  useEffect(() => {
-    if (open && library) {
-      setTitle(library.title ?? "");
-      setDescription(library.description ?? "");
-    }
-  }, [open, library]);
-
-  const id = library?.id;
-  const trimmedTitle = title.trim();
-  const dirty =
-    !!library &&
-    (trimmedTitle !== (library.title ?? "").trim() ||
-      description.trim() !== (library.description ?? "").trim());
-
-  function submit() {
-    if (!id || !trimmedTitle) return;
-    updateLibrary.mutate(
-      {
-        id,
-        title: trimmedTitle,
-        description: description.trim() || null,
-      },
-      {
-        onSuccess: () => {
-          toast.success(t("brandKits.updated"));
-          onOpenChange(false);
-        },
-        onError: (err: unknown) => {
-          toast.error(
-            err instanceof Error ? err.message : t("brandKits.updateFailed"),
-          );
-        },
-      },
-    );
-  }
-
-  return (
-    <Dialog open={open} onOpenChange={onOpenChange}>
-      <DialogContent>
-        <DialogHeader>
-          <DialogTitle>{t("brandKits.editDialogTitle")}</DialogTitle>
-        </DialogHeader>
-        <div className="space-y-4">
-          <div className="space-y-2">
-            <Label htmlFor="edit-library-title">
-              {t("brandKitDetail.name")}
-            </Label>
-            <Input
-              id="edit-library-title"
-              value={title}
-              onChange={(event) => setTitle(event.target.value)}
-              placeholder={t("brandKits.namePlaceholder")}
-              autoFocus
-              onKeyDown={(event) => {
-                if (event.key === "Enter" && !event.shiftKey) {
-                  event.preventDefault();
-                  submit();
-                }
-              }}
-            />
-          </div>
-          <div className="space-y-2">
-            <Label htmlFor="edit-library-description">
-              {t("assetDetail.description")}
-            </Label>
-            <Textarea
-              id="edit-library-description"
-              value={description}
-              onChange={(event) => setDescription(event.target.value)}
-              placeholder={t("brandKits.editDescriptionPlaceholder")}
-            />
-          </div>
-        </div>
-        <DialogFooter>
-          <Button variant="outline" onClick={() => onOpenChange(false)}>
-            {t("brandKitDetail.cancel")}
-          </Button>
-          <Button
-            onClick={submit}
-            disabled={!trimmedTitle || !dirty || updateLibrary.isPending}
-          >
-            {updateLibrary.isPending
-              ? t("settings.saving")
-              : t("brandKitDetail.save")}
-          </Button>
-        </DialogFooter>
-      </DialogContent>
-    </Dialog>
-  );
-}