@agent-native/core 0.115.4 → 0.116.0

package/agent-native.eject.json

@@ -17,6 +17,7 @@
         "context7",
         "sentry",
         "notion",
+        "granola",
         "semgrep",
         "linear",
         "atlassian",

package/corpus/README.md

@@ -28,6 +28,6 @@ rg -n "defineAction|useActionQuery" node_modules/@agent-native/core/corpus
 
 ## Generated Counts
 
-- core files: 1527
-- toolkit files: 144
-- template files: 6369
+- core files: 1529
+- toolkit files: 145
+- template files: 6410

package/corpus/core/CHANGELOG.md

@@ -1,5 +1,33 @@
 # @agent-native/core
 
+## 0.116.0
+
+### Minor Changes
+
+- 03a043e: Improve Agent Resources settings with contextual documentation links, cleaner file empty states, and file-name creation that defaults extensionless files to Markdown.
+- 03a043e: Add explicit collaboration access modes for resource-scoped and intentionally
+  deployment-wide authenticated documents, with legacy compatibility and Doctor
+  guidance for implicit configurations.
+- 03a043e: Add a catalog-driven in-chat MCP connection suggestion that recognizes Granola
+  and resumes the pending chat request after OAuth or direct connection setup.
+
+### Patch Changes
+
+- 03a043e: Expose the Google Drive workspace connection and provider API to Analytics for Google Sheets exports.
+- 03a043e: Make realtime voice the clear primary microphone action, remember the selected input mode, improve speech waveform responsiveness, and show a shine while the voice agent is working.
+- 03a043e: Prevent reasoning messages from losing their assistant UI provider, and add a progressively disclosed recent-chat rail for app sidebars.
+- 03a043e: Improve the MCP device authorization success message hierarchy by separating the confirmation title from the follow-up connection guidance.
+- 03a043e: Keep page-chat controls clear of messages, continue shared sync in background tabs at a relaxed cadence, and make the latest tool visibly active until the turn finishes.
+- 03a043e: Trim the MCP connection authorization page by removing redundant branding and status pills.
+- 03a043e: Make template feedback controls opt in through `VITE_AGENT_NATIVE_FEEDBACK_URL` so cloned apps do not send feedback to Agent Native by default.
+- 03a043e: Ensure interrupted or empty agent runs always end with a visible final response instead of a bare tool call.
+- 03a043e: Keep the active chat tab fully visible while the right sidebar opens and its tab strip expands.
+- Updated dependencies [03a043e]
+- Updated dependencies [03a043e]
+- Updated dependencies [03a043e]
+  - @agent-native/toolkit@0.9.1
+  - @agent-native/recap-cli@0.5.1
+
 ## 0.115.4
 
 ### Patch Changes

package/corpus/core/agent-native.eject.json

@@ -17,6 +17,7 @@
         "context7",
         "sentry",
         "notion",
+        "granola",
         "semgrep",
         "linear",
         "atlassian",

package/corpus/core/docs/AGENTS.md

@@ -59,7 +59,7 @@ preserve public action, state, auth, and agent-chat runtime contracts.
 | Localize UI copy and language choices | `content/internationalization.md`, `content/client.md`                                                   |
 | Build headless or chat-first apps     | `content/pure-agent-apps.md`, `content/agent-surfaces.md`, `content/using-your-agent.md`                 |
 | Add automations or scheduled work     | `content/automations.md`, `content/recurring-jobs.md`                                                    |
-| Compose apps or call sibling agents   | `content/a2a-protocol.md`, `content/multi-app-workspace.md`, `content/workspace.md`                      |
+| Compose apps or call sibling agents   | `content/a2a-protocol.md`, `content/multi-app-workspace.md`, `content/agent-resources.mdx`               |
 | Expose tools to external agents       | `content/external-agents.md`, `content/mcp-protocol.md`, `content/mcp-apps.md`, `content/mcp-clients.md` |
 | Add integrations, setup, or secrets   | `content/onboarding.md`, `content/workspace-connections.md`, `content/security.md`                       |
 | Build extensions or custom widgets    | `content/extensions.md`, `content/agent-web-surfaces.md`                                                 |

package/corpus/core/docs/content/agent-mentions.mdx

@@ -154,7 +154,7 @@ model: inherit
 You are a focused design agent.
 ```
 
-See [Agent Resources — Custom Agents](/docs/workspace#custom-agents) for the full format (including `tools`, `delegate-default`, and model overrides).
+See [Agent Resources — Custom Agents](/docs/agent-resources#custom-agents) for the full format (including `tools`, `delegate-default`, and model overrides).
 
 You can create them from the Resources tab using:
 
@@ -240,4 +240,4 @@ Custom mention providers appear alongside the built-in agent and file providers
 - [**A2A Protocol**](/docs/a2a-protocol) — how connected-agent mentions are resolved over the wire
 - [**Agent Teams**](/docs/agent-teams) — spawn sub-agents and pass the `agent` profile parameter
 - [**Skills Guide**](/docs/skills-guide) — author the skills referenced with `/`
-- [**Agent Resources**](/docs/workspace#custom-agents) — the full custom-agent profile format
+- [**Agent Resources**](/docs/agent-resources#custom-agents) — the full custom-agent profile format

package/corpus/core/docs/content/{workspace.mdx → agent-resources.mdx}

@@ -5,12 +5,6 @@ description: "Claude-Code-level customization per user — skills, memory, instr
 
 # Agent Resources
 
-<Callout tone="info">
-
-**Which workspace doc?** This page covers **Agent Resources** — the agent customization layer. For the deployment shape (one monorepo, many apps) see [Multi-App Workspaces](/docs/multi-app-workspace); for governance (who reviews, approves, and owns what) see [Workspace Governance](/docs/workspace-management).
-
-</Callout>
-
 Every agent-native app ships with **agent resources**: the customization layer that makes the agent yours. It contains team instructions (`AGENTS.md`), shared learnings (`LEARNINGS.md`), personal structured memory (`memory/MEMORY.md`), skills the agent pulls in on demand, custom sub-agents, scheduled jobs, and connected MCP servers — everything you'd expect from a Claude Code / Codex setup.
 
 The twist: **it's SQL rows, not filesystem files.** Each user gets their own set of agent resources stored in the database. There's no dev-box to spin up, no container per user, no files to mount. A multi-tenant SaaS can give every user a fully-customizable agent for essentially free, because all of it is rows — personal memory, personal MCP servers, personal skills, personal sub-agents — and the shared codebase hosts all of them at once.
@@ -233,7 +227,7 @@ For example:
 - Avoid: unsupported superlatives and vague AI claims
 ```
 
