@agent-native/core 0.44.4 → 0.45.0

package/docs/content/template-plan.md

@@ -162,6 +162,47 @@ Sharing and commenting are the workflows that need an account:
 The hosted Plans connector lives at `https://plan.agent-native.com/_agent-native/mcp`.
 Never put shared secrets in skill files.
 
+## Local-files privacy mode {#local-files}
+
+For privacy-focused work, ask for local-files mode:
+
+```text
+Use /visual-plan in local-files mode. Do not write this plan to the Plan DB.
+```
+
+or set the convention for your agent environment:
+
+```bash
+export AGENT_NATIVE_PLANS_MODE=local-files
+```
+
+In this mode the agent writes a local MDX folder under `plans/<slug>/` and must
+not call the hosted Plan MCP tools. The durable files are:
+
+- `plan.mdx`
+- optional `canvas.mdx`
+- optional `prototype.mdx`
+- optional `.plan-state.json`
+
+After writing the folder, the agent validates and previews it locally:
+
+```bash
+agent-native plan local preview --dir plans/<slug> --kind plan
+```
+
+If you run the Plan app locally with the same `PLAN_LOCAL_DIR`, you can open the
+read-only app route:
+
+```text
+http://localhost:<port>/local-plans/<slug>
+```
+
+Local-files mode prevents plan or recap content from going to the Agent-Native
+Plan database. It also disables hosted sharing, browser comments, plan history,
+and publish/export receipts until you explicitly opt into publishing. It does
+not automatically make your coding agent's LLM local; choose a local or approved
+model if that privacy boundary matters too.
+
 ## Useful prompts
 
 - "Use `/visual-plan` before changing the auth flow."
@@ -169,6 +210,7 @@ Never put shared secrets in skill files.
 - "Use `/visual-plan` on the Markdown plan below and make it easier to review."
 - "Run `/visual-recap` on this PR so I can review the shape of the change first."
 - "Use `/visual-recap` on the diff between `main` and this branch."
+- "Use `/visual-recap` in local-files mode so no recap content is written to the Plan DB."
 
 ## Recovering from auth errors {#auth-errors}
 
@@ -205,7 +247,9 @@ persistence, or running a fully self-hosted review surface.
 For fully offline, no-account use, you can run the Plans app locally and sync
 your plans to your repo as MDX. This local mode is a separate, advanced path —
 not the default hosted flow — and is best when you need everything to stay on
-your machine and in version control.
+your machine and in version control. For the stricter no-DB path, use
+[local-files privacy mode](#local-files), which reads from MDX folders instead
+of creating local SQL rows.
 
 ## What's next
 

package/package.json

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

package/src/templates/workspace-core/.agents/skills/external-agents/SKILL.md

@@ -95,9 +95,9 @@ For local stdio proxying, Codex/Cowork compatibility, or clients without
 remote MCP OAuth, use the hosted connect fallback:
 
 ```bash
-npx @agent-native/core connect https://dispatch.agent-native.com
+npx @agent-native/core@latest connect https://dispatch.agent-native.com
 # or, for an isolated app:
-npx @agent-native/core connect https://mail.agent-native.com
+npx @agent-native/core@latest connect https://mail.agent-native.com
 ```
 
 The command opens the app in the browser, the user clicks **Authorize**, and a
@@ -111,6 +111,19 @@ Claude bearer-token entry is the migration path: the CLI replaces
 `Authorization` headers with URL-only OAuth config and tells the user to
 authenticate from `/mcp`.
 
+To re-authenticate an already-installed local/fallback client without
+reinstalling skills or connectors, use:
+
+```bash
+npx @agent-native/core@latest reconnect https://dispatch.agent-native.com --client codex
+# or:
+npx @agent-native/core@latest connect reconnect https://dispatch.agent-native.com --client codex
+```
+
+With no URL, `reconnect` searches the selected client config for the existing
+Agent Native MCP entry. Pass `--name <serverName>` when the config has multiple
+entries or a custom server name.
+
 Under the hood: a logged-in browser session mints an `A2A_SECRET`-signed JWT
 carrying the caller's `sub` + `org_domain` and a unique `jti`, so tool runs
 stay tenant-scoped via `runWithRequestContext`. The existing
@@ -339,14 +352,17 @@ and mutating actions are filtered out (`filterPublicAgentActions`). The full
 surface appears when authenticated as a real caller: a deployed /
 `AGENT_MODE=production` app, or a local app reached through `connect` /
 `agent-native mcp install` (which provisions an identity-bearing token). A
-sparse `tools/list` means you are hitting an unauthenticated dev endpoint —
-connect or present a token rather than assuming the action is missing.
+sparse or empty `tools/list` is diagnostic, not proof of auth failure: check
+OAuth scopes, compact-catalog filtering, and the client/server auth status
+before telling the user they are unauthenticated.
 
 ## Do
 
 - Do connect local/fallback clients to Dispatch with
-  `npx @agent-native/core connect https://dispatch.agent-native.com`; use a
-  direct app URL only when the host should be isolated to one app.
+  `npx @agent-native/core@latest connect https://dispatch.agent-native.com`;
+  use `npx @agent-native/core@latest reconnect ...` for reauth without
+  reinstalling; use a direct app URL only when the host should be isolated to
+  one app.
 - Do add a `link` builder to any action that produces or lists a navigable
   resource (draft, event, dashboard, document).
 - Do add `mcpApp` when a UI-capable MCP host should render an inline review or