@agent-native/core 0.7.13 → 0.7.14

package/docs/content/what-is-agent-native.md

@@ -1,108 +1,73 @@
 ---
 title: "What Is Agent-Native?"
-description: "The ladder from a naked llm() call to a full agent-native app — and why every agent needs a UI (and every app benefits from an agent)."
+description: "Why most AI apps feel half-built, what makes an app truly agent-native, and what your day-to-day experience looks like as a result."
 ---
 
 # What Is Agent-Native?
 
 Agent-native is a way of building software where the AI agent and the UI are **equal partners**. Everything the agent can do, the UI can do. Everything the UI can do, the agent can do. They share the same database, the same state, and they stay in sync.
 
-If you only remember one thing from this page, remember this: most AI apps today stop at the first rung of the ladder, and it's the biggest mistake in the space right now.
+If you only remember one thing from this page, remember this: most AI apps today stop one step short of being useful, and that gap is the biggest mistake in the space right now.
 
-## The ladder {#the-ladder}
+## What it looks like as a user {#what-it-looks-like}
 
-Here's the progression. Most teams stop at rung 1. Agent-native is rung 3.
+Picture your inbox, calendar, or analytics dashboard. Now picture an agent panel docked on the right side of that app. You can:
 
-### Rung 1 — a single LLM call (the anti-pattern) {#rung-one}
-
-```ts
-const output = await llm(prompt);
-```
-
-A text box sends a prompt, you get a string back, maybe you parse it, and you render it. There's no way for the user to course-correct, no way for the LLM to take action, no way to inspect what happened. Non-deterministic output → deterministic pipeline. It breaks the moment reality gets messy.
+- **Click anything you'd normally click.** All the buttons, lists, dashboards, keyboard shortcuts — they all still work. This is a real app, not a chat window pretending to be one.
+- **Or just ask.** Type "reply to the email from Sara saying I'll be there by 3" into the agent. It opens the right thread, drafts the reply, and shows it to you for approval — exactly as if you'd done it by hand.
+- **See what it sees.** Open an email, and the agent knows which one. Select a chart, and the agent knows which chart. Highlight a paragraph and hit Cmd+I, and the agent acts on just that paragraph.
+- **Watch it work.** As the agent does things — opens views, edits drafts, runs reports — the UI updates in real time. You can stop it, redirect it, or take over with the mouse at any moment.
+- **Steer it like a teammate.** Give feedback, queue another task, edit its instructions, audit what it did yesterday. It remembers, and it gets better at your workflows over time.
 
-You see this everywhere: "AI features" bolted onto SaaS that are basically `fetch('/summarize')` with a spinner. That's not AI product; that's a toy.
-
-### Rung 2 — tools and a loop {#rung-two}
-
-```ts
-const loop = query({ prompt, tools });
-for await (const msg of loop) {
-  if (msg.type === "tool_use") {
-    // run the tool, feed the result back into the loop
-  }
-  if (msg.type === "result") {
-    output = msg.text;
-  }
-}
-```
+That's the experience agent-native is designed for. Now here's why most products don't get there.
 
-Now the LLM can _do things_. You give it tools (`draftEmail`, `searchEmails`, `queryData`) and run a loop: LLM requests a tool → your code runs it → result goes back → loop continues until the task is done. This is what Claude Code, Codex, and the Anthropic/OpenAI agent SDKs all do under the hood.
+## Why most "AI apps" fall short {#the-ladder}
 
-This is a real step up. But on its own it still assumes the agent is correct. When it's not, the user has no steering wheel.
+There's a progression most teams climb, and most stop one rung too early.
 
-So the next move is obvious: stream the agent's work into a chat UI where the user can watch, interrupt, give feedback, queue the next message. That's the state of the art today — and it's still not enough for a real product.
+### Rung 1 — a single LLM call (the anti-pattern) {#rung-one}
 
-### Rung 3 — `<Agent />` + actions + workspace {#rung-three}
+A text box sends a prompt, the AI returns a string, and you display it. Maybe with a spinner. There's no way for the user to course-correct, no way for the AI to take action, no way to see what happened or why.
 