-## Resources Tab {#workspace-panel}
+## Resources Tab {#resources-tab}
 
 The agent panel includes a **Resources** tab alongside Chat and CLI. It shows a folder-organized tree of all resources, an inline editor for any text file (Markdown, JSON, YAML, plain text), and the `+` menu's typed creation flows (Files, Skills, Agents, Scheduled Tasks). Users can browse inherited workspace defaults and create/edit/delete personal or organization resources.
 

package/corpus/core/docs/content/agent-teams.mdx

@@ -14,7 +14,7 @@ Agent Teams runs on the core run-manager: events stream and persist, aborts prop
 ## The mental model {#mental-model}
 
 - **Main chat** — the orchestrator. Reads your request, delegates. Rarely does heavy work itself.
-- **Sub-agents** — run with their own thread, their own system prompt, their own tool set. Each maps to a "custom agent" profile in [Agent Resources](/docs/workspace).
+- **Sub-agents** — run with their own thread, their own system prompt, their own tool set. Each maps to a "custom agent" profile in [Agent Resources](/docs/agent-resources).
 - **Chips** — the rich preview card that appears inline in the main chat, showing the sub-agent's current step, streaming output, and final summary. Collapsed by default; expands to the full conversation on click.
 - **Bidirectional messaging** — the main agent can send follow-ups to a running sub-agent; a sub-agent can message back when it hits an ambiguous point.
 
@@ -105,7 +105,7 @@ Three ways to kick off a sub-agent, from least to most explicit:
 
 The user types `@agent-name` in the chat composer. A dropdown of workspace sub-agents appears. Selecting one inserts a chip; on submit the main agent delegates the message to that sub-agent.
 
