@agent-native/core 0.198.7-nightly-20260930213124 → 0.198.7

package/dist/agent/production-agent.js

@@ -2612,8 +2612,16 @@ export function normalizeToolErrorForBreaker(error) {
         .replace(/\s+/g, " ")
         .trim());
 }
-function rateLimitRecoveryHint(message) {
-    if (!/\b(?:429|rate[-\s]?limit|rate limited|quota exceeded|too many requests|calls limit exceeded)\b/i.test(message)) {
+function rateLimitRecoveryHint(message, error) {
+    const statusCode = typeof error === "object" && error !== null && "statusCode" in error
+        ? error.statusCode
+        : undefined;
+    const errorCode = typeof error === "object" && error !== null && "errorCode" in error
+        ? error.errorCode
+        : undefined;
+    if (statusCode !== 429 &&
+        !/\b(?:429|rate[-\s]?limit|rate limited|quota exceeded|too many requests|calls limit exceeded)\b/i.test(message) &&
+        !(typeof errorCode === "string" && /rate[-_]?limit|quota/i.test(errorCode))) {
         return "";
     }
     return "\n\nProvider rate-limit guidance: stop retrying this provider in this turn. Report the rate limit as a coverage gap, include any evidence already gathered, and ask the user to retry after the provider quota resets if full coverage is required.";
@@ -4995,7 +5003,7 @@ export async function runAgentLoop(opts) {
                         const errorCode = isActionContractError(err) && err.errorCode !== "action_failed"
                             ? ` (errorCode: ${err.errorCode})`
                             : "";
-                        result = `Error running ${toolCall.name}: ${message}${errorCode}${rateLimitRecoveryHint(message)}`;
+                        result = `Error running ${toolCall.name}: ${message}${errorCode}${rateLimitRecoveryHint(message, err)}`;
                     }
                     isError = true;
                 }

package/dist/automation/index.d.ts

@@ -139,8 +139,8 @@ export declare function createAutomationCallbackHandler(runtime: AutomationRunti
     duplicate?: undefined;
     eventId?: undefined;
 } | {
+    error?: undefined;
     accepted: boolean;
     duplicate: boolean;
     eventId: string;
-    error?: undefined;
 }>;

package/dist/cli/create.js

@@ -15,6 +15,7 @@ const REPO = "BuilderIO/agent-native";
 const TEMPLATES_DIR = "templates";
 const PGLITE_DEPENDENCY_VERSION = "^0.5.8";
 const POSTGRES_DEPENDENCY_VERSION = "^3.4.9";
+const DRIZZLE_DEPENDENCY_VERSION = "^0.45.3";
 const STANDALONE_EXACT_DEPENDENCY_OVERRIDES = {
     "@react-router/dev": "8.1.0",
     "@react-router/fs-routes": "8.1.0",
@@ -807,6 +808,7 @@ async function scaffoldOneAppIntoWorkspace(workspace, appName, templateName, cla
         const workspaceOverrides = prepareWorkspaceOverrides(workspace.workspaceRoot);
         await scaffoldRequiredPackages([templateName], workspace.workspaceRoot);
         applyLocalWorkspaceOverrides(workspace.workspaceRoot, workspaceOverrides);
+        ensureWorkspaceDrizzleDependency(workspace.workspaceRoot);
         s.stop(`Scaffolded apps/${appName}.`);
     }
     catch (err) {
@@ -1411,6 +1413,19 @@ function resolvePublishedWorkspaceSpecifier(packageName, workspaceSpecifier) {
         return "*";
     }
 }
+function ensureWorkspaceDrizzleDependency(workspaceRoot) {
+    const packageJsonPath = path.join(workspaceRoot, "package.json");
+    const pkg = JSON.parse(fs.readFileSync(packageJsonPath, "utf-8"));
+    if (!pkg || typeof pkg !== "object" || Array.isArray(pkg)) {
+        throw new Error(`${packageJsonPath} must contain a JSON object`);
+    }
+    pkg.dependencies ??= {};
+    if (typeof pkg.dependencies !== "object" || Array.isArray(pkg.dependencies)) {
+        throw new Error(`${packageJsonPath} has an invalid dependencies object`);
+    }
+    pkg.dependencies["drizzle-orm"] ??= DRIZZLE_DEPENDENCY_VERSION;
+    fs.writeFileSync(packageJsonPath, JSON.stringify(pkg, null, 2) + "\n");
+}
 async function scaffoldRequiredPackages(templateNames, workspaceRoot) {
     const needed = new Set();
     for (const t of templateNames) {
@@ -1624,6 +1639,7 @@ function postProcessStandalone(name, targetDir, templateName, resolution) {
             }
             pkg.dependencies = pkg.dependencies ?? {};
             pkg.dependencies["@electric-sql/pglite"] ??= PGLITE_DEPENDENCY_VERSION;
+            pkg.dependencies["drizzle-orm"] ??= DRIZZLE_DEPENDENCY_VERSION;
             pkg.dependencies.postgres ??= POSTGRES_DEPENDENCY_VERSION;
             ensureReactRouterBuildDependencies(pkg);
             hasNodePty = [

package/dist/cli/skills-content/design-visual-edit-skill.d.ts

@@ -1 +1 @@
-export declare const DESIGN_VISUAL_EDIT_SKILL_MD = "---\nname: visual-edit\ndescription: >-\n  Open and collaboratively edit a running local app in Design, with shared\n  fallback previews and source handoff. Use when the user asks to inspect,\n  share, or edit a real local app in Design.\nmetadata:\n  visibility: exported\n---\n\n# Visual Edit\n\nUse `/visual-edit` when the user wants to inspect or edit a real local app\nvisually instead of generating standalone Alpine HTML. The source of truth is\nthe running localhost app plus its route URLs. Design shows those routes as\niframe-backed screens on the infinite canvas.\n\nThe editor is hosted at `https://design.agent-native.com`. Never start local\nDesign; only the target app and bridge run locally.\n\nSee the [Visual Edit guide](https://github.com/BuilderIO/agent-native/blob/main/skills/visual-edit/README.md)\nfor a worked onboarding-flow example.\n\n## Fast local startup\n\n- Do not install this skill into the target app or start a local Design server.\n  The skill belongs to the coding host; Design is always the hosted app above.\n- If you need to start an Agent-Native framework app yourself, use\n  `AUTH_DISABLED=1` with its normal dev command. This is local-only and gives\n  the visual editor the framework's dev identity without a user login.\n- If an agent-owned local server redirects a requested screen to `/sign-in`,\n  restart that server with `AUTH_DISABLED=1` and probe the route again before\n  opening Design. Never present a sign-in page as the requested screen.\n- Before calling `open-visual-edit`, verify the target URL responds. Start an\n  agent-owned dev server with its normal command when it is down, and wait for\n  the requested routes to respond before opening Design. Never leave a dead\n  localhost URL in the canvas.\n- Preserve a server you did not start; use its existing authenticated browser\n  session or explain that the target app, rather than Design, requires login.\n- When the user gives explicit paths, skip route inventory and place those\n  paths directly. Discover routes only when paths were not supplied.\n\n## Installation\n\n`npx @agent-native/core@latest skills add visual-edit` installs the skill and\nhosted Design MCP connector. `npx skills@latest add BuilderIO/agent-native\n--skill visual-edit` installs instructions only; page-capable WebMCP hosts need\nno connector installation.\n\n## Put Design Beside The Chat\n\nPrefer the interactive MCP App from `open-visual-edit`: it keeps Design beside\nchat and routes **Apply design updates** through the host's MCP Apps bridge. The\nhost may ask the user to confirm the current conversation. Otherwise,\n`openUrl` is a credential-free, read-only fallback; never claim it is editable.\n\n- Inline-browser hosts should open `https://design.agent-native.com/visual-edit`\n  and call its `open-visual-edit` WebMCP tool. It works signed in or out; the\n  one-time capability is not a Design account session. A page-capable browser\n  controller is enough, so Claude-in-Chrome, Claude Code browser tools, the\n  ChatGPT Chrome/browser extension, Puppeteer or Playwright MCP, CDP, and\n  similar JavaScript-capable controllers do not need the hosted MCP connector.\n- VS Code uses its Design webview/deep link. Without page WebMCP, use the hosted\n  Design MCP connector and its normal OAuth/device authorization. Never replace\n  either path with a local Design server.\n\nInside Design, use **Show/Hide UI** from the `Cmd K` menu or press Figma's\n`Shift \\` shortcut to toggle all editing chrome so only the canvas remains.\n\n## Browser WebMCP (Default Without Connector)\n\nWithout a connected Design MCP, use a visible browser tab with a main-world\nJavaScript evaluator. Prefer the host's inline browser; use external Chrome\nonly when requested or unavailable. Open\n`https://design.agent-native.com/visual-edit`, keep it visible while tools\nregister, and read the title before work. Never enter, copy, or request\npasswords, cookies, tokens, or codes. Signed-out loopback visual-edit works;\nother pages that block tools behind sign-in still require a signed-in tab.\nIf the browser exposes CDP permissions, grant `local-network-access` to\n`https://design.agent-native.com` before calling page tools; otherwise use the\npage's Connect button and let the browser's permission prompt complete.\n\nUse a native browser-session WebMCP bridge when the host provides one: list\nonce with `list-browser-session-webmcp-tools` and run with\n`run-browser-session-webmcp-tool`, or use the `list-host-webmcp-tools` and\n`run-host-webmcp-tool` pair. Preserve the exact discovered name, origin, and\nargs. Otherwise use the page-world API. Agent-Native pages expose this helper:\n\nExample assumes signed-in or existing bridge; fresh signed-out loopback must add\nthe locally held `bridgeToken` described below.\n\n```js\nconst an = window.__agentNativeWebMcp;\nconst status = await an.ready({ waitMs: 20_000 });\nif (status.state !== \"ready\") throw new Error(status.error ?? status.state);\nconst tools = await an.tools(\"visual-edit\");\nif (!tools.some((tool) => tool.name === \"open-visual-edit\")) {\n  throw new Error(\"open-visual-edit is not registered yet\");\n}\nconst result = await an.call(\"open-visual-edit\", {\n  devServerUrl: \"http://localhost:5173\",\n  paths: [\"/\"],\n  navigate: true,\n}, { waitMs: 2_000 });\nif (result.state === \"pending\") {\n  // On the next evaluation, read the still-running call without replaying it.\n  an.result(result.id);\n}\n```\n\nIf the helper is absent, use standard WebMCP directly. `document.modelContext`\nis canonical; `navigator.modelContext` is deprecated:\n\n```js\nconst ctx = document.modelContext;\nconst tool = (await ctx.getTools()).find((candidate) => candidate.name === NAME);\nif (!tool) throw new Error(`WebMCP tool not found: ${NAME}`);\nconst codex = typeof ctx.codexExecuteTool === \"function\" ||\n  typeof ctx.codexGetTools === \"function\";\nconst result = await ctx.executeTool(tool, codex ? ARGS : JSON.stringify(ARGS));\n```\n\nThe helper handles live discovery, partial registries, and pending calls. If a\ncall returns `state: \"pending\"`, read `an.result(id)` on the next evaluation;\nnever replay a write. For Claude Code or Cowork, `javascript_tool` runs this\npage-world code with top-level `await`; for Codex open the page with\n`cua.createBrowserTab(\"iab\", url, { visible: true })`, then use CDP\n`Runtime.evaluate` with `awaitPromise: true`; Puppeteer and Playwright MCP can\nuse their page evaluator. Playwright isolated worlds cannot see\n`document.modelContext`. Keep evaluator output small, batch dependent calls,\nand do not navigate inside a batch.\n\nTool descriptors are page-local. Do not copy them into the host, hand-build\nauthenticated HTTP requests, or replace named tools with clicks, typing, DOM\nautomation, or screenshots. UI automation remains appropriate for canvas work\nwithout a named tool or when requested. If both bridges are unavailable after\none discovery and one independent evaluator check, use hosted MCP/CLI before\nchanging state.\n\nFor a fresh signed-out loopback connection, generate the bridge token locally,\nstart the durable bridge with it, and pass that same token once as the page\ntool's `bridgeToken`; the page never returns it. Reuse a matching running\nbridge without the token. Account-backed or private Design work requires a\nsigned-in session or the authenticated Design MCP connector. After canvas edits,\ncall `an.call(\"get-visual-edit-prompt\", {}, { waitMs: 2_000 })` and apply the\nreturned handoff. The page tool may show an approval dialog; let the user\napprove it and never bypass that consent.\n\n## Core Model\n\n- Each screen is a URL-backed iframe, not copied HTML.\n- Each screen keeps URL metadata: `connectionId`, `routeId`, `path`,\n  `url`, `bridgeUrl`, title, and viewport size.\n- The owner edits through the local bridge. Shared\n  `/visual-edit/:designId?share=1` links render a sanitized inert snapshot,\n  refreshed on route or DOM changes; guests never reach the owner's localhost.\n  Guest edits stay pending until an owner or editor applies them to source.\n- Authorized viewers and commenters on private designs can edit the shared\n  Visual Edit canvas and submit pending changes without writing design files.\n  The owner or editor applies those source changes.\n- **The `/visual-edit` skill needs no Design account sign-in.**\n  `open-visual-edit` mints a five-minute, single-use capability for the exact\n  `/visual-edit/:designId` local-editor route. The MCP host redeems it outside\n  model-visible text, then opens the existing editor with localhost edit access.\n  A public `/visual-edit/:designId` route enables browser-only DOM editing of\n  public localhost snapshots; handoffs stay pending until applied. The owner\n  sees **Apply edits** when a recipient has pending changes.\n  This capability is not an account session: `/_agent-native/session` remains\n  signed out, and account-backed save/share/generate actions remain denied.\n- Hosted MCP highlights `get-visual-edit-pending`; pass the visual-edit\n  design ID for a tab-free handoff. It returns a revision; after applying,\n  call `acknowledge-visual-edit-pending` with that revision, then pull again.\n  `empty` means no edits; `session-ended` means edits were lost;\n  `unknown` means the marker was unreadable, not proof of no change.\n- Browser hosts can use page-local `get-visual-edit-prompt`.\n- The `open-visual-edit` action is owned by Design. From another app, use the\n  hosted MCP server at `https://design.agent-native.com/mcp` or the page's\n  WebMCP helper, not `pnpm action` in the target app. The page path works\n  signed out only for loopback apps in public mode, using a short-lived\n  capability-scoped principal; hosted MCP uses its normal OAuth identity.\n- Ordinary public links stay read-only. Public `/visual-edit/:designId` and\n  authorized private shares allow DOM-only edits, never source writes. Guest\n  Interact is blocked; snapshots strip active content and owner-local resources,\n  and persisted writes stay role-gated. Loopback is not a trust boundary because\n  tunnels can proxy remote callers.\n- The live editor is same-origin through the local bridge proxy. This boots\n  CSR apps and root-relative assets, but it is still a localhost editing proxy:\n  app-origin cookies, WebSockets/HMR, SSE, and non-GET app API calls may need a\n  future dev-server/plugin integration for perfect parity with the app's own\n  origin.\n- The canvas is the editing view; Interact runs the normal URL with rails and a\n  device bar. Interact preserves navigation, scrolling, links, and controls;\n  the canvas pans/zooms and suppresses native frame interaction.\n- While a localhost screen has pending live visual edits, do not switch back to\n  Interact until the user either applies the edits to source or explicitly\n  aborts/discards the preview.\n- Alt-drag duplicates a localhost frame and its URL metadata. Change the copy's\n  path/query for another state; preserve the order of named or numbered flows.\n  Shorthand like `localhost:1234/onboarding/1` means\n  `http://localhost:1234/onboarding/1`.\n\n## Useful Canvas Sets\n\nUse a focused batch of 3-7 frames by default: one ordered frame per requested\nroute/query state, repeat routes at requested desktop/tablet/mobile viewports,\nand include URL-addressable empty, loading, error, modal-open, or selected-item\nstates. Keep the Screens section readable so Layers remains useful while\nediting. Do not expand beyond 7 frames unless the user explicitly asks for an\nexhaustive audit or a complete route inventory.\n\nDo not expand every discovered route or every viewport unless the user asks for\nan exhaustive audit. Preserve the user's labels and sequence so the canvas\nreads like the workflow they described.\n\n## Select And Reprompt\n\nWhen a chat message begins with `[Reprompt selection]`, the selected subtree is\na hard write boundary. The only mutation path is `propose-node-rewrite` with\nthe exact `repromptId`, target, and `baseVersionHash` captured in\n`design-reprompt-pending:<designId>:<fileId>`. Never use `apply-visual-edit`,\n`apply-source-edit`, `write-source`, `write-local-file`, `edit-design`, or any\nother content-writing action for that request. Clarifying questions are allowed,\nbut a requested change must remain a proposal.\n\nProduce one variant by default. Produce two or three only when the instruction\nasks for options. A retry includes `priorProposalId`; keep the same target and\nbase version, incorporate the feedback, and call `propose-node-rewrite` again.\nThe UI previews the returned subtree without persisting it.\n\nUse `resolve-node-rewrite` for the accept/reject lifecycle. Accept applies the\nchosen variant as one version-checked inline/Yjs content transaction so one\nundo restores the prior structure; reject clears the proposal without changing\ncontent. For conversational resolution such as \"apply the second one,\" call\n`view-screen`, read the active `design.reprompt.proposal`, and pass its\n`proposalId` plus the zero-based `variantIndex` to `resolve-node-rewrite`.\n\n## Review Quality\n\nTreat the running app as truth, preserving its component language, tokens, route\nstate, and content. Compare visual edits before/after at requested viewports and\ncheck meaningful URL, hover, focus, scroll, and modal states.\n\n## Account And Sharing Model\n\n- The capability permits live iframe inspection, session-local edits, undo/redo,\n  **Apply design updates**, and **Copy prompt**. These hand bounded source\n  instructions to the coding agent; they do not persist account-owned Design data.\n- Public `/design/:id` links stay read-only without a signed-in owner/editor\n  session. Never use the local capability to upgrade that ordinary sharing\n  surface.\n- Prefer links returned by Design actions or `/_agent-native/open` deep links;\n  never surface `_session=` tokens or hand-build capability URLs.\n- Do not attempt account-backed write actions with the browser capability. The\n  trusted local `open-visual-edit` CLI call may register its bridge, create or\n  reuse its workspace-owned local design, and place screens without an account.\n  Direct source-file action writes, generation, saving into an account, and\n  sharing still require an authenticated action caller. If a signed-out visitor\n  wants those durable account operations, send them through the framework\n  sign-in return flow first.\n\n## Required Local Bridge\n\nThe live-edit bridge is unlocked by a shared secret (the \"bridge token\") that\nmust match on two sides: the local bridge process, and the user's connection row\nin Design (which the browser reads to authorize `/live-edit-bridge`,\n`/read-file`, `/write-file`). Get them to match by letting the\n`open-visual-edit` action mint the token, then starting the\nbridge with it. This is the only ordering that works for the remote-MCP flow -\nthe bridge cannot push its own token to the server without a CLI auth token, so\nthe server mints instead and the bridge adopts.\nThe `connectionId` (usually `localhost_...`) only identifies the row; never\npass it as `bridgeToken`.\n\nFor a fresh signed-out browser flow, generate the token locally, keep it in the\nhost process, and pass it once as the page tool's optional `bridgeToken`; the\npage never returns it:\n\n```bash\nBRIDGE_TOKEN=\"$(node -e 'process.stdout.write(require(\"node:crypto\").randomBytes(32).toString(\"hex\"))')\"\nAGENT_NATIVE_BRIDGE_TOKEN=\"$BRIDGE_TOKEN\" npx @agent-native/core@latest design connect --url http://localhost:5173 --root . --daemon\n```\n\nReuse an existing matching connection without `bridgeToken`; hosted MCP can\nmint the token when page WebMCP is unavailable.\n\nFrom the target app repo, make sure its dev server is running, then:\n\n**1. Discover routes without starting a durable bridge** (one-shot, exits):\n\n```bash\nnpx @agent-native/core@latest design connect --url http://localhost:5173 --root . --json\n```\n\nThis prints the manifest (routes + capabilities). Parse it to build\n`routeManifest` for the next step. (Skip this if the user already gave explicit\npaths/URLs to place.)\n\nInside the agent-native monorepo itself, use the workspace CLI instead of\n`npx` \u2014 `npx` installs the last published `@agent-native/core`, which will not\ncontain local changes and costs a slow install on every call:\n\n```bash\npnpm dev:cli design connect --url http://localhost:5173 --root templates/<app> --json\n```\n\n**2. For the hosted MCP path, call `open-visual-edit`** (see Action Flow below)\nwith NO `bridgeToken`.\nThe server mints one, stores it on the user's connection row, copies it into the\nplaced screens' metadata, and returns it to you as `bridgeToken`. Capture it.\n\n**3. Start the persistent bridge adopting that token** (single line; prefer the\nenv var so the secret does not appear in `ps`):\n\n```bash\nAGENT_NATIVE_BRIDGE_TOKEN=\"<bridgeToken from step 2>\" npx @agent-native/core@latest design connect --url http://localhost:5173 --root . --daemon\n```\n\n(Equivalently, pass `--bridge-token <token>`.) This starts a detached bridge on\n`http://127.0.0.1:7331`, adopts the server-minted token \u2014 so bridge and row\nagree and live-edit authorizes with no self-registration \u2014 and stays alive after\nthe command exits.\n\nFor a manual health/manifest check on the running bridge:\n\n```bash\ncurl http://127.0.0.1:7331/health\n```\n\n`/health` needs no token. The full manifest at `/manifest.json` is\npreview-token protected, so an unauthenticated `curl` of it returns\n`{\"ok\":false,\"error\":\"invalid or missing preview token\"}` \u2014 that response means\nthe bridge is up, not that it is broken.\n\nOnly use `--json` for the step-1 route probe. Never use `--json`, `--once`,\nor `--dry-run` for the durable step-3 bridge: they print the manifest and exit,\nso Design falls back to a non-editable live iframe.\n\nThe bridge listens on a single fixed port (7331) and refuses to start for a\nsecond, different app. It is detached with no log file, so if `--daemon` reports\na timeout, check for a stale process (`lsof -ti:7331`) before retrying.\n\nIf local Design uses PGlite, never invoke the in-process CLI against that server:\nboth open the same directory and the second owner is rejected. For a signed-out\nlocal test, start Design with `AUTH_DISABLED=1`, open `/visual-edit`, and call\nthe server-action `open-visual-edit` through `window.__agentNativeWebMcp` after\nit registers. This keeps one PGlite owner; `get-visual-edit-prompt` is only the\npost-edit handoff. With auth enabled, sign in to hosted Design MCP or use shared\nPostgres before using the CLI action.\n\n## Action Flow\n\nWhen a browser is available, reuse the local bridge and call the Design page's\n`open-visual-edit` WebMCP tool. For a fresh signed-out connection, pass the\nlocally held `bridgeToken`; it reads its preview manifest and challenge proof,\nthen sends both for validation. Hosted Design never fetches `127.0.0.1`. If the\npage has no WebMCP, use the connected Design MCP server or its normal hosted\nMCP fallback.\n\nFrom another app, call the connected Design MCP tool\n`mcp__agent-native-design__open-visual-edit` with the JSON arguments below. It\nregisters or refreshes the localhost bridge,\nmints and stores the bridge token, creates or reuses a Design project, places\nURL-backed screens, stores visual-edit context, and navigates to overview mode\nin one call. Never run `pnpm action` from the target app's checkout: its local\nregistry does not contain Design actions.\n\nCall it before starting the durable bridge: it does not contact the bridge, so\nthe server can mint `bridgeToken` for the bridge to adopt. Omit that input.\n\n```json\n{\n  \"title\": \"Docs homepage visual edit\",\n  \"devServerUrl\": \"http://localhost:5173\",\n  \"bridgeUrl\": \"http://127.0.0.1:7331\",\n  \"rootPath\": \"/absolute/path/to/app\",\n  \"routeManifest\": { \"...\": \"from /manifest.json\" },\n  \"paths\": [\"/\", \"/pricing\", \"/checkout?step=payment\"]\n}\n```\n\nThe action returns `designId`, `connectionId`, `bridgeToken`, `screens`,\n`urlPath`, and credential-free `openUrl`. MCP App metadata carries the\nhidden one-time launcher. Keep the ids for follow-ups\nand pass the token to `design connect`; reusing the connection reuses its token.\n\n### Desktop and mobile side by side\n\nPass `viewports` to place every requested route once per viewport. Frames lay\nout as a grid: one row per route, one column per viewport. Presets are\n`desktop` (1280x900), `laptop` (1440x900), `tablet` (834x1112), and `mobile`\n(390x844); an explicit `{ \"label\": \"...\", \"width\": N, \"height\": N }` also works.\n\n```json\n{\n  \"title\": \"Tasks responsive visual edit\",\n  \"devServerUrl\": \"http://localhost:5173\",\n  \"bridgeUrl\": \"http://127.0.0.1:7331\",\n  \"rootPath\": \"/absolute/path/to/app\",\n  \"paths\": [\"/tasks\", \"/inbox\"],\n  \"viewports\": [\"desktop\", \"mobile\"]\n}\n```\n\nPrefer this over two separate calls with `defaultWidth`/`defaultHeight`: it\nkeeps each route's viewports aligned in a row and titles them\n`Tasks \u2014 Desktop` / `Tasks \u2014 Mobile` so the canvas reads clearly. `viewports`\noverrides `defaultWidth`/`defaultHeight`. With no `routes`/`paths`, it expands\nevery route in the localhost manifest, which is usually far more frames than\nthe user wants \u2014 name the paths.\n\n### Managing screens and breakpoints manually\n\nSelect a screen and use the right-rail **Screen** section to switch between\nStatic HTML and URL-backed modes, edit its route/path, choose a localhost\nconnection, add another URL screen, or remove the selected screen. URL mode\nkeeps the iframe live; switching to Static stores a sanitized snapshot of the\ncurrent frame, including its current client state when the page can provide it.\nThe same operations are available to a page-capable agent through\n`add-localhost-screens`, `update-screen-source`, `add-breakpoint`, and\n`remove-breakpoint`.\n\n### Adding more page frames later\n\nCall `open-visual-edit` again with the same `designId` and `connectionId` and\nonly the new paths. Existing frames for the same route and viewport are\nrefreshed in place rather than duplicated, and a frame the user has dragged or\nresized keeps its position unless you explicitly pass `x`/`y`/`width`/`height`.\n\n```json\n{\n  \"designId\": \"<existing-design-id>\",\n  \"connectionId\": \"<existing-connection-id>\",\n  \"devServerUrl\": \"http://localhost:5173\",\n  \"paths\": [\"/settings\", \"/team\"],\n  \"startY\": 2200\n}\n```\n\nDo NOT add `defaultWidth`/`defaultHeight` just to restate the default size:\nsupplying either one marks the viewport as explicitly requested, which\noverwrites frame sizes the user has already adjusted on the canvas.\n\nFor a numbered flow the user describes in chat, keep the labels and order:\n\n```json\n{\n  \"designId\": \"<existing-design-id>\",\n  \"connectionId\": \"<existing-connection-id>\",\n  \"devServerUrl\": \"http://localhost:1234\",\n  \"routes\": [\n    { \"url\": \"localhost:1234/onboarding/1\", \"title\": \"Screen 1\" },\n    { \"url\": \"localhost:1234/onboarding/2\", \"title\": \"Screen 2\" },\n    { \"url\": \"localhost:1234/onboarding/3\", \"title\": \"Screen 3\" }\n  ]\n}\n```\n\nIf no `routes` or `paths` are supplied, `open-visual-edit` uses every route\nfrom the localhost manifest.\n\nFallback only when `open-visual-edit` is unavailable and hosted Design MCP is\nauthorized:\n\n1. Register or refresh the bridge with `connect-localhost`, passing the\n   `/manifest.json` result as `routeManifest` and `capabilities`.\n2. Create or reuse a Design project with `create-design`.\n3. Place URL-backed screens with `add-localhost-screens`.\n4. Navigate to overview mode with `navigate`.\n\nThe fallback still targets `https://design.agent-native.com`; only the app and\nbridge URLs are localhost. Never run `pnpm action` from `templates/design`.\n\n## Open The Design Surface\n\n- Use the `link`, `deepLink`, or MCP App embed returned by Design actions so the\n  user sees the canvas. Prefer the MCP App; its host launcher carries the\n  one-time capability. The credential-free `openUrl` is read-only fallback.\n- Never return or open a hand-built `/design/:id?_session=...` URL.\n- If the user is working in VS Code, the Agent-Native extension can open the\n  same URL via\n  `vscode://builder.agent-native/open?url=<encoded-design-url>`. Its\n  `Agent-Native: Open Design Canvas` command also starts the local bridge and\n  opens hosted Design in the VS Code side panel.\n- Once `open-visual-edit` returns the expected `screenCount`, hand back the\n  link and stop. Do not open it yourself in a browser-automation tool to\n  screenshot or poll until it renders \u2014 a cold dev server can take 10-30s\n  regardless of who's watching, and that wait adds nothing the response didn't\n  already confirm. Reach for browser automation only if the user later reports\n  the canvas is broken.\n\n## Applying Visual Edits Back To Source\n\nWith Design closed, call hosted Design MCP's highlighted\n`get-visual-edit-pending` for the design ID; it returns the handoff and\nrevision. Verify the applied source, acknowledge that revision, then pull again.\nIf MCP is unavailable, read the local bridge:\n\n```bash\nnpx @agent-native/core@latest design pending --root . --design-id <design-id-from-visual-edit-url>\n```\n\nPass the ID after `visual-edit` in the Design URL; the CLI prints that\ndesign's prompt (`null` when empty).\n\nCanvas edits on a localhost screen never write source directly. They stay\npending until the canvas shows **Apply design updates** (local) or **Apply edits**\n(shared). An MCP App sends its prompt through the host or local Design agent;\notherwise use **Copy prompt to your agent**.\n\nChatGPT and Claude Code should pull, apply, acknowledge, and pull again.\nBrowser WebMCP hosts can call `get-visual-edit-prompt`. Never acknowledge\nbefore applying the source change.\n\n- Style, text, and drag/drop edits collect into one pending batch for a single\n  apply.\n- After the write lands, the target app's own dev-server HMR refreshes the\n  frames \u2014 no manual reload. If frames do not refresh, the write did not land;\n  say so rather than assuming.\n- The separate disk-icon \"Apply to source\" button is the deterministic\n  whole-file HTML/CSS writer. It is intentionally disabled for compiled\n  `.jsx`/`.tsx` routes \u2014 those must go through the agent path above.\n\n## Editing URLs\n\nKeep localhost screens as URL files plus `screenMetadata[fileId]`. Do not\nreplace them with copied `srcdoc` HTML unless the user explicitly asks for a\nfrozen snapshot. To change a state, rerun `open-visual-edit` with the new\npath/query, use the Screen settings section, call `update-screen-source`, or\nduplicate the screen and update the copy's URL metadata.\n\n## Local Files in the Code Tab\n\nOnce a connection is registered, the design editor's Code panel (left rail \u2192\nCode, or `navigate --view editor --designId <id> --leftPanel code`) shows a\nlocal-files workspace root for that connection next to the design's own files.\nTreat that root like VS Code opened at the connected project directory: file\ntree, search, open/edit, and save are backed by the real local files. It lists\nthe connected app's text/code files through the bridge\n(`list-local-files` / `read-local-file`); build output, `node_modules`,\n`.git`, and secret-looking paths (`.env*`, key files) are always excluded.\n\n- Browsing and reading need only editor access on the design plus the running\n  bridge.\n- Saving goes through `write-local-file`: the first save opens the\n  write-consent dialog (an 8-hour, folder-scoped grant) and retries\n  automatically once granted. Only text/code files are writable; secret paths\n  are always blocked.\n- If the agent calls `write-local-file` directly (not through a UI save) and it\n  fails with \"no write-consent grant\", call `request-localhost-write-consent`.\n  It opens the write-consent dialog in the editor, or reports `alreadyGranted`\n  if one already exists. Granting is human-only \u2014\n  `grant-localhost-write-consent` is hidden from agents, so you cannot approve\n  it yourself. Tell the user to click \"Allow writes\", then retry\n  `write-local-file` once. Do not keep retrying blindly: the write stays\n  blocked until the user approves.\n- Saves are conflict-checked against the file's on-disk version \u2014 a file that\n  changed since it was read fails with a version conflict instead of being\n  overwritten.\n\n## React Source Writeback\n\n- Use compiler/debug provenance (project-relative file, line, column,\n  component, and runtime multiplicity) to locate React/TSX source. Treat it as\n  evidence, not as permission for a generic AST structural transform.\n- Read `positionPrecision` on every anchor before you trust `line`/`column`.\n  `authored` means those are the real JSX coordinates. `transformed` means they\n  are the dev server's own output coordinates \u2014 React 19 removed `_debugSource`\n  and exposes only an owner stack, so this is the normal case on a Vite/Next\n  dev server, and the line will not match the file. `unknown` means no tier was\n  reported. On anything but `authored`, use the file and component to find the\n  element by its JSX shape and re-derive the line from the file you read; never\n  edit at the reported line.\n- A single-instance leaf text edit, literal `className`/`class` edit, or flat\n  literal `style={{ ... }}` property may use `apply-visual-edit` with a\n  `local-file` source and a complete `target.sourceAnchor`. Forward the\n  anchor's `positionPrecision` with it \u2014 the action refuses a `transformed`\n  anchor with `status: \"needsAgent\"` instead of seeking to a line that means\n  something else in the authored file. Preview first (omit `persist`), inspect\n  `proposedDiff`, then call with `persist: true`.\n- Reparenting, grouping/ungrouping, wrappers, dynamic expressions, repeated\n  `.map()` instances, shared components, breakpoint-scoped edits, and\n  cross-file changes go through the coding agent with complete subject/target\n  anchors and their runtime relationship. `apply-visual-edit` refuses these\n  with `status: \"needsAgent\"` rather than guessing.\n- Before each write, read the file and pass its exact `versionHash` to\n  `write-local-file` with `requireExpectedVersionHash: true`; on conflict,\n  re-read and re-plan. Keep the optimistic preview until HMR/runtime confirms\n  the result. Human write consent remains mandatory and agents cannot grant it.\n\n## Verification\n\nFor a plain \"open this app\" request, `open-visual-edit`'s own response is\nthe verification \u2014 see Open The Design Surface. Reach for the checks below\nonly to diagnose an actual report, or to confirm an applied edit landed:\n\n- `list-localhost-connections` returns the expected connection and routes.\n- The Design editor opens in overview mode.\n- Every requested screen renders the intended localhost URL, showing real app\n  content rather than an endless loading spinner.\n- The screen iframe carries a `src`, not a `srcdoc`. A localhost screen with a\n  `srcdoc` is a bug, not a slow load \u2014 check it in the browser devtools before\n  reporting the canvas as working.\n- Alt-dragging a screen copies the URL-backed frame, not an inline HTML clone.\n- A query/path edit changes only the target screen's URL metadata and iframe.\n- `get-visual-edit-pending` is the tab-free handoff; acknowledge its revision\n  after applying. `get-visual-edit-prompt` is the browser equivalent.\n- The Code tab shows a local-files root for the connection and opens its files.\n";
+export declare const DESIGN_VISUAL_EDIT_SKILL_MD = "---\nname: visual-edit\ndescription: >-\n  Open and collaboratively edit a running local app in Design, with shared\n  fallback previews and source handoff. Use when the user asks to inspect,\n  share, or edit a real local app in Design.\nmetadata:\n  visibility: exported\n---\n\n# Visual Edit\n\nUse `/visual-edit` when the user wants to inspect or edit a real local app\nvisually instead of generating standalone Alpine HTML. The source of truth is\nthe running localhost app plus its route URLs. Design shows those routes as\niframe-backed screens on the infinite canvas.\n\nThe editor is hosted at `https://design.agent-native.com`. Never start local\nDesign; only the target app and bridge run locally.\n\nSee the [Visual Edit guide](https://github.com/BuilderIO/agent-native/blob/main/skills/visual-edit/README.md)\nfor a worked onboarding-flow example.\n\n## Fast local startup\n\n- Do not install this skill into the target app or start a local Design server.\n  The skill belongs to the coding host; Design is always the hosted app above.\n- If you need to start an Agent-Native framework app yourself, use\n  `AUTH_DISABLED=1` with its normal dev command. This is local-only and gives\n  the visual editor the framework's dev identity without a user login.\n- If an agent-owned local server redirects a requested screen to `/sign-in`,\n  restart that server with `AUTH_DISABLED=1` and probe the route again before\n  opening Design. Never present a sign-in page as the requested screen.\n- Before calling `open-visual-edit`, verify the target URL responds. Start an\n  agent-owned dev server with its normal command when it is down, and wait for\n  the requested routes to respond before opening Design. Never leave a dead\n  localhost URL in the canvas.\n- Preserve a server you did not start; use its existing authenticated browser\n  session or explain that the target app, rather than Design, requires login.\n- When the user gives explicit paths, skip route inventory and place those\n  paths directly. Discover routes only when paths were not supplied.\n\n## Installation\n\n`npx @agent-native/core@latest skills add visual-edit` installs the skill and\nhosted Design MCP connector. `npx skills@latest add BuilderIO/agent-native\n--skill visual-edit` installs instructions only; page-capable WebMCP hosts need\nno connector installation.\n\n## Put Design Beside The Chat\n\nPrefer the MCP App from `open-visual-edit`: it keeps Design beside\nchat. Use **Copy prompt** to hand the visual edits to the coding agent; the host\nmay request conversation confirmation. Otherwise,\n`openUrl` is a credential-free, read-only fallback; never claim it is editable.\n\n- Inline-browser hosts should open `https://design.agent-native.com/visual-edit`\n  and call its `open-visual-edit` WebMCP tool. It works signed in or out; the\n  one-time capability is not a Design account session. A page-capable browser\n  controller is enough, so Claude-in-Chrome, Claude Code browser tools, the\n  ChatGPT Chrome/browser extension, Puppeteer or Playwright MCP, CDP, and\n  similar JavaScript-capable controllers do not need the hosted MCP connector.\n- VS Code uses its Design webview/deep link. Without page WebMCP, use the hosted\n  Design MCP connector and its normal OAuth/device authorization. Never replace\n  either path with a local Design server.\n\nInside Design, use **Show/Hide UI** from the `Cmd K` menu or press Figma's\n`Shift \\` shortcut to toggle all editing chrome so only the canvas remains.\n\n## Browser WebMCP (Default Without Connector)\n\nWithout a connected Design MCP, use a visible browser tab with a main-world\nJavaScript evaluator. Prefer the host's inline browser; use external Chrome\nonly when requested or unavailable. Open\n`https://design.agent-native.com/visual-edit`, keep it visible while tools\nregister, and read the title before work. Never enter, copy, or request\npasswords, cookies, tokens, or codes. Signed-out loopback visual-edit works;\nother pages that block tools behind sign-in still require a signed-in tab.\nIf the browser exposes CDP permissions, grant `local-network-access` to\n`https://design.agent-native.com` before calling page tools; otherwise use the\npage's Connect button and let the browser's permission prompt complete.\n\nUse a native browser-session WebMCP bridge when the host provides one: list\nonce with `list-browser-session-webmcp-tools` and run with\n`run-browser-session-webmcp-tool`, or use the `list-host-webmcp-tools` and\n`run-host-webmcp-tool` pair. Preserve the exact discovered name, origin, and\nargs. Otherwise use the page-world API. Agent-Native pages expose this helper:\n\nExample assumes signed-in or existing bridge; fresh signed-out loopback must add\nthe locally held `bridgeToken` described below.\n\n```js\nconst an = window.__agentNativeWebMcp;\nconst status = await an.ready({ waitMs: 20_000 });\nif (status.state !== \"ready\") throw new Error(status.error ?? status.state);\nconst tools = await an.tools(\"visual-edit\");\nif (!tools.some((tool) => tool.name === \"open-visual-edit\")) {\n  throw new Error(\"open-visual-edit is not registered yet\");\n}\nconst result = await an.call(\"open-visual-edit\", {\n  devServerUrl: \"http://localhost:5173\",\n  paths: [\"/\"],\n  navigate: true,\n}, { waitMs: 2_000 });\nif (result.state === \"pending\") {\n  // On the next evaluation, read the still-running call without replaying it.\n  an.result(result.id);\n}\n```\n\nIf the helper is absent, use standard WebMCP directly. `document.modelContext`\nis canonical; `navigator.modelContext` is deprecated:\n\n```js\nconst ctx = document.modelContext;\nconst tool = (await ctx.getTools()).find((candidate) => candidate.name === NAME);\nif (!tool) throw new Error(`WebMCP tool not found: ${NAME}`);\nconst codex = typeof ctx.codexExecuteTool === \"function\" ||\n  typeof ctx.codexGetTools === \"function\";\nconst result = await ctx.executeTool(tool, codex ? ARGS : JSON.stringify(ARGS));\n```\n\nThe helper handles live discovery, partial registries, and pending calls. If a\ncall returns `state: \"pending\"`, read `an.result(id)` on the next evaluation;\nnever replay a write. For Claude Code or Cowork, `javascript_tool` runs this\npage-world code with top-level `await`; for Codex open the page with\n`cua.createBrowserTab(\"iab\", url, { visible: true })`, then use CDP\n`Runtime.evaluate` with `awaitPromise: true`; Puppeteer and Playwright MCP can\nuse their page evaluator. Playwright isolated worlds cannot see\n`document.modelContext`. Keep evaluator output small, batch dependent calls,\nand do not navigate inside a batch.\n\nTool descriptors are page-local. Do not copy them into the host, hand-build\nauthenticated HTTP requests, or replace named tools with clicks, typing, DOM\nautomation, or screenshots. UI automation remains appropriate for canvas work\nwithout a named tool or when requested. If both bridges are unavailable after\none discovery and one independent evaluator check, use hosted MCP/CLI before\nchanging state.\n\nFor a fresh signed-out loopback connection, generate the bridge token locally,\nstart the durable bridge with it, and pass that same token once as the page\ntool's `bridgeToken`; the page never returns it. Reuse a matching running\nbridge without the token. Account-backed or private Design work requires a\nsigned-in session or the authenticated Design MCP connector. After canvas edits,\ncall `an.call(\"get-visual-edit-prompt\", {}, { waitMs: 2_000 })` and apply the\nreturned handoff. The page tool may show an approval dialog; let the user\napprove it and never bypass that consent.\n\n## Core Model\n\n- Each screen is a URL-backed iframe, not copied HTML.\n- Each screen keeps URL metadata: `connectionId`, `routeId`, `path`,\n  `url`, `bridgeUrl`, title, and viewport size.\n- The owner edits through the local bridge. Shared\n  `/visual-edit/:designId?share=1` links render a sanitized inert snapshot,\n  refreshed on route or DOM changes; guests never reach the owner's localhost.\n  Guest edits stay pending until an owner or editor applies them to source.\n- Authorized viewers and commenters on private designs can edit the shared\n  Visual Edit canvas and submit pending changes without writing design files.\n  The owner or editor applies those source changes.\n- **The `/visual-edit` skill needs no Design account sign-in.**\n  `open-visual-edit` mints a five-minute, single-use capability for the exact\n  `/visual-edit/:designId` local-editor route. The MCP host redeems it outside\n  model-visible text, then opens the existing editor with localhost edit access.\n  A public `/visual-edit/:designId` route enables browser-only DOM editing of\n  public localhost snapshots; handoffs stay pending until applied. The owner\n  sees **Apply edits** when a recipient has pending changes.\n  This capability is not an account session: `/_agent-native/session` remains\n  signed out, and account-backed save/share/generate actions remain denied.\n- Hosted MCP highlights `get-visual-edit-pending`; pass the visual-edit\n  design ID for a tab-free handoff. It returns a revision; after applying,\n  call `acknowledge-visual-edit-pending` with that revision, then pull again.\n  `empty` means no edits; `session-ended` means edits were lost;\n  `unknown` means the marker was unreadable, not proof of no change.\n- Browser hosts can use page-local `get-visual-edit-prompt`.\n- The `open-visual-edit` action is owned by Design. From another app, use the\n  hosted MCP server at `https://design.agent-native.com/mcp` or the page's\n  WebMCP helper, not `pnpm action` in the target app. The page path works\n  signed out only for loopback apps in public mode, using a short-lived\n  capability-scoped principal; hosted MCP uses its normal OAuth identity.\n- Ordinary public links stay read-only. Public `/visual-edit/:designId` and\n  authorized private shares allow DOM-only edits, never source writes. Guest\n  Interact is blocked; snapshots strip active content and owner-local resources,\n  and persisted writes stay role-gated. Loopback is not a trust boundary because\n  tunnels can proxy remote callers.\n- The live editor is same-origin through the local bridge proxy. This boots\n  CSR apps and root-relative assets, but it is still a localhost editing proxy:\n  app-origin cookies, WebSockets/HMR, SSE, and non-GET app API calls may need a\n  future dev-server/plugin integration for perfect parity with the app's own\n  origin.\n- The canvas is the editing view; Interact runs the normal URL with rails and a\n  device bar. Interact preserves navigation, scrolling, links, and controls;\n  the canvas pans/zooms and suppresses native frame interaction.\n- While a localhost screen has pending live visual edits, do not switch back to\n  Interact until the user either applies the edits to source or explicitly\n  aborts/discards the preview.\n- Alt-drag duplicates a localhost frame and its URL metadata. Change the copy's\n  path/query for another state; preserve the order of named or numbered flows.\n  Shorthand like `localhost:1234/onboarding/1` means\n  `http://localhost:1234/onboarding/1`.\n\n## Useful Canvas Sets\n\nUse a focused batch of 3-7 frames by default: one ordered frame per requested\nroute/query state, repeat routes at requested desktop/tablet/mobile viewports,\nand include URL-addressable empty, loading, error, modal-open, or selected-item\nstates. Keep the Screens section readable so Layers remains useful while\nediting. Do not expand beyond 7 frames unless the user explicitly asks for an\nexhaustive audit or a complete route inventory.\n\nDo not expand every discovered route or every viewport unless the user asks for\nan exhaustive audit. Preserve the user's labels and sequence so the canvas\nreads like the workflow they described.\n\n## Select And Reprompt\n\nWhen a chat message begins with `[Reprompt selection]`, the selected subtree is\na hard write boundary. The only mutation path is `propose-node-rewrite` with\nthe exact `repromptId`, target, and `baseVersionHash` captured in\n`design-reprompt-pending:<designId>:<fileId>`. Never use `apply-visual-edit`,\n`apply-source-edit`, `write-source`, `write-local-file`, `edit-design`, or any\nother content-writing action for that request. Clarifying questions are allowed,\nbut a requested change must remain a proposal.\n\nProduce one variant by default. Produce two or three only when the instruction\nasks for options. A retry includes `priorProposalId`; keep the same target and\nbase version, incorporate the feedback, and call `propose-node-rewrite` again.\nThe UI previews the returned subtree without persisting it.\n\nUse `resolve-node-rewrite` for the accept/reject lifecycle. Accept applies the\nchosen variant as one version-checked inline/Yjs content transaction so one\nundo restores the prior structure; reject clears the proposal without changing\ncontent. For conversational resolution such as \"apply the second one,\" call\n`view-screen`, read the active `design.reprompt.proposal`, and pass its\n`proposalId` plus the zero-based `variantIndex` to `resolve-node-rewrite`.\n\n## Review Quality\n\nTreat the running app as truth, preserving its component language, tokens, route\nstate, and content. Compare visual edits before/after at requested viewports and\ncheck meaningful URL, hover, focus, scroll, and modal states.\n\n## Account And Sharing Model\n\n- The capability permits live iframe inspection, session-local edits, undo/redo,\n  and **Copy prompt**. The copied instructions go to the coding agent; they do\n  not persist account-owned Design data.\n- Public `/design/:id` links stay read-only without a signed-in owner/editor\n  session. Never use the local capability to upgrade that ordinary sharing\n  surface.\n- Prefer links returned by Design actions or `/_agent-native/open` deep links;\n  never surface `_session=` tokens or hand-build capability URLs.\n- Do not attempt account-backed write actions with the browser capability. The\n  trusted local `open-visual-edit` CLI call may register its bridge, create or\n  reuse its workspace-owned local design, and place screens without an account.\n  Direct source-file action writes, generation, saving into an account, and\n  sharing still require an authenticated action caller. If a signed-out visitor\n  wants those durable account operations, send them through the framework\n  sign-in return flow first.\n\n## Required Local Bridge\n\nThe live-edit bridge is unlocked by a shared secret (the \"bridge token\") that\nmust match on two sides: the local bridge process, and the user's connection row\nin Design (which the browser reads to authorize `/live-edit-bridge`,\n`/read-file`, `/write-file`). Get them to match by letting the\n`open-visual-edit` action mint the token, then starting the\nbridge with it. This is the only ordering that works for the remote-MCP flow -\nthe bridge cannot push its own token to the server without a CLI auth token, so\nthe server mints instead and the bridge adopts.\nThe `connectionId` (usually `localhost_...`) only identifies the row; never\npass it as `bridgeToken`.\n\nFor a fresh signed-out browser flow, generate the token locally, keep it in the\nhost process, and pass it once as the page tool's optional `bridgeToken`; the\npage never returns it:\n\n```bash\nBRIDGE_TOKEN=\"$(node -e 'process.stdout.write(require(\"node:crypto\").randomBytes(32).toString(\"hex\"))')\"\nAGENT_NATIVE_BRIDGE_TOKEN=\"$BRIDGE_TOKEN\" npx @agent-native/core@latest design connect --url http://localhost:5173 --root . --daemon\n```\n\nReuse an existing matching connection without `bridgeToken`; hosted MCP can\nmint the token when page WebMCP is unavailable.\n\nFrom the target app repo, make sure its dev server is running, then:\n\n**1. Discover routes without starting a durable bridge** (one-shot, exits):\n\n```bash\nnpx @agent-native/core@latest design connect --url http://localhost:5173 --root . --json\n```\n\nThis prints the manifest (routes + capabilities). Parse it to build\n`routeManifest` for the next step. (Skip this if the user already gave explicit\npaths/URLs to place.)\n\nInside the agent-native monorepo itself, use the workspace CLI instead of\n`npx` \u2014 `npx` installs the last published `@agent-native/core`, which will not\ncontain local changes and costs a slow install on every call:\n\n```bash\npnpm dev:cli design connect --url http://localhost:5173 --root templates/<app> --json\n```\n\n**2. For the hosted MCP path, call `open-visual-edit`** (see Action Flow below)\nwith NO `bridgeToken`.\nThe server mints one, stores it on the user's connection row, copies it into the\nplaced screens' metadata, and returns it to you as `bridgeToken`. Capture it.\n\n**3. Start the persistent bridge adopting that token** (single line; prefer the\nenv var so the secret does not appear in `ps`):\n\n```bash\nAGENT_NATIVE_BRIDGE_TOKEN=\"<bridgeToken from step 2>\" npx @agent-native/core@latest design connect --url http://localhost:5173 --root . --daemon\n```\n\n(Equivalently, pass `--bridge-token <token>`.) This starts a detached bridge on\n`http://127.0.0.1:7331`, adopts the server-minted token \u2014 so bridge and row\nagree and live-edit authorizes with no self-registration \u2014 and stays alive after\nthe command exits.\n\nFor a manual health/manifest check on the running bridge:\n\n```bash\ncurl http://127.0.0.1:7331/health\n```\n\n`/health` needs no token. The full manifest at `/manifest.json` is\npreview-token protected, so an unauthenticated `curl` of it returns\n`{\"ok\":false,\"error\":\"invalid or missing preview token\"}` \u2014 that response means\nthe bridge is up, not that it is broken.\n\nOnly use `--json` for the step-1 route probe. Never use `--json`, `--once`,\nor `--dry-run` for the durable step-3 bridge: they print the manifest and exit,\nso Design falls back to a non-editable live iframe.\n\nThe bridge listens on a single fixed port (7331) and refuses to start for a\nsecond, different app. It is detached with no log file, so if `--daemon` reports\na timeout, check for a stale process (`lsof -ti:7331`) before retrying.\n\nIf local Design uses PGlite, never invoke the in-process CLI against that server:\nboth open the same directory and the second owner is rejected. For a signed-out\nlocal test, start Design with `AUTH_DISABLED=1`, open `/visual-edit`, and call\nthe server-action `open-visual-edit` through `window.__agentNativeWebMcp` after\nit registers. This keeps one PGlite owner; `get-visual-edit-prompt` is only the\npost-edit handoff. With auth enabled, sign in to hosted Design MCP or use shared\nPostgres before using the CLI action.\n\n## Action Flow\n\nWhen a browser is available, reuse the local bridge and call the Design page's\n`open-visual-edit` WebMCP tool. For a fresh signed-out connection, pass the\nlocally held `bridgeToken`; it reads its preview manifest and challenge proof,\nthen sends both for validation. Hosted Design never fetches `127.0.0.1`. If the\npage has no WebMCP, use the connected Design MCP server or its normal hosted\nMCP fallback.\n\nFrom another app, call the connected Design MCP tool\n`mcp__agent-native-design__open-visual-edit` with the JSON arguments below. It\nregisters or refreshes the localhost bridge,\nmints and stores the bridge token, creates or reuses a Design project, places\nURL-backed screens, stores visual-edit context, and navigates to overview mode\nin one call. Never run `pnpm action` from the target app's checkout: its local\nregistry does not contain Design actions.\n\nCall it before starting the durable bridge: it does not contact the bridge, so\nthe server can mint `bridgeToken` for the bridge to adopt. Omit that input.\n\n```json\n{\n  \"title\": \"Docs homepage visual edit\",\n  \"devServerUrl\": \"http://localhost:5173\",\n  \"bridgeUrl\": \"http://127.0.0.1:7331\",\n  \"rootPath\": \"/absolute/path/to/app\",\n  \"routeManifest\": { \"...\": \"from /manifest.json\" },\n  \"paths\": [\"/\", \"/pricing\", \"/checkout?step=payment\"]\n}\n```\n\nThe action returns `designId`, `connectionId`, `bridgeToken`, `screens`,\n`urlPath`, and credential-free `openUrl`. MCP App metadata carries the\nhidden one-time launcher. Keep the ids for follow-ups\nand pass the token to `design connect`; reusing the connection reuses its token.\n\n### Desktop and mobile side by side\n\nPass `viewports` to place every requested route once per viewport. Frames lay\nout as a grid: one row per route, one column per viewport. Presets are\n`desktop` (1280x900), `laptop` (1440x900), `tablet` (834x1112), and `mobile`\n(390x844); an explicit `{ \"label\": \"...\", \"width\": N, \"height\": N }` also works.\n\n```json\n{\n  \"title\": \"Tasks responsive visual edit\",\n  \"devServerUrl\": \"http://localhost:5173\",\n  \"bridgeUrl\": \"http://127.0.0.1:7331\",\n  \"rootPath\": \"/absolute/path/to/app\",\n  \"paths\": [\"/tasks\", \"/inbox\"],\n  \"viewports\": [\"desktop\", \"mobile\"]\n}\n```\n\nPrefer this over two separate calls with `defaultWidth`/`defaultHeight`: it\nkeeps each route's viewports aligned in a row and titles them\n`Tasks \u2014 Desktop` / `Tasks \u2014 Mobile` so the canvas reads clearly. `viewports`\noverrides `defaultWidth`/`defaultHeight`. With no `routes`/`paths`, it expands\nevery route in the localhost manifest, which is usually far more frames than\nthe user wants \u2014 name the paths.\n\n### Managing screens and breakpoints manually\n\nSelect a screen and use the right-rail **Screen** section to switch between\nStatic HTML and URL-backed modes, edit its route/path, choose a localhost\nconnection, add another URL screen, or remove the selected screen. URL mode\nkeeps the iframe live; switching to Static stores a sanitized snapshot of the\ncurrent frame, including its current client state when the page can provide it.\nThe same operations are available to a page-capable agent through\n`add-localhost-screens`, `update-screen-source`, `add-breakpoint`, and\n`remove-breakpoint`.\n\n### Adding more page frames later\n\nCall `open-visual-edit` again with the same `designId` and `connectionId` and\nonly the new paths. Existing frames for the same route and viewport are\nrefreshed in place rather than duplicated, and a frame the user has dragged or\nresized keeps its position unless you explicitly pass `x`/`y`/`width`/`height`.\n\n```json\n{\n  \"designId\": \"<existing-design-id>\",\n  \"connectionId\": \"<existing-connection-id>\",\n  \"devServerUrl\": \"http://localhost:5173\",\n  \"paths\": [\"/settings\", \"/team\"],\n  \"startY\": 2200\n}\n```\n\nDo NOT add `defaultWidth`/`defaultHeight` just to restate the default size:\nsupplying either one marks the viewport as explicitly requested, which\noverwrites frame sizes the user has already adjusted on the canvas.\n\nFor a numbered flow the user describes in chat, keep the labels and order:\n\n```json\n{\n  \"designId\": \"<existing-design-id>\",\n  \"connectionId\": \"<existing-connection-id>\",\n  \"devServerUrl\": \"http://localhost:1234\",\n  \"routes\": [\n    { \"url\": \"localhost:1234/onboarding/1\", \"title\": \"Screen 1\" },\n    { \"url\": \"localhost:1234/onboarding/2\", \"title\": \"Screen 2\" },\n    { \"url\": \"localhost:1234/onboarding/3\", \"title\": \"Screen 3\" }\n  ]\n}\n```\n\nIf no `routes` or `paths` are supplied, `open-visual-edit` uses every route\nfrom the localhost manifest.\n\nFallback only when `open-visual-edit` is unavailable and hosted Design MCP is\nauthorized:\n\n1. Register or refresh the bridge with `connect-localhost`, passing the\n   `/manifest.json` result as `routeManifest` and `capabilities`.\n2. Create or reuse a Design project with `create-design`.\n3. Place URL-backed screens with `add-localhost-screens`.\n4. Navigate to overview mode with `navigate`.\n\nThe fallback still targets `https://design.agent-native.com`; only the app and\nbridge URLs are localhost. Never run `pnpm action` from `templates/design`.\n\n## Open The Design Surface\n\n- Use the `link`, `deepLink`, or MCP App embed returned by Design actions so the\n  user sees the canvas. Prefer the MCP App; its host launcher carries the\n  one-time capability. The credential-free `openUrl` is read-only fallback.\n- Never return or open a hand-built `/design/:id?_session=...` URL.\n- If the user is working in VS Code, the Agent-Native extension can open the\n  same URL via\n  `vscode://builder.agent-native/open?url=<encoded-design-url>`. Its\n  `Agent-Native: Open Design Canvas` command also starts the local bridge and\n  opens hosted Design in the VS Code side panel.\n- Once `open-visual-edit` returns the expected `screenCount`, hand back the\n  link and stop. Do not open it yourself in a browser-automation tool to\n  screenshot or poll until it renders \u2014 a cold dev server can take 10-30s\n  regardless of who's watching, and that wait adds nothing the response didn't\n  already confirm. Reach for browser automation only if the user later reports\n  the canvas is broken.\n\n## Applying Visual Edits Back To Source\n\nWith Design closed, call hosted Design MCP's highlighted\n`get-visual-edit-pending` for the design ID; it returns the handoff and\nrevision. Verify the applied source, acknowledge that revision, then pull again.\nIf MCP is unavailable, read the local bridge:\n\n```bash\nnpx @agent-native/core@latest design pending --root . --design-id <design-id-from-visual-edit-url>\n```\n\nPass the ID after `visual-edit` in the Design URL; the CLI prints that\ndesign's prompt (`null` when empty).\n\nCanvas edits on a localhost screen never write source directly. They stay\npending until the coding agent pulls them with `get-visual-edit-pending` or the\ncopied prompt, then writes them to source. There is no separate canvas Apply\nbutton. An MCP App sends its prompt through the host or local Design agent;\notherwise use **Copy prompt to your agent**.\n\nChatGPT and Claude Code should pull, apply, acknowledge, and pull again.\nBrowser WebMCP hosts can call `get-visual-edit-prompt`. Never acknowledge\nbefore applying the source change.\n\n- Style, text, and drag/drop edits collect into one pending batch for a single\n  apply.\n- After the write lands, the target app's own dev-server HMR refreshes the\n  frames \u2014 no manual reload. If frames do not refresh, the write did not land;\n  say so rather than assuming.\n- The separate disk-icon \"Apply to source\" button is the deterministic\n  whole-file HTML/CSS writer. It is intentionally disabled for compiled\n  `.jsx`/`.tsx` routes \u2014 those must go through the agent path above.\n\n## Editing URLs\n\nKeep localhost screens as URL files plus `screenMetadata[fileId]`. Do not\nreplace them with copied `srcdoc` HTML unless the user explicitly asks for a\nfrozen snapshot. To change a state, rerun `open-visual-edit` with the new\npath/query, use the Screen settings section, call `update-screen-source`, or\nduplicate the screen and update the copy's URL metadata.\n\n## Local Files in the Code Tab\n\nOnce a connection is registered, the design editor's Code panel (left rail \u2192\nCode, or `navigate --view editor --designId <id> --leftPanel code`) shows a\nlocal-files workspace root for that connection next to the design's own files.\nTreat that root like VS Code opened at the connected project directory: file\ntree, search, open/edit, and save are backed by the real local files. It lists\nthe connected app's text/code files through the bridge\n(`list-local-files` / `read-local-file`); build output, `node_modules`,\n`.git`, and secret-looking paths (`.env*`, key files) are always excluded.\n\n- Browsing and reading need only editor access on the design plus the running\n  bridge.\n- Saving goes through `write-local-file`: the first save opens the\n  write-consent dialog (an 8-hour, folder-scoped grant) and retries\n  automatically once granted. Only text/code files are writable; secret paths\n  are always blocked.\n- If the agent calls `write-local-file` directly (not through a UI save) and it\n  fails with \"no write-consent grant\", call `request-localhost-write-consent`.\n  It opens the write-consent dialog in the editor, or reports `alreadyGranted`\n  if one already exists. Granting is human-only \u2014\n  `grant-localhost-write-consent` is hidden from agents, so you cannot approve\n  it yourself. Tell the user to click \"Allow writes\", then retry\n  `write-local-file` once. Do not keep retrying blindly: the write stays\n  blocked until the user approves.\n- Saves are conflict-checked against the file's on-disk version \u2014 a file that\n  changed since it was read fails with a version conflict instead of being\n  overwritten.\n\n## React Source Writeback\n\n- Use compiler/debug provenance (project-relative file, line, column,\n  component, and runtime multiplicity) to locate React/TSX source. Treat it as\n  evidence, not as permission for a generic AST structural transform.\n- Read `positionPrecision` on every anchor before you trust `line`/`column`.\n  `authored` means those are the real JSX coordinates. `transformed` means they\n  are the dev server's own output coordinates \u2014 React 19 removed `_debugSource`\n  and exposes only an owner stack, so this is the normal case on a Vite/Next\n  dev server, and the line will not match the file. `unknown` means no tier was\n  reported. On anything but `authored`, use the file and component to find the\n  element by its JSX shape and re-derive the line from the file you read; never\n  edit at the reported line.\n- A single-instance leaf text edit, literal `className`/`class` edit, or flat\n  literal `style={{ ... }}` property may use `apply-visual-edit` with a\n  `local-file` source and a complete `target.sourceAnchor`. Forward the\n  anchor's `positionPrecision` with it \u2014 the action refuses a `transformed`\n  anchor with `status: \"needsAgent\"` instead of seeking to a line that means\n  something else in the authored file. Preview first (omit `persist`), inspect\n  `proposedDiff`, then call with `persist: true`.\n- Reparenting, grouping/ungrouping, wrappers, dynamic expressions, repeated\n  `.map()` instances, shared components, breakpoint-scoped edits, and\n  cross-file changes go through the coding agent with complete subject/target\n  anchors and their runtime relationship. `apply-visual-edit` refuses these\n  with `status: \"needsAgent\"` rather than guessing.\n- Before each write, read the file and pass its exact `versionHash` to\n  `write-local-file` with `requireExpectedVersionHash: true`; on conflict,\n  re-read and re-plan. Keep the optimistic preview until HMR/runtime confirms\n  the result. Human write consent remains mandatory and agents cannot grant it.\n\n## Verification\n\nFor a plain \"open this app\" request, `open-visual-edit`'s own response is\nthe verification \u2014 see Open The Design Surface. Reach for the checks below\nonly to diagnose an actual report, or to confirm an applied edit landed:\n\n- `list-localhost-connections` returns the expected connection and routes.\n- The Design editor opens in overview mode.\n- Every requested screen renders the intended localhost URL, showing real app\n  content rather than an endless loading spinner.\n- The screen iframe carries a `src`, not a `srcdoc`. A localhost screen with a\n  `srcdoc` is a bug, not a slow load \u2014 check it in the browser devtools before\n  reporting the canvas as working.\n- Alt-dragging a screen copies the URL-backed frame, not an inline HTML clone.\n- A query/path edit changes only the target screen's URL metadata and iframe.\n- `get-visual-edit-pending` is the tab-free handoff; acknowledge its revision\n  after applying. `get-visual-edit-prompt` is the browser equivalent.\n- The Code tab shows a local-files root for the connection and opens its files.\n";

package/dist/cli/skills-content/design-visual-edit-skill.js

@@ -49,9 +49,9 @@ no connector installation.
 
 ## Put Design Beside The Chat
 
-Prefer the interactive MCP App from \`open-visual-edit\`: it keeps Design beside
-chat and routes **Apply design updates** through the host's MCP Apps bridge. The
-host may ask the user to confirm the current conversation. Otherwise,
+Prefer the MCP App from \`open-visual-edit\`: it keeps Design beside
+chat. Use **Copy prompt** to hand the visual edits to the coding agent; the host
+may request conversation confirmation. Otherwise,
 \`openUrl\` is a credential-free, read-only fallback; never claim it is editable.
 
 - Inline-browser hosts should open \`https://design.agent-native.com/visual-edit\`
@@ -243,8 +243,8 @@ check meaningful URL, hover, focus, scroll, and modal states.
 ## Account And Sharing Model
 
 - The capability permits live iframe inspection, session-local edits, undo/redo,
-  **Apply design updates**, and **Copy prompt**. These hand bounded source
-  instructions to the coding agent; they do not persist account-owned Design data.
+  and **Copy prompt**. The copied instructions go to the coding agent; they do
+  not persist account-owned Design data.
 - Public \`/design/:id\` links stay read-only without a signed-in owner/editor
   session. Never use the local capability to upgrade that ordinary sharing
   surface.
@@ -503,8 +503,9 @@ Pass the ID after \`visual-edit\` in the Design URL; the CLI prints that
 design's prompt (\`null\` when empty).
 
 Canvas edits on a localhost screen never write source directly. They stay
-pending until the canvas shows **Apply design updates** (local) or **Apply edits**
-(shared). An MCP App sends its prompt through the host or local Design agent;
+pending until the coding agent pulls them with \`get-visual-edit-pending\` or the
+copied prompt, then writes them to source. There is no separate canvas Apply
+button. An MCP App sends its prompt through the host or local Design agent;
 otherwise use **Copy prompt to your agent**.
 
 ChatGPT and Claude Code should pull, apply, acknowledge, and pull again.

package/dist/client/use-agent-engine-configured.js

@@ -130,7 +130,11 @@ export function useAgentEngineConfigured(enabled = true, options) {
             return check(options);
         };
         const onConfiguredChanged = () => {
-            checkNow();
+            // Read after the shared client-status cache invalidates in its listener.
+            queueMicrotask(() => {
+                if (!cancelled)
+                    checkNow();
+            });
         };
         const onMissing = (event) => {
             if (!missingKeyEventMatchesScope(event, options))

package/dist/collab/awareness.d.ts

@@ -38,19 +38,19 @@ export declare const postAwareness: import("h3").EventHandlerWithFetch<import("h
     error: string;
     states?: undefined;
 } | {
+    error?: undefined;
     states: {
         clientId: number;
         state: string;
     }[];
-    error?: undefined;
 }>>;
 export declare const getActiveUsers: import("h3").EventHandlerWithFetch<import("h3").EventHandlerRequest, Promise<{
     error: string;
     users?: undefined;
 } | {
+    error?: undefined;
     users: {
         clientId: number;
         lastSeen: number;
     }[];
-    error?: undefined;
 }>>;

package/dist/collab/routes.d.ts

@@ -8,16 +8,16 @@ export declare const getCollabState: import("h3").EventHandlerWithFetch<import("
     state: string;
 }>>;
 export declare const postCollabUpdate: import("h3").EventHandlerWithFetch<import("h3").EventHandlerRequest, Promise<{
-    ok?: undefined;
     error: string;
+    ok?: undefined;
 } | {
     error?: undefined;
     ok: boolean;
 }>>;
 export declare const postCollabText: import("h3").EventHandlerWithFetch<import("h3").EventHandlerRequest, Promise<{
     ok?: undefined;
-    text?: undefined;
     error: string;
+    text?: undefined;
 } | {
     error?: undefined;
     ok: boolean;

package/dist/collab/struct-routes.d.ts

@@ -1,6 +1,6 @@
 export declare const postCollabJson: import("h3").EventHandlerWithFetch<import("h3").EventHandlerRequest, Promise<{
-    ok?: undefined;
     error: string;
+    ok?: undefined;
 } | {
     error?: undefined;
     ok: boolean;

package/dist/file-upload/actions/upload-image.d.ts

@@ -35,20 +35,20 @@ declare const _default: import("../../action.js").ActionDefinition<{
 } | {
     error: string;
     url?: undefined;
+    id?: undefined;
     provider?: undefined;
     configured?: undefined;
-    id?: undefined;
 } | {
     url: string;
     id: string;
     provider: string;
-    configured?: undefined;
     error?: undefined;
+    configured?: undefined;
 } | {
     url?: undefined;
+    id?: undefined;
     provider?: undefined;
     error: string;
     configured: boolean;
-    id?: undefined;
 }>;
 export default _default;

package/dist/notifications/routes.d.ts

@@ -16,6 +16,6 @@ export declare function createNotificationsHandler(): import("h3").EventHandlerW
 } | {
     count?: undefined;
     updated?: undefined;
-    error?: undefined;
     ok: boolean;
+    error?: undefined;
 }>>;

package/dist/observability/routes.d.ts

@@ -27,38 +27,38 @@ export declare function createObservabilityHandler(): import("h3").EventHandlerW
     thumbsUpRate: number;
     avgEvalScore: number;
 } | {
+    id?: undefined;
+    ok?: undefined;
     error: string;
     message: string;
     summary?: undefined;
     spans?: undefined;
-    id?: undefined;
-    ok?: undefined;
 } | {
+    id?: undefined;
     error?: undefined;
+    ok?: undefined;
     message?: undefined;
     summary: import("./types.js").TraceSummary;
     spans: import("./types.js").TraceSpan[];
-    id?: undefined;
-    ok?: undefined;
 } | {
     error?: undefined;
+    ok?: undefined;
     message?: undefined;
     summary?: undefined;
     spans?: undefined;
     id: string;
-    ok?: undefined;
 } | {
+    id?: undefined;
+    ok?: undefined;
     message?: undefined;
     summary?: undefined;
     spans?: undefined;
-    id?: undefined;
     error: any;
-    ok?: undefined;
 } | {
+    id?: undefined;
     error?: undefined;
     message?: undefined;
     summary?: undefined;
     spans?: undefined;
-    id?: undefined;
     ok: boolean;
 }>>;

package/dist/progress/routes.d.ts

@@ -2,6 +2,6 @@ export declare function createProgressHandler(): import("h3").EventHandlerWithFe
     error: string;
     ok?: undefined;
 } | {
-    ok: boolean;
     error?: undefined;
+    ok: boolean;
 }>>;

package/dist/secrets/routes.d.ts

@@ -55,31 +55,31 @@ export declare function createWriteSecretHandler(): import("h3").EventHandlerWit
 } | {
     error: string;
     errorCode?: undefined;
-    ok?: undefined;
     status?: undefined;
+    ok?: undefined;
 } | {
     error: string;
     errorCode: string;
-    ok?: undefined;
     status?: undefined;
+    ok?: undefined;
 } | {
     errorCode?: undefined;
     ok: boolean;
     status: string;
     error?: undefined;
 } | {
-    ok?: undefined;
     error: string;
     removed?: undefined;
+    ok?: undefined;
 } | {
     ok: boolean;
     removed: boolean;
     error?: undefined;
 }>>;
 export declare function createTestSecretHandler(): import("h3").EventHandlerWithFetch<import("h3").EventHandlerRequest, Promise<{
-    ok?: undefined;
     error: string;
     note?: undefined;
+    ok?: undefined;
 } | {
     ok: boolean;
     note?: undefined;

package/dist/server/agent-engine-api-key-route.d.ts

@@ -65,8 +65,8 @@ export declare function createAgentEngineApiKeyHandler(): import("h3").EventHand
     error: any;
     code: any;
 } | {
-    errorCode?: undefined;
     error?: undefined;
+    errorCode?: undefined;
     code?: undefined;
     ok: boolean;
     key: string;

package/dist/server/agent-engine-default-model-route.d.ts

@@ -8,17 +8,17 @@ export declare const AGENT_ENGINE_API_KEY_ACTION_NAME = "agent-engine-api-key";
  * resolveEngine's credential detection.
  */
 export declare function createAgentEngineDisconnectHandler(): import("h3").EventHandlerWithFetch<import("h3").EventHandlerRequest, Promise<{
-    ok?: undefined;
     error: string;
     scope?: undefined;
+    ok?: undefined;
 } | {
     ok: boolean;
     error: any;
     scope?: undefined;
 } | {
-    error?: undefined;
     ok: boolean;
     scope: "org" | "user";
+    error?: undefined;
 }>>;
 export interface DefaultModelSelectionRequest {
     engine: string;

package/dist/server/agent-engine-ollama-models-route.d.ts

@@ -3,7 +3,7 @@ export declare function createAgentEngineOllamaModelsHandler(): import("h3").Eve
     models?: undefined;
     ok?: undefined;
 } | {
+    error?: undefined;
     ok: boolean;
     models: string[];
-    error?: undefined;
 }>>;

package/dist/server/realtime-token.d.ts

@@ -54,8 +54,8 @@ export declare function createRealtimeTokenHandler(): import("h3").EventHandlerW
     expiresAt?: undefined;
     ttlSeconds?: undefined;
 } | {
+    error?: undefined;
     token: string;
     expiresAt: string;
     ttlSeconds: number;
-    error?: undefined;
 }>>;

package/dist/templates/chat/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 All notable user-facing changes to this app are documented here.
 
+## 2026-09-30
+
+### Improved
+
+- Chat uses a compact + menu with context submenus, keeps task, automation, and skill actions at the root, and omits Generate Image.
+
 ## 2026-09-27
 
 ### Fixed

package/dist/templates/chat/changelog/2026-09-30-compact-composer-context-menus.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-09-30
+---
+
+Chat uses a compact + menu with context submenus, keeps task, automation, and skill actions at the root, and omits Generate Image.

package/dist/templates/workspace-root/package.json

@@ -17,6 +17,7 @@
   },
   "dependencies": {
     "@agent-native/core": "latest",
+    "drizzle-orm": "^0.45.3",
     "postgres": "^3.4.9"
   },
   "devDependencies": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.198.7-nightly-20260930213124",
+  "version": "0.198.7",
   "description": "The agentic application framework for building autonomous agents with intuitive UIs",
   "homepage": "https://github.com/BuilderIO/agent-native#readme",
   "bugs": {
@@ -662,8 +662,8 @@
     "yaml": "^2.9.0",
     "yjs": "^13.6.33",
     "zod": "^4.3.6",
-    "@agent-native/agentkit": "^0.198.7-nightly-20260930213124",
-    "@agent-native/recap-cli": "^0.5.56"
+    "@agent-native/agentkit": "^0.198.7",
+    "@agent-native/recap-cli": "^0.5.57"
   },
   "devDependencies": {
     "@ai-sdk/anthropic": "^3.0.71",
@@ -734,7 +734,7 @@
     "xlsx": "^0.18.5"
   },
   "peerDependencies": {
-    "@agent-native/core-corpus": "0.198.7-nightly-20260930213124",
+    "@agent-native/core-corpus": ">=0.196.0",
     "@ai-sdk/anthropic": ">=3",
     "@ai-sdk/cohere": ">=3",
     "@ai-sdk/google": ">=3",

package/src/templates/chat/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 All notable user-facing changes to this app are documented here.
 
+## 2026-09-30
+
+### Improved
+
+- Chat uses a compact + menu with context submenus, keeps task, automation, and skill actions at the root, and omits Generate Image.
+
 ## 2026-09-27
 
 ### Fixed

package/src/templates/chat/changelog/2026-09-30-compact-composer-context-menus.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-09-30
+---
+
+Chat uses a compact + menu with context submenus, keeps task, automation, and skill actions at the root, and omits Generate Image.

package/src/templates/workspace-root/package.json

@@ -17,6 +17,7 @@
   },
   "dependencies": {
     "@agent-native/core": "latest",
+    "drizzle-orm": "^0.45.3",
     "postgres": "^3.4.9"
   },
   "devDependencies": {