-```tsx
-// actions/reply-to-email.ts
-import { defineAction } from "@agent-native/core";
-import { z } from "zod";
+You see this everywhere: "AI features" that are basically a "Summarize" button bolted onto a SaaS product. They look impressive in demos and break the moment reality gets messy. That's not a product; that's a toy.
 
-export default defineAction({
-  description: "Reply to an email thread",
-  schema: z.object({
-    emailId: z.string(),
-    body: z.string(),
-  }),
-  run: async ({ emailId, body }) => {
-    await db.replies.insert({ emailId, body });
-  },
-});
-```
+### Rung 2 — a chat with tools {#rung-two}
 
-```tsx
-// Anywhere in your React app
-import { AgentSidebar } from "@agent-native/core/client";
+Now the AI can _do things_. It has tools — "draft email," "search contacts," "run query" — and a chat interface where it works in front of you, showing tool calls and results as it goes. This is what Claude, ChatGPT, and Cursor look like under the hood.
 
-<AgentSidebar />;
-```
+This is a real step up. But on its own, it's still a chat window. There's no proper UI. No dashboards, no lists, no forms, no keyboard shortcuts, no team collaboration. If the AI gets confused, you're stuck retyping rather than just clicking the right button. Non-developers struggle to get real work done in this format.
 
-```tsx
-// The same action, typesafe, from a button
-const { mutate } = useActionMutation("replyToEmail");
+### Rung 3 — agent + UI as equal partners {#rung-three}
 
-<Button onClick={() => mutate({ emailId, body: "Thanks!" })}>
-  Send Reply
-</Button>;
-```
+This is agent-native. You add a real, full-featured app around the agent — and crucially, every action the agent can take is also a button in the UI, and every button the user clicks runs the same logic the agent uses. One implementation, two ways in.
 
-One action. The agent calls it as a tool. The UI calls it as an HTTP endpoint. External agents call it over [A2A](/docs/a2a-protocol). Claude Desktop calls it as an [MCP server](/docs/mcp-protocol). Four surfaces, one implementation.
+Three things change when you reach rung 3:
 
-And you didn't just add buttons to a chatbot — you added an agent to an app. The user has a real UI with dashboards, lists, forms, and keyboard shortcuts. The agent has real tools, real memory, and real context. Both write to the same database; both see the same state.
+- **You stopped adding buttons to a chatbot. You added an agent to an app.** That's a much higher-quality product on both sides.
+- **The agent has real context.** It sees what you're looking at, what you've selected, what you just did. It writes to the same database the UI reads from, so its work shows up immediately.
+- **External agents can use it too.** Other agent-native apps can call this one's actions over the [A2A protocol](/docs/a2a-protocol). Tools like Claude Desktop can drive it as an [MCP server](/docs/mcp-protocol). One app, many entry points.
 
 That's rung 3. That's agent-native.
 
 ## Why every agent needs a UI {#why-every-agent-needs-a-ui}
 
-The hot take floating around right now is "apps are dead, agents will replace UIs, everyone will just text an agent in Telegram." That's wrong.
+The hot take in 2026 is "apps are dead, agents will replace UIs, everyone will just text an agent in Telegram." That's wrong.
 
-Every agent eventually needs a UI. Even if the agent does all the _work_, humans still need to:
+Even when the agent does all the heavy lifting, humans still need to:
 
-- **See what it's doing** — progress, tool calls, intermediate output
+- **See what it's doing** — progress, intermediate output, what it touched
 - **Steer it** — give feedback, interrupt, queue the next task
 - **Manage it** — edit its instructions, skills, memory, scheduled jobs, connected accounts
-- **Inspect its work** — review drafts, audit trails, rollbacks
-- **Share its output** — dashboards, reports, forms, links
+- **Inspect its work** — review drafts, audit history, roll back mistakes
+- **Share its output** — dashboards, reports, forms, links to send to teammates
 
-At minimum, "a UI for the agent" is an observability + management interface. At maximum, it's a full SaaS app with an agent embedded in it. Both ends of that spectrum are agent-native — see [Pure-Agent Apps](/docs/pure-agent-apps) for the minimal end and [Cloneable SaaS](/docs/cloneable-saas) for the maximal end.
+At minimum, "a UI for the agent" is an observability and management dashboard. At maximum, it's a full SaaS app with the agent embedded as a co-pilot. Both ends count as agent-native — see [Pure-Agent Apps](/docs/pure-agent-apps) for the minimal end and [Cloneable SaaS](/docs/cloneable-saas) for the maximal end.
 
 ## Why every app benefits from an agent {#why-every-app-benefits-from-an-agent}
 
-The flip side is equally important. Existing SaaS products hit a wall: 80% of what you need, and 20% you can't change. Bolting a sidebar chat onto a SaaS app rarely works because the chat can't actually _do_ the things the UI can.
+The flip side is just as important. Existing SaaS products keep hitting the same wall: 80% of what you need works great, and 20% you just can't change. Adding a chat sidebar rarely fixes that — the chat usually can't actually _do_ the things the UI can.
 
-Agent-native flips that. Because every action in the app is defined once and exposed as both a UI handler and an agent tool, the agent can do everything the buttons can — and a lot more — without a separate "AI world" to maintain. Natural language becomes a first-class input alongside clicks.
+Agent-native flips that. Because every action in the app is defined once and exposed as both a button and an agent tool, the agent can do everything the buttons can — and more — without a separate "AI world" to maintain. Natural language becomes a first-class input alongside clicks.
 
 The argument isn't "agents replace UI." It's "**agents belong inside applications, with a UI on top, as equal partners**." Neither can stand alone.
 
@@ -114,22 +79,22 @@ This is the defining principle.
 >
 > **From the agent** — natural language, other agents via A2A, Slack, Telegram. The agent writes to the database; the UI updates automatically.
 
-When the agent creates a draft email, it appears in the UI. When the user clicks "Send," the agent knows it was sent. There's no separate "agent world" and "UI world" — it's one system. See [Key Concepts](/docs/key-concepts) for the architecture that makes this work.
+When the agent creates a draft email, it appears in the UI. When you click "Send," the agent knows it was sent. There's no separate "agent world" and "UI world" — it's one system. See [Key Concepts](/docs/key-concepts) for the architecture that makes this work.
 
-## Customization that's usually reserved for Claude Code {#workspace-customization}
+## Customization usually reserved for power tools {#workspace-customization}
 
-The reason tools like Claude Code and Codex are so powerful isn't the model — it's the **customization layer**: per-project instructions, skills, memory files, sub-agents, connected MCP servers. You can shape the agent to your codebase, your preferences, your team.
+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 ships the same customization layer as a first-class part of every app — the **workspace**. Each app includes:
+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:
 
-- `AGENTS.md` — team-wide rules (shared)
-- `learnings.md` — per-user memory the agent writes to automatically (personal)
-- `skills/` — reusable how-to guides (`/slash` commands)
-- `agents/` — custom sub-agent profiles (invoked with `@mentions`)
-- `jobs/` — scheduled tasks that run on a cron
-- MCP servers — local _or_ remote, per-user or per-org
+- Edit team-wide rules everyone's agent reads
+- Let the agent remember preferences automatically as you correct it
+- Write reusable how-to guides as `/slash` commands
+- Keep custom sub-agents for specific tasks (invoked with `@mentions`)
+- 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 **SQL-backed, not filesystem-backed.** There's no dev-box to spin up, no container per user, no files to sync. Every user gets their own full workspace — personal memory, personal MCP servers, personal skills — for essentially free, because it's all rows in a database. That makes this model viable for real SaaS: multi-tenant, deployable to any serverless or edge host, with Claude-Code-level flexibility per user.
+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.
 
 See [Workspace](/docs/workspace) for the full concept.
 
@@ -142,39 +107,22 @@ See [Workspace](/docs/workspace) for the full concept.
 | **Claude Code / Codex for SaaS**       | Great for devs on their own machines. Doesn't translate to multi-tenant SaaS — one codebase per user on a dev-box doesn't scale.       |
 | **Agent-native apps**                  | The agent is a first-class citizen. It shares the same database, the same state, and can do everything the UI can do — and vice versa. |
 
-## What is agent-native development? {#what-is-agent-native-development}
-
-Agent-native development means building with agents first. Projects are structured so any AI coding tool — Claude Code, Codex, Cursor, Windsurf, Builder.io — reads the same instructions and follows the same patterns.
-
-The payoff: the agent tends to do _better_ than a human developer because you can encode rules like "when you add a feature, also add a skill for it" — the kind of thing humans skip when they're tired or rushed.
-
-## Agents as first-class developers {#agents-as-first-class-developers}
-
-In an agent-native project:
-
-- **AGENTS.md** gives every AI coding tool the same instructions — Claude Code, Cursor, Windsurf, and others all read the same file
-- **Skills** teach the agent patterns for specific tasks — adding features, storing data, wiring real-time sync
-- **Agent PR reviewers** validate the four-area checklist, that skills were updated, and that code matches conventions
-- **Auto-maintained docs and tests** — agents are instructed to keep docs current and tests passing
-
-This is the shift from desktop-first to mobile-first applied to development. Mobile-first didn't mean "no desktop" — it meant designing for mobile constraints first. Agent-native development means designing for agent workflows first, then ensuring humans work effectively too.
-
 ## Whole-team development {#whole-team-development}
 
-Agent-native development isn't just for developers:
+Agent-native isn't just for developers. Because the agent can edit the app's own code, evolving an app stops being a developer-only activity:
 
-- **Designers** update designs directly in the code through the agent
-- **Product managers** update functionalities and requirements
-- **QA** tests and prompts for fixes
+- **Designers** update designs directly in the running app through the agent
+- **Product managers** add functionality and update flows by describing them
+- **QA** tests the app and asks the agent to fix what's broken
 - **Anyone on the team** contributes through natural language
 
-The vision: reduce handoffs, enable one-person-to-full-team productivity.
+The vision: fewer handoffs, one person doing the work of a small team.
 
 ## Fork and customize {#fork-and-customize}
 
 Agent-native apps follow a fork-and-customize model. You start from a **cloneable SaaS** template — Mail, Calendar, Analytics, Slides, Clips, Forms, Dispatch — and make it yours:
 
-1. Pick a template on [agent-native.com](/templates)
+1. Pick a template on [agent-native.com/templates](/templates)
 2. Use it immediately as a hosted app (e.g. mail.agent-native.com)
 3. Fork it when you want to customize — "connect our Stripe account," "add a cohort chart"
 4. The agent modifies the code to match your needs
@@ -184,14 +132,50 @@ Because it's _your_ app, not shared infrastructure, the agent can safely evolve
 
 ## Composable agents {#composable-agents}
 
-Agent-native apps talk to each other over the [A2A protocol](/docs/a2a-protocol). From the mail app, you can tag the analytics agent to query data and include the results in a draft email. Agents discover what other agents are available, call them over the protocol, and show results in the UI.
+Agent-native apps can talk to each other. From inside the mail app, you can tag the analytics agent to query data and include the result in a draft email. The agents discover what other agents are available, hand off work between each other, and surface the results in the UI you're already in.
+
+This is powered by [A2A](/docs/a2a-protocol) and [MCP](/docs/mcp-protocol) under the hood — same definition, multiple surfaces — but as a user, all you have to know is "I can ask any of my apps for help with anything any of them can do."
+
+## What does this look like in code? {#what-does-it-look-like-in-code}
+
+If you're building or extending an agent-native app, here's the central pattern: every operation in the app is an **action** — defined once, available to both the agent and the UI.
+
+```ts
+// actions/reply-to-email.ts
+import { defineAction } from "@agent-native/core";
+import { z } from "zod";
+
+export default defineAction({
+  description: "Reply to an email thread",
+  schema: z.object({ emailId: z.string(), body: z.string() }),
+  run: async ({ emailId, body }) => {
+    await db.replies.insert({ emailId, body });
+  },
+});
+```
+
+```tsx
+// In any React component — same action, called from a button
+const { mutate } = useActionMutation("replyToEmail");
+
+<Button onClick={() => mutate({ emailId, body: "Thanks!" })}>
+  Send Reply
+</Button>;
+```
+
+```tsx
+// And the agent panel mounted anywhere in your app
+import { AgentSidebar } from "@agent-native/core/client";
+
+<AgentSidebar />;
+```
 
-Every action you define is also a tool exposed over A2A _and_ as an MCP server, so external tools like Claude Desktop can drive your app directly. Same definition, four surfaces.
+One action, four surfaces: the agent calls it as a tool, the UI calls it as a typesafe mutation, external agents reach it over [A2A](/docs/a2a-protocol), and tools like Claude Desktop talk to it as an [MCP server](/docs/mcp-protocol). See [Actions](/docs/actions) for the full reference.
 
-## What's next
+## What's next {#whats-next}
 