-Custom agents live in agent resources at `agents/<slug>.md` — a Markdown file with YAML frontmatter. See [Custom Agents](/docs/workspace#custom-agents) for the format.
+Custom agents live in agent resources at `agents/<slug>.md` — a Markdown file with YAML frontmatter. See [Custom Agents](/docs/agent-resources#custom-agents) for the format.
 
 ### 2. The main agent delegates automatically {#auto-delegate}
 
@@ -247,7 +247,7 @@ interface AgentTask {
 
 ## Custom agent profiles {#profiles}
 
-Sub-agents map to custom agent profiles — Markdown files at `agents/<slug>.md` in agent resources that appear in the `@mention` dropdown and serve as delegation targets. [Agent Resources — Custom Agents](/docs/workspace#custom-agents) owns the full format (frontmatter, `tools`, `delegate-default`, model overrides).
+Sub-agents map to custom agent profiles — Markdown files at `agents/<slug>.md` in agent resources that appear in the `@mention` dropdown and serve as delegation targets. [Agent Resources — Custom Agents](/docs/agent-resources#custom-agents) owns the full format (frontmatter, `tools`, `delegate-default`, model overrides).
 
 ## Delegation depth guard {#depth-guard}
 
@@ -326,6 +326,6 @@ When a sub-agent is at or below the cap, the framework injects a line into its r
 
 ## What's next
 
-- [**Agent Resources — Custom Agents**](/docs/workspace#custom-agents) — the profile format
+- [**Agent Resources — Custom Agents**](/docs/agent-resources#custom-agents) — the profile format
 - [**A2A Protocol**](/docs/a2a-protocol) — when the "sub-agent" lives in a different app entirely
 - [**Actions**](/docs/actions) — the tools a sub-agent calls

package/corpus/core/docs/content/dispatch.mdx

@@ -91,15 +91,15 @@ If you're running a single template standalone, you don't need Dispatch — each
 
 Seven capabilities, all sitting on top of the same workspace database the other apps use:
 
-| Capability               | What it gives you                                                               | Set it up                                                           |
-| ------------------------ | ------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
-| **Central inbox**        | Slack, email, Telegram, WhatsApp all reach one agent with shared memory + tools | **Settings → Messaging** ([Messaging](/docs/messaging))             |
-| **Secret vault**         | Store each credential once; rotate in one place across every app                | **Vault** + access mode (all-apps or manual)                        |
-| **Cross-app delegation** | Routes a request to the right specialist app over A2A and replies in-thread     | Automatic ([A2A](/docs/a2a-protocol))                               |
-| **Unified MCP gateway**  | One MCP connector for external agents reaches every granted workspace app       | [External Agents](/docs/external-agents)                            |
-| **Workspace resources**  | Author skills/instructions/profiles once; apps inherit them at runtime          | **Resources** ([Agent Resources](/docs/workspace#global-resources)) |
-| **Dreams**               | Reviews past runs/feedback and proposes durable improvements for you to approve | **Dreams** tab                                                      |
-| **Approval flow**        | Gate sensitive runtime changes behind inline admin review                       | **dispatch approval policy**                                        |
+| Capability               | What it gives you                                                               | Set it up                                                                 |
+| ------------------------ | ------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
+| **Central inbox**        | Slack, email, Telegram, WhatsApp all reach one agent with shared memory + tools | **Settings → Messaging** ([Messaging](/docs/messaging))                   |
+| **Secret vault**         | Store each credential once; rotate in one place across every app                | **Vault** + access mode (all-apps or manual)                              |
+| **Cross-app delegation** | Routes a request to the right specialist app over A2A and replies in-thread     | Automatic ([A2A](/docs/a2a-protocol))                                     |
+| **Unified MCP gateway**  | One MCP connector for external agents reaches every granted workspace app       | [External Agents](/docs/external-agents)                                  |
+| **Workspace resources**  | Author skills/instructions/profiles once; apps inherit them at runtime          | **Resources** ([Agent Resources](/docs/agent-resources#global-resources)) |
+| **Dreams**               | Reviews past runs/feedback and proposes durable improvements for you to approve | **Dreams** tab                                                            |
+| **Approval flow**        | Gate sensitive runtime changes behind inline admin review                       | **dispatch approval policy**                                              |
 
 Each is detailed below.
 
@@ -134,7 +134,7 @@ The single MCP connector URL external agents add (e.g. `https://dispatch.agent-n
 
 Skills, guardrail instructions, agent profiles, and reference resources can be authored once in Dispatch and inherited by the rest of the workspace. Resources with **All apps** scope are global: Dispatch stores them once at workspace scope, and every app agent reads them at runtime. They are not copied into each app, and there is no manual workspace-resource sync step. App shared resources and personal resources can override or narrow the workspace defaults locally.
 
-See [Agent Resources — Global resources](/docs/workspace#global-resources) for the canonical path table, starter pack, and override model.
+See [Agent Resources — Global resources](/docs/agent-resources#global-resources) for the canonical path table, starter pack, and override model.
 
 MCP server resources use JSON and are intentionally HTTP-only. Store tokens in
 Dispatch Vault, grant or sync those keys to the target apps, and reference them

package/corpus/core/docs/content/drop-in-agent.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Drop-in Agent"
-description: "Mount the agent chat + workspace into any React app with <AgentPanel>, <AgentSidebar>, and sendToAgentChat()."
+description: "Mount the agent chat + resources into any React app with <AgentPanel>, <AgentSidebar>, and sendToAgentChat()."
 ---
 
 # Drop-in Agent
@@ -47,7 +47,7 @@ All of these are exported from `@agent-native/core/client`.
       </div>
       <div class="diagram-node panel">
         Agent panel<br /><small class="diagram-muted"
-          >chat &middot; CLI &middot; workspace</small
+          >chat &middot; CLI &middot; resources</small
         >
       </div>
     </div>
@@ -170,7 +170,7 @@ export default function AgentRoute() {
 }
 ```
 
-`<AgentPanel>` gives you the raw tabs (Chat / CLI / Workspace) without the sidebar wrapper, the collapse button, or any state persistence. Put it wherever you want; you handle the layout.
+`<AgentPanel>` gives you the raw tabs (Chat / CLI / Resources) without the sidebar wrapper, the collapse button, or any state persistence. Put it wherever you want; you handle the layout.
 
 ### Selected props
 
@@ -337,5 +337,5 @@ The user sees a chat button in the header, can open it, and can talk to the agen
 
 - [**Actions**](/docs/actions) — `defineAction()` and `useActionMutation()`
 - [**Context Awareness**](/docs/context-awareness) — selection, navigation, view-screen
-- [**Agent Resources**](/docs/workspace) — what the Resources tab contains (skills, memory, MCP servers, scheduled jobs)
+- [**Agent Resources**](/docs/agent-resources) — what the Resources tab contains (skills, memory, MCP servers, scheduled jobs)
 - [**Voice Input**](/docs/voice-input) — the microphone in the chat composer

package/corpus/core/docs/content/external-agents.mdx

@@ -90,7 +90,7 @@ The identity rule is the safety hinge: the link is just `view` + record ids + fi
 - **Your own runtime behind Agent-Native chat:** see [Agent Surfaces](/docs/agent-surfaces#byo-agent) and [Native Chat UI](/docs/native-chat-ui#byo-agent-runtimes) when an agent built with another framework should power `<AssistantChat runtime={...}>`.
 - **Your app consuming MCP tools:** see [MCP Clients](/docs/mcp-clients) when an agent-native app needs to call tools exposed by another MCP server.
 - **Another app or agent via A2A:** use [Agent Mentions](/docs/agent-mentions) and [A2A](/docs/a2a-protocol) when agent-native apps should discover and delegate to each other.
-- **Local custom sub-agents:** use [Agent Resources](/docs/workspace) when you want custom agent profiles inside the app's own agent resources.
+- **Local custom sub-agents:** use [Agent Resources](/docs/agent-resources) when you want custom agent profiles inside the app's own agent resources.
 
 ## Easy setup {#easy-setup}
 

package/corpus/core/docs/content/frames.mdx

@@ -79,7 +79,7 @@ component in dev and prod.
 
 - Exported as `AgentPanel` from `@agent-native/core/client`, with a
   production-only variant `ProductionAgentPanel`.
-- Provides the full Chat / CLI / Workspace surface, so the agent input stays on
+- Provides the full Chat / CLI / Resources surface, so the agent input stays on
   the shared composer stack used everywhere else in the framework.
 - Reads `application_state.navigation` every turn, so it already knows which
   view you're in and what's selected — you don't have to re-explain "this".

package/corpus/core/docs/content/integrations.mdx

@@ -7,7 +7,7 @@ search: "integrations directory MCP connectors OAuth manual setup restricted pro
 # Connect your stack
 
 Agent-Native apps can use the tools your team already works in. This directory
-mirrors the framework's current remote MCP catalog: 25 provider presets that
+mirrors the framework's current remote MCP catalog: 26 provider presets that
 can be discovered from the composer and Workspace Resources surfaces. It also
 explains the separate reusable workspace-connection and provider-API layers so
 you can choose the connection path that matches your product.
@@ -39,7 +39,7 @@ These self-hosted provider marks keep the directory fast and deployable
 without a third-party logo CDN. Connection details and status categories remain
 in the directory table below.
 
-<Diagram id="doc-block-integrations-wall" title="Remote MCP integrations" summary="A self-hosted logo wall of the 25 remote MCP presets currently shipped in the Agent-Native framework." frame="hide" renderMode="design">
+<Diagram id="doc-block-integrations-wall" title="Remote MCP integrations" summary="A self-hosted logo wall of the 26 remote MCP presets currently shipped in the Agent-Native framework." frame="hide" renderMode="design">
 
 ```html
 <div class="integration-wall">
@@ -67,6 +67,16 @@ in the directory table below.
       <div><strong>Notion</strong><small>Knowledge &amp; docs</small></div>
     </div>
   </div>
+  <div class="integration-card">
+    <div class="integration-head">
+      <span class="integration-mark"
+        ><img src="/integration-logos/granola.svg" alt=""
+      /></span>
+      <div>
+        <strong>Granola</strong><small>Meetings &amp; transcripts</small>
+      </div>
+    </div>
+  </div>
   <div class="integration-card">
     <div class="integration-head">
       <span class="integration-mark"
@@ -327,6 +337,7 @@ but need provider or administrator setup before a generic connection can work.
 | [Context7](https://context7.com/)                                                                                                                                       | No auth                | Ready · verified                   | `https://mcp.context7.com/mcp`            | Fetch current library and framework docs.                                                                                                                                                                                         |
 | [Sentry](https://docs.sentry.io/product/sentry-mcp/)                                                                                                                    | Header / token         | Ready · preflight only             | `https://mcp.sentry.dev/mcp`              | Add a Sentry bearer token as the `Authorization` header.                                                                                                                                                                          |
 | [Notion](https://developers.notion.com/guides/mcp/get-started-with-mcp)                                                                                                 | OAuth                  | Ready · preflight only             | `https://mcp.notion.com/mcp`              | User OAuth; enterprise admins can audit or restrict MCP clients.                                                                                                                                                                  |
+| [Granola](https://docs.granola.ai/help-center/sharing/integrations/mcp)                                                                                                 | OAuth                  | Ready · preflight only             | `https://mcp.granola.ai/mcp`              | Browser OAuth; review the meeting notes and transcripts the connected Granola account makes available.                                                                                                                            |
 | [Semgrep](https://github.com/semgrep/mcp#readme)                                                                                                                        | No auth                | Ready · preflight only             | `https://mcp.semgrep.ai/mcp`              | Scan code for security findings.                                                                                                                                                                                                  |
 | [Linear](https://linear.app/docs/mcp)                                                                                                                                   | OAuth                  | Ready · preflight only             | `https://mcp.linear.app/mcp`              | Authorize the workspace and issue permissions required by the workflow.                                                                                                                                                           |
 | [Atlassian Rovo MCP](https://developer.atlassian.com/cloud/rovo-mcp/guides/getting-started/)                                                                            | OAuth + provider setup | Restricted                         | `https://mcp.atlassian.com/v1/mcp/authv2` | Admins may need to trust the app origin and enable Rovo Read, Write, and Search permissions.                                                                                                                                      |

package/corpus/core/docs/content/key-concepts.mdx

@@ -418,7 +418,7 @@ Two architectural rules keep apps portable across databases and hosts:
 
 ## Agent Resources {#workspace}
 
-Every user gets a personal set of **agent resources** — instructions, skills, memory, custom sub-agents, scheduled jobs, and connected MCP servers — all stored in SQL rather than files. That makes Claude-Code-level customization viable inside multi-tenant SaaS without spinning up a container per user. See [Agent Resources](/docs/workspace).
+Every user gets a personal set of **agent resources** — instructions, skills, memory, custom sub-agents, scheduled jobs, and connected MCP servers — all stored in SQL rather than files. That makes Claude-Code-level customization viable inside multi-tenant SaaS without spinning up a container per user. See [Agent Resources](/docs/agent-resources).
 
 ## Related building blocks {#building-blocks}
 
@@ -433,7 +433,7 @@ These sit on top of the same contract and have their own deep dives:
 Adopting the framework is valuable mostly because of what you stop having to build. The moment your app follows the six rules, you inherit:
 
 - **One action = every surface.** Every action defined with `defineAction()` is simultaneously an agent tool, a typesafe frontend hook (`useActionQuery` / `useActionMutation`), a framework-owned HTTP transport, a CLI command, an MCP tool for external clients, and an A2A tool for other agent-native apps. Optional `link` and `mcpApp` metadata add deep links and MCP Apps UI without a second implementation.
-- **A full set of agent resources per user.** Skills, shared `LEARNINGS.md`, personal `memory/MEMORY.md`, `AGENTS.md`, custom sub-agents, scheduled jobs, connected MCP servers — all SQL-backed, no dev-box required. See [Agent Resources](/docs/workspace).
+- **A full set of agent resources per user.** Skills, shared `LEARNINGS.md`, personal `memory/MEMORY.md`, `AGENTS.md`, custom sub-agents, scheduled jobs, connected MCP servers — all SQL-backed, no dev-box required. See [Agent Resources](/docs/agent-resources).
 - **Drop-in React components.** `<AgentPanel />` and `<AgentSidebar />` render chat + resources anywhere in your app. See [Drop-in Agent](/docs/drop-in-agent).
 - **BYO agent chat runtimes.** The same chat UI can sit on top of OpenAI Agents, OpenAI Responses, Claude Agent SDK, Vercel AI SDK, AG-UI, or your own normalized HTTP stream. See [Native Chat UI](/docs/native-chat-ui#byo-agent-runtimes).
 - **Live sync between agent and UI.** Same-process writes stream immediately over `/_agent-native/events`; a lightweight poll keeps serverless, cron, and cross-process writes convergent. Mutating actions invalidate action-backed queries automatically, so agent-created records appear without a manual refresh. See [Live Sync](#polling-sync) below.

package/corpus/core/docs/content/mcp-clients.mdx

@@ -275,7 +275,7 @@ export default {
 };
 ```
 
-Preset ids are `context7`, `sentry`, `notion`, `semgrep`, `linear`,
+Preset ids are `context7`, `sentry`, `notion`, `granola`, `semgrep`, `linear`,
 `atlassian`, `supabase`, `neon`, `stripe`, `cloudflare`, `gitlab`, `figma`,
 `vercel`, `github`, `slack`, `asana`, `hubspot`, `intercom`, `monday`,
 `webflow`, `paypal`, `box`, `netlify`, and `zapier`.
@@ -287,6 +287,12 @@ link to their official setup instructions, but do not show a misleading
 one-click connect button. Provider restrictions change over time, so verify
 the vendor setup note before enabling one in a production catalog.
 
+When a chat request clearly names an unconnected catalog provider, the
+composer and relevant completed responses can show an inline **Connect**
+suggestion. OAuth and direct connections preserve that request in the current
+tab and resume it after setup completes; long or abandoned requests expire
+automatically.
+
 ### Atlassian / Jira
 
 The Atlassian preset uses Atlassian Rovo MCP's OAuth 2.1 endpoint,

package/corpus/core/docs/content/multi-app-workspace.mdx

@@ -7,7 +7,7 @@ description: "Host many agent-native apps in one monorepo with shared auth, RBAC
 
 <Callout tone="info">
 
-**Which workspace doc?** This page covers the **deployment shape** — one monorepo, many apps, shared auth and a unified deploy. For the agent customization layer (Agent Resources: `AGENTS.md`, memory, skills, custom agents) see [Agent Resources](/docs/workspace); for governance (who reviews, approves, and owns what) see [Workspace Governance](/docs/workspace-management).
+**Which workspace doc?** This page covers the **deployment shape** — one monorepo, many apps, shared auth and a unified deploy. For the agent customization layer (Agent Resources: `AGENTS.md`, memory, skills, custom agents) see [Agent Resources](/docs/agent-resources); for governance (who reviews, approves, and owns what) see [Workspace Governance](/docs/workspace-management).
 
 </Callout>
 
@@ -222,7 +222,7 @@ Because the shared package is a `workspace:*` dependency, pnpm symlinks it into
 
 Use `packages/shared` for code-level defaults that should ship with the repo: plugins, shared actions, shared React code, filesystem `AGENTS.md`, and filesystem skills. Use Dispatch workspace resources for runtime-editable global context that admins want to manage without a code change.
 
-Dispatch resources are scoped **All apps** (every app inherits them at runtime, no copy or sync step) or **Selected apps** (granted per app for app-specific context). See [Agent Resources](/docs/workspace#global-resources) for the full resource-model table, path conventions, and the recommended starter pack.
+Dispatch resources are scoped **All apps** (every app inherits them at runtime, no copy or sync step) or **Selected apps** (granted per app for app-specific context). See [Agent Resources](/docs/agent-resources#global-resources) for the full resource-model table, path conventions, and the recommended starter pack.
 
 ## Authentication and RBAC {#auth-and-rbac}
 
@@ -332,7 +332,7 @@ The workspace pattern is intentionally narrow. A few things it deliberately does
 
 ## What's next {#whats-next}
 
-- [Agent Resources](/docs/workspace) — the customization layer (`AGENTS.md`, `LEARNINGS.md`, personal memory, skills, custom agents) every app in the workspace shares.
+- [Agent Resources](/docs/agent-resources) — the customization layer (`AGENTS.md`, `LEARNINGS.md`, personal memory, skills, custom agents) every app in the workspace shares.
 - [Workspace Governance](/docs/workspace-management) — branching, CODEOWNERS, PR review across many apps in one repo.
 - [Multi-Tenancy](/docs/multi-tenancy) — organizations, roles, and per-org data isolation.
 - [Cross-App SSO](/docs/cross-app-sso) — identity federation for separate-domain deploys.

package/corpus/core/docs/content/real-time-collaboration.mdx

@@ -240,10 +240,11 @@ export default defineConfig({
 
 ### 3. Add the collab server plugin
 
-Always set `resourceType` to the name of the shareable resource registered
-via `registerShareableResource`. Without it, collab push events are delivered
-to all authenticated users without document-level scoping, and the server
-logs a one-time warning.
+Choose the access mode that matches the data model. Owned or shareable records
+use `mode: "resource"` with the type registered via
+`registerShareableResource`. Records deliberately shared with every
+authenticated user on the deployment use explicit `mode: "all-authenticated"`.
+Never invent a resource type merely to silence a warning.
 
 ```ts
 // server/plugins/collab.ts
@@ -253,10 +254,13 @@ export default createCollabPlugin({
   table: "documents",
   contentColumn: "content",
   idColumn: "id",
-  resourceType: "document", // required for access-scoped event delivery
+  access: { mode: "resource", resourceType: "document" },
 });
 ```
 
+Omitting `access` is a deprecated legacy behavior. It behaves like
+`all-authenticated`, logs a warning, and is flagged by Doctor.
+
 ### 4. Use the client hook
 
 ```ts
@@ -590,23 +594,37 @@ plugin:
 
 ## Security {#security}
 
-### Always set `resourceType`
+### Choose the access model explicitly
+
+For owned or shareable resources, use the resource type registered through
+`registerShareableResource`:
 
 ```ts
 createCollabPlugin({
-  resourceType: "document", // the name passed to registerShareableResource
+  access: { mode: "resource", resourceType: "document" },
 });
 ```
 
-Without `resourceType` the plugin logs a warning and broadcasts collab push
-events to all authenticated users on the deployment without document-level
-scoping. Non-owners fall back to state-vector catch-up (safe but higher
-latency) regardless of whether `resourceType` is set.
+For a resource intentionally shared deployment-wide, say so explicitly:
+
+```ts
+createCollabPlugin({
+  access: { mode: "all-authenticated" },
+});
+```
+
+Do not invent a `resourceType` to make a warning disappear: resource mode is
+valid only when the corresponding ownership and sharing model exists. Omitting
+`access` is supported for legacy compatibility, behaves like
+`all-authenticated`, logs a warning, and is flagged by Doctor.
+
+Non-owner sharees with explicit access use state-vector catch-up through the
+poll path (safe, higher latency).
 
 ### Access checks
 
-All collab routes require authentication. When `resourceType` is set, reads
-require at least viewer access and writes require editor access, using the
+All collab routes require authentication. In resource mode, reads require at
+least viewer access and writes require editor access, using the
 same `resolveAccess` / `assertAccess` helpers as the sharing system. A 404
 (not 403) is returned on access failures to avoid leaking document existence.
 
@@ -618,7 +636,7 @@ Override per-plugin:
 
 ```ts
 createCollabPlugin({
-  resourceType: "document",
+  access: { mode: "resource", resourceType: "document" },
   maxPayloadBytes: 512 * 1024, // 512 KB
 });
 ```
@@ -726,7 +744,7 @@ Key properties:
 - [Real-Time Sync](/docs/client#usedbsync) — the `useDbSync` + `useChangeVersion`
   system that delivers the `updatedAt` bump driving editor reconciliation.
 - [Security](/docs/security) — `registerShareableResource`, `resolveAccess`,
-  and `assertAccess` for the access model referenced by `resourceType`.
+  and `assertAccess` for resource-scoped collaboration.
 - [Sharing](/docs/sharing) — how documents are shared and how access is granted.
 - [Template: Content](/docs/template-content) — reference implementation of
   collaborative rich-text editing.

package/corpus/core/docs/content/recurring-jobs.mdx

@@ -9,7 +9,7 @@ A **recurring job** is a prompt that runs on a cron schedule. It's how the agent
 
 Recurring jobs fire on a clock. To react to _events_ (a booking created, an email received) — same `jobs/` file format plus conditions — see [Automations](/docs/automations).
 
-Jobs live in [Agent Resources](/docs/workspace) at `jobs/<name>.md` — just a Markdown file with YAML frontmatter. No registration, no wiring. Drop the file in and the framework picks it up.
+Jobs live in [Agent Resources](/docs/agent-resources) at `jobs/<name>.md` — just a Markdown file with YAML frontmatter. No registration, no wiring. Drop the file in and the framework picks it up.
 
 ## A job file {#job-file}
 
@@ -40,12 +40,12 @@ Jobs live in [Agent Resources](/docs/workspace) at `jobs/<name>.md` — just a M
     {
       lines: "7-12",
       label: "The prompt",
-      note: "The body is just a prompt — the agent runs it at each firing with all its normal tools and workspace context.",
+      note: "The body is just a prompt — the agent runs it at each firing with all its normal tools and agent context.",
     },
   ]}
 />
 
-That's it. The body is a prompt the agent runs at each scheduled firing. The agent has access to all the same tools and workspace context it has in an interactive chat — actions, skills, memory, connected MCP servers, sub-agents.
+That's it. The body is a prompt the agent runs at each scheduled firing. The agent has access to all the same tools and agent context it has in an interactive chat — actions, skills, memory, connected MCP servers, sub-agents.
 
 ## Frontmatter {#frontmatter}
 
@@ -54,7 +54,7 @@ That's it. The body is a prompt the agent runs at each scheduled firing. The age
 | `schedule`   | cron expression               | _(required)_ | Standard 5-field cron. `"0 7 * * *"` = every day at 07:00; `"0 */4 * * *"` = every 4 hours.            |
 | `enabled`    | boolean                       | `true`       | Flip to `false` to pause without deleting the job.                                                     |
 | `runAs`      | `"creator"` \| `"shared"`     | `"creator"`  | `"creator"` runs with the job owner's identity and `ANTHROPIC_API_KEY`. `"shared"` uses the org's key. |
-| `createdBy`  | email                         | _(auto)_     | Populated when the job is created through the workspace UI or by the agent.                            |
+| `createdBy`  | email                         | _(auto)_     | Populated when the job is created through the Agent Resources UI or by the agent.                      |
 | `orgId`      | string                        | _(auto)_     | Org scope; inherited from the creator's active org.                                                    |
 | `lastRun`    | ISO timestamp                 | _(managed)_  | Written by the scheduler after each run.                                                               |
 | `lastStatus` | `"success"` \| `"error"` \| … | _(managed)_  | Latest outcome.                                                                                        |
@@ -211,7 +211,7 @@ The scheduler is a framework plugin (the internal `processRecurringJobs()` routi
 
 ## Debugging a job {#debugging}
 
-- Open `jobs/<name>.md` in the workspace — the frontmatter shows `lastRun`, `lastStatus`, `lastError`, `nextRun`.
+- Open `jobs/<name>.md` in Agent Resources — the frontmatter shows `lastRun`, `lastStatus`, `lastError`, `nextRun`.
 - **Test it without waiting:** there's no force-fire tool. To exercise the same work on demand, either paste the job's prompt into the agent chat and let it run there, or temporarily set the schedule to the next minute so the scheduler picks it up on the next tick (then restore the real cron).
 - **Pause it:** flip `enabled: false`. The file stays put, just stops running.
 
@@ -234,7 +234,7 @@ A single `manage-jobs` tool is registered in every template. The `action` parame
 
 Don't confuse recurring jobs with `@agent-native/scheduling`:
 
-- **Recurring jobs (this page)** — cron-scheduled _prompts_ the agent runs in the background. Framework-level. Lives in the workspace. Runs on any agent-native app.
+- **Recurring jobs (this page)** — cron-scheduled _prompts_ the agent runs in the background. Framework-level. Lives in Agent Resources. Runs on any agent-native app.
 - **`@agent-native/scheduling`** — a reusable domain package for building calendar/booking features (event types, availability windows, bookings). Powers the `calendar` template and custom scheduling surfaces.
 
 Recurring jobs are "how do I make the agent act on its own?" The scheduling package is "how do I build a calendar app?" Different concerns.
@@ -242,7 +242,7 @@ Recurring jobs are "how do I make the agent act on its own?" The scheduling pack
 ## What's next
 
 - [**Automations**](/docs/automations) — add event triggers and conditions to the same `jobs/` format
-- [**Agent Resources**](/docs/workspace) — where jobs live alongside skills, memory, and custom agents
+- [**Agent Resources**](/docs/agent-resources) — where jobs live alongside skills, memory, and custom agents
 - [**Actions**](/docs/actions) — the tools a job calls
 - [**MCP Clients**](/docs/mcp-clients) — connect remote or local MCP tools and OAuth grants
 - [**Agent Teams**](/docs/agent-teams) — jobs often spawn sub-agents to do parallel work

package/corpus/core/docs/content/skills-guide.mdx

@@ -141,7 +141,7 @@ Create a skill when:
 Don't create a skill when:
 
 - The guidance already exists in another skill — extend it instead
-- The guidance is a one-off — put it in `AGENTS.md` or workspace memory instead
+- The guidance is a one-off — put it in `AGENTS.md` or agent memory instead
 
 ## Skill format {#skill-format}
 
@@ -299,11 +299,11 @@ This replaces the old hack of relying on Claude Code only reading `.claude/skill
 
 </Callout>
 
-If the knowledge applies to _everyone_ working in the app ("always prefer CTEs over subqueries"), it's a skill or shared `LEARNINGS.md`. If it's about _this particular user_ ("Steve likes concise answers"), it belongs in `memory/MEMORY.md`. See [Agent Resources — Memory](/docs/workspace#memory) for the full treatment.
+If the knowledge applies to _everyone_ working in the app ("always prefer CTEs over subqueries"), it's a skill or shared `LEARNINGS.md`. If it's about _this particular user_ ("Steve likes concise answers"), it belongs in `memory/MEMORY.md`. See [Agent Resources — Memory](/docs/agent-resources#memory) for the full treatment.
 
 ## Skills vs SQL resources {#skills-vs-resources}
 
-This page frames a skill as a file at `.agents/skills/<name>/SKILL.md`. [Agent Resources](/docs/workspace#skills) frames the same skill as a SQL resource at path `skills/<slug>/SKILL.md`, scoped workspace/shared/personal. These are the same concept from two angles: Code mode reads and writes the file directly; App mode stores it as a resource row so it works without a filesystem. Author the content using this page's format either way.
+This page frames a skill as a file at `.agents/skills/<name>/SKILL.md`. [Agent Resources](/docs/agent-resources#skills) frames the same skill as a SQL resource at path `skills/<slug>/SKILL.md`, scoped workspace/shared/personal. These are the same concept from two angles: Code mode reads and writes the file directly; App mode stores it as a resource row so it works without a filesystem. Author the content using this page's format either way.
 
 ## App-backed skills — full details {#app-backed-skills-full}
 
@@ -428,6 +428,6 @@ the same instructions without maintaining a second copy.
 ## What's next {#whats-next}
 
 - [**Writing Agent Instructions**](/docs/writing-agent-instructions) — word skill descriptions and split guidance across AGENTS.md, skills, and memory
-- [**Agent Resources**](/docs/workspace#skills) — where skills live as SQL resources in App mode
+- [**Agent Resources**](/docs/agent-resources#skills) — where skills live as SQL resources in App mode
 - [**Agent Mentions**](/docs/agent-mentions) — the `/`-command trigger that invokes a skill in chat
 - [**Plan plugin & marketplace**](/docs/plan-plugin) — a real app-backed skill's end-to-end install and auto-update flow

package/corpus/core/docs/content/template-brain.mdx

@@ -549,7 +549,7 @@ Ask the agent to make changes for you — it can edit its own source. See
 
 - [**Dispatch**](/docs/dispatch) — the workspace control plane
 - [**Dispatch template**](/docs/template-dispatch) — the scaffolded coordination app
-- [**Agent Resources**](/docs/workspace) — shared resources across apps
+- [**Agent Resources**](/docs/agent-resources) — shared resources across apps
 - [**A2A Protocol**](/docs/a2a-protocol) — cross-app delegation
 - [**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

package/corpus/core/docs/content/toolkit-collaboration.mdx

@@ -38,7 +38,7 @@ operations.
 import { createCollabPlugin } from "@agent-native/core/server";
 
 export default createCollabPlugin({
-  resourceType: "document",
+  access: { mode: "resource", resourceType: "document" },
   table: "documents",
   contentColumn: "content",
 });

package/corpus/core/docs/content/using-your-agent.mdx

@@ -89,7 +89,7 @@ The agent isn't a separate app you tab over to. It ships as a handful of React c
 
 ## You can go UI-light {#ui-light}
 
-Not every app needs a full dashboard. When the agent _is_ the product, you can skip most of the custom UI: open the app, ask for what you want, and let the agent do the rest. The agent still has its management surface — history, workspace, settings — but the primary interaction is conversation rather than clicks.
+Not every app needs a full dashboard. When the agent _is_ the product, you can skip most of the custom UI: open the app, ask for what you want, and let the agent do the rest. The agent still has its management surface — history, agent resources, settings — but the primary interaction is conversation rather than clicks.
 
 ## You co-edit with it {#you-co-edit}
 

package/corpus/core/docs/content/what-is-agent-native.mdx

@@ -289,7 +289,7 @@ When the agent creates a draft email, it appears in the UI. When you click "Send
 
 The reason tools like Claude Code feel so powerful isn't the model — it's the **customization layer**: per-project instructions, skills, memory, sub-agents, connected services. You can shape the agent to your codebase, your preferences, your team.
 
-Agent-native gives every user that same customization layer — without ever leaving the app. Each app comes with a personal **workspace** where you (or anyone on your team) can:
+Agent-native gives every user that same customization layer — without ever leaving the app. Each app comes with personal **agent resources** that you (or anyone on your team) can use to:
 
 - Edit team-wide rules everyone's agent reads
 - Let the agent remember preferences automatically as you correct it
@@ -298,9 +298,9 @@ Agent-native gives every user that same customization layer — without ever lea
 - Schedule jobs to run on a cron (e.g. "every Monday morning, summarize last week")
 - Connect external services (Gmail, Stripe, Slack, internal APIs) via per-user MCP servers
 
-The twist: it's all stored in the database, not the filesystem. There's no dev environment to spin up, no container per user. Every user gets their own full workspace — personal memory, personal connections, personal skills — for essentially free, because it's all rows in a table. That's what makes Claude-Code-level flexibility viable inside a real multi-tenant SaaS product.
+The twist: it's all stored in the database, not the filesystem. There's no dev environment to spin up, no container per user. Every user gets their own full set of agent resources — personal memory, personal connections, personal skills — for essentially free, because it's all rows in a table. That's what makes Claude-Code-level flexibility viable inside a real multi-tenant SaaS product.
 
-See [Agent Resources](/docs/workspace) for the full concept.
+See [Agent Resources](/docs/agent-resources) for the full concept.
 
 ## What makes it different {#what-makes-it-different}
 
@@ -396,7 +396,7 @@ One action, many surfaces: the agent calls it as a tool, the UI calls it as a ty
 - [**Agent Surfaces**](/docs/agent-surfaces) — choose chat, native inline UI, full app pages, embedded sidecar, automation, or external agent access
 - [**Key Concepts**](/docs/key-concepts) — the architecture: SQL, actions, polling sync, context awareness, portability
 - [**Templates**](/docs/cloneable-saas) — templates as complete products you own
-- [**Agent Resources**](/docs/workspace) — the per-user customization layer (skills, memory, instructions, MCP) backed by SQL, not files
+- [**Agent Resources**](/docs/agent-resources) — the per-user customization layer (skills, memory, instructions, MCP) backed by SQL, not files
 - [**Dispatch**](/docs/dispatch) — the workspace control plane: secrets vault, Slack/email inbox, cross-app delegation
 - [**Extensions**](/docs/extensions) — sandboxed mini-apps the agent creates instantly without code changes
 - [**Drop-in Agent**](/docs/drop-in-agent) — mount `<AgentPanel>` into any React app