+- [**Getting Started**](/docs) — pick a template and run it
 - [**Key Concepts**](/docs/key-concepts) — the architecture: SQL, actions, polling sync, context awareness, portability
 - [**Cloneable SaaS**](/docs/cloneable-saas) — templates as complete products you own
 - [**Workspace**](/docs/workspace) — the per-user customization layer (skills, memory, instructions, MCP)
 - [**Drop-in Agent**](/docs/drop-in-agent) — mount `<AgentPanel>` into any React app
-- [**Getting Started**](/docs) — scaffold your first app

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.7.13",
+  "version": "0.7.14",
   "type": "module",
   "description": "Framework for agent-native application development — where AI agents and UI share state via files",
   "license": "MIT",
@@ -26,6 +26,7 @@
     "./server/ssr-handler": "./dist/server/ssr-handler.js",
     "./server/agent-discovery": "./dist/server/agent-discovery.js",
     "./server/request-context": "./dist/server/request-context.js",
+    "./server/design-token-utils": "./dist/server/design-token-utils.js",
     "./db": "./dist/db/index.js",
     "./db/schema": "./dist/db/schema.js",
     "./db/drizzle-config": "./dist/db/drizzle-config.js",
@@ -54,6 +55,7 @@
     "./sharing/actions/list-resource-shares": "./dist/sharing/actions/list-resource-shares.js",
     "./sharing/actions/set-resource-visibility": "./dist/sharing/actions/set-resource-visibility.js",
     "./client/sharing": "./dist/client/sharing/index.js",
+    "./client/tools": "./dist/client/tools/index.js",
     "./client/transcription/use-live-transcription": "./dist/client/transcription/use-live-transcription.js",
     "./client/transcription/BuilderTranscriptionCta": "./dist/client/transcription/BuilderTranscriptionCta.js",
     "./transcription/builder": "./dist/transcription/builder-transcription.js",
@@ -123,6 +125,7 @@
     "drizzle-orm": "^0.45.2",
     "h3": "^2.0.1-rc.20",
     "isbot": "^5",
+    "jiti": "^2.6.1",
     "jose": "^6.2.2",
     "minimatch": "^10.0.0",
     "nanoid": "^5.1.9",

package/src/templates/default/app/root.tsx

@@ -5,8 +5,10 @@ import {
   Scripts,
   ScrollRestoration,
   isRouteErrorResponse,
+  Link,
+  useRouteError,
 } from "react-router";
-import { useState } from "react";
+import { useEffect, useState } from "react";
 import {
   QueryClient,
   QueryClientProvider,
@@ -81,17 +83,41 @@ export default function Root() {
   );
 }
 
-export function ErrorBoundary({ error }: { error: unknown }) {
-  let message = "Oops!";
+function useApplyThemeClass() {
+  useEffect(() => {
+    const root = document.documentElement;
+    if (root.classList.contains("dark") || root.classList.contains("light"))
+      return;
+    try {
+      const stored = localStorage.getItem("theme");
+      if (stored === "dark") {
+        root.classList.add("dark");
+      } else if (stored === "light") {
+        root.classList.add("light");
+      } else if (window.matchMedia("(prefers-color-scheme: dark)").matches) {
+        root.classList.add("dark");
+      }
+    } catch {}
+  }, []);
+}
+
+export function ErrorBoundary() {
+  useApplyThemeClass();
+  const error = useRouteError();
+  let status: number | null = null;
+  let title = "Something went wrong";
   let details = "An unexpected error occurred.";
   let stack: string | undefined;
 
   if (isRouteErrorResponse(error)) {
-    message = error.status === 404 ? "404" : "Error";
-    details =
-      error.status === 404
-        ? "The requested page could not be found."
-        : error.statusText || details;
+    status = error.status;
+    if (error.status === 404) {
+      title = "Page not found";
+      details = "This page doesn't exist. It may have been moved or deleted.";
+    } else {
+      title = `${error.status} Error`;
+      details = error.statusText || details;
+    }
   } else if (
     typeof process !== "undefined" &&
     process.env.NODE_ENV !== "production" &&
@@ -102,12 +128,23 @@ export function ErrorBoundary({ error }: { error: unknown }) {
   }
 
   return (
-    <main className="flex items-center justify-center min-h-screen p-4">
-      <div className="text-center">
-        <h1 className="text-4xl font-bold mb-2">{message}</h1>
-        <p className="text-muted-foreground">{details}</p>
+    <main className="flex items-center justify-center min-h-screen p-4 bg-background text-foreground">
+      <div className="flex flex-col items-center text-center max-w-md">
+        {status && (
+          <span className="text-7xl font-bold tracking-tight text-muted-foreground/40">
+            {status}
+          </span>
+        )}
+        <h1 className="mt-3 text-2xl font-semibold">{title}</h1>
+        <p className="mt-2 text-muted-foreground text-sm">{details}</p>
+        <Link
+          to="/"
+          className="mt-6 inline-flex items-center gap-1.5 rounded-md bg-primary px-4 py-2 text-sm font-medium text-primary-foreground shadow-sm hover:bg-primary/90 cursor-pointer"
+        >
+          Go home
+        </Link>
         {stack && (
-          <pre className="mt-4 text-left text-xs overflow-auto max-w-lg mx-auto p-4 bg-muted rounded">
+          <pre className="mt-6 w-full text-left text-xs overflow-auto p-4 bg-muted rounded">
             <code>{stack}</code>
           </pre>
         )}

package/src/templates/default/react-router.config.ts

@@ -3,4 +3,7 @@ import type { Config } from "@react-router/dev/config";
 export default {
   appDirectory: "app",
   ssr: true,
+  future: {
+    v8_viteEnvironmentApi: true,
+  },
 } satisfies Config;

package/docs/content/integrations.md

@@ -1,198 +0,0 @@
----
-title: "Integrations"
-description: "Connect your agent to Slack, Telegram, WhatsApp, and other messaging platforms."
----
-
-# Integrations
-
-Connect your agent to messaging platforms so you can chat with it from Slack, Telegram, WhatsApp, and more. Same agent, same tools, same thread history.
-
-## Overview {#overview}
-
-Messaging integrations let users talk to their agent from the platforms they already use. Instead of opening the web UI, you send a message in Slack or Telegram and the agent responds right there. It has access to the same actions, the same database, and the same conversation history as the web chat.
-
-Each integration works through webhooks. The messaging platform sends incoming messages to your app, the agent processes them, and the response is posted back. No polling, no long-lived connections — just standard HTTP webhooks.
-
-## How it works {#how-it-works}
-
-The flow for every platform follows the same pattern:
-
-1. A user sends a message on the external platform (Slack, Telegram, etc.)
-2. The platform delivers the message to your app via a webhook at `/_agent-native/integrations/<platform>/webhook`
-3. The integrations plugin validates the request, extracts the message text and thread context, and maps it to an internal conversation thread
-4. The agent processes the message in the background using the same pipeline as the web chat — same system prompt, same actions, same tools
-5. The response is posted back to the external platform in the same thread
-
-`User (Slack/Telegram/WhatsApp)` → `Webhook` → `Agent Processing` → `Response posted back`
-
-## Setup {#setup}
-
-The integrations plugin auto-mounts when no custom version exists in your template. To customize it, create a plugin file:
-
-```ts
-// server/plugins/integrations.ts
-import { createIntegrationsPlugin } from "@agent-native/core/server";
-import { scriptRegistry } from "../../agent.config";
-
-export default createIntegrationsPlugin({
-  actions: scriptRegistry,
-  systemPrompt: "You are a helpful assistant...",
-});
-```
-
-The plugin registers webhook routes for each enabled platform under `/_agent-native/integrations/`. Which platforms are active depends on which environment variables are configured.
-
-## Slack {#slack}
-
-### 1. Create a Slack app
-
-Go to [api.slack.com/apps](https://api.slack.com/apps) and create a new app. Under **OAuth & Permissions**, add the following bot token scopes:
-
-- `chat:write` — send messages
-- `app_mentions:read` — receive @-mentions (optional)
-
-### 2. Enable Event Subscriptions
-
-Under **Event Subscriptions**, set the Request URL to:
-
-```text
-https://your-app.example.com/_agent-native/integrations/slack/webhook
-```
-
-Subscribe to the `message.im` bot event (and optionally `app_mention` for channel mentions).
-
-### 3. Set environment variables
-
-```bash
-SLACK_BOT_TOKEN=xoxb-your-bot-token
-SLACK_SIGNING_SECRET=your-signing-secret
-```
-
-The bot token is found under **OAuth & Permissions** after installing the app to your workspace. The signing secret is under **Basic Information**.
-
-## Telegram {#telegram}
-
-### 1. Create a bot
-
-Message [@BotFather](https://t.me/BotFather) on Telegram and use the `/newbot` command. You will receive a bot token.
-
-### 2. Set environment variables
-
-```bash
-TELEGRAM_BOT_TOKEN=your-bot-token
-```
-
-### 3. Register the webhook
-
-After deploying your app, call the setup endpoint to register the webhook with Telegram:
-
-```text
-// The integrations plugin exposes a setup endpoint
-POST /_agent-native/integrations/telegram/setup
-
-// This calls Telegram's setWebhook API pointing to:
-// https://your-app.example.com/_agent-native/integrations/telegram/webhook
-```
-
-You can also register the webhook manually using the Telegram Bot API if you prefer.
-
-## WhatsApp {#whatsapp}
-
-### 1. Set up the WhatsApp Cloud API
-
-Go to the [Meta Developer Portal](https://developers.facebook.com/), create an app, and enable the WhatsApp product. Configure a phone number for your business.
-
-### 2. Set environment variables
-
-```bash
-WHATSAPP_ACCESS_TOKEN=your-access-token
-WHATSAPP_VERIFY_TOKEN=your-verify-token
-WHATSAPP_PHONE_NUMBER_ID=your-phone-number-id
-```
-
-The verify token is a string you choose — Meta uses it during webhook verification. The access token and phone number ID come from the Meta Developer Portal.
-
-### 3. Configure the webhook
-
-In the Meta Developer Portal, set the webhook URL to:
-
-```text
-https://your-app.example.com/_agent-native/integrations/whatsapp/webhook
-```
-
-Subscribe to the `messages` webhook field.
-
-## Configuration {#configuration}
-
-Integrations can be managed from the settings UI in the sidebar. Each platform shows its connection status and webhook URL. You can enable/disable individual integrations without removing environment variables.
-
-The webhook URLs follow a consistent pattern:
-
-```text
-/_agent-native/integrations/<platform>/webhook
-
-# Examples:
-/_agent-native/integrations/slack/webhook
-/_agent-native/integrations/telegram/webhook
-/_agent-native/integrations/whatsapp/webhook
-```
-
-## Thread continuity {#thread-continuity}
-
-Conversations from external platforms are mapped to internal threads. Each Slack DM, Telegram chat, or WhatsApp conversation becomes a persistent thread in the agent-native database. This means:
-
-- The agent retains context across messages in the same external conversation
-- External conversations appear in the web UI alongside web-originated threads, tagged with their source platform
-- You can continue a conversation that started in Slack from the web UI, or vice versa
-
-## Custom adapters {#custom-adapters}
-
-To add support for a new messaging platform, implement the `PlatformAdapter` interface:
-
-```ts
-import type { PlatformAdapter } from "@agent-native/core/server";
-
-const myAdapter: PlatformAdapter = {
-  platform: "discord",
-
-  // Verify the incoming webhook request is authentic
-  verifyRequest(request: Request): Promise<boolean> {
-    // Validate signature headers
-  },
-
-  // Extract the message text and thread context from the webhook payload
-  parseMessage(body: unknown): Promise<{
-    text: string;
-    threadId: string;
-    senderId: string;
-    metadata?: Record<string, unknown>;
-  }> {
-    // Parse platform-specific payload
-  },
-
-  // Send the agent's response back to the platform
-  sendResponse(threadId: string, text: string): Promise<void> {
-    // Call the platform's API to post the message
-  },
-};
-```
-
-Register your adapter in the integrations plugin config:
-
-```ts
-export default createIntegrationsPlugin({
-  actions: scriptRegistry,
-  systemPrompt: "You are a helpful assistant...",
-  adapters: [myAdapter],
-});
-```
-
-## Security {#security}
-
-Every incoming webhook is verified before processing:
-
-- **Slack** — HMAC-SHA256 signature verification using `SLACK_SIGNING_SECRET`. The `X-Slack-Signature` header is checked against the request body.
-- **Telegram** — requests are validated by checking the secret token set during webhook registration via the Telegram Bot API.
-- **WhatsApp** — Meta's webhook verification challenge (using `WHATSAPP_VERIFY_TOKEN`) and payload signature validation.
-
-All platform credentials (tokens, secrets) are stored as environment variables and never persisted in the database or source code. Use the settings UI or your deployment platform's env var management to configure them.