@softr/sdk 0.0.91-alpha.1 → 0.0.92-emailotc.0

package/skills/softr-sdk/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: core
   library: softr-sdk
-  library_version: 0.0.91-alpha.1
+  library_version: 0.0.91
 ---
 
 # Softr SDK core
@@ -52,7 +52,6 @@ Each sub-skill stands alone for its task and repeats the boundary above, so most
 | Ask an AI model: a summary, an extraction from a document, a classification, a draft, a chat | [ai/SKILL.md](./ai/SKILL.md) |
 | Call a connected third-party API (Slack, Stripe, Gmail, …), or an AI model on the user's own provider account | [integrations/SKILL.md](./integrations/SKILL.md) |
 | Open the app to AI assistants over MCP | [mcp/SKILL.md](./mcp/SKILL.md) |
-| Let visitors chat with a Softr agent | [agent-chat/SKILL.md](./agent-chat/SKILL.md) |
 | Let visitors install the app on their home screen | [pwa/SKILL.md](./pwa/SKILL.md) |
 | Show a date, a time or a number | [formatting/SKILL.md](./formatting/SKILL.md) |
 
@@ -95,9 +94,6 @@ Running a model on the user's OWN provider account, because they chose that for
 Opening the app to an AI assistant over MCP?
   load softr-sdk/mcp
 
-Adding a chat with one of the app's Softr agents, or a Connect button for the visitor's account it needs?
-  load softr-sdk/agent-chat
-
 Adding an install button, or making the app installable?
   load softr-sdk/pwa
 

package/skills/softr-sdk/ai/SKILL.md

@@ -13,7 +13,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.79-alpha.0
+  library_version: 0.0.91
 ---
 
 **Boundary.** `ai` lives on `@softr/sdk/server` and runs only inside a `createServerFn` handler — importing it into a component fails the build. `defineAiAction` and every type come from `@softr/sdk` and can be imported anywhere.

package/skills/softr-sdk/auth/SKILL.md

@@ -3,13 +3,13 @@ name: auth
 description: >-
   Sign a visitor in, out or up from a server function with auth from
   @softr/sdk/server: password, code, Google and magic link, sign-up and its
-  confirmation, the authenticator-app steps, password reset links,
+  confirmation, the emailed-code and authenticator-app steps, password reset links,
   updateProfile, and getAuthSettings and useAuthSettings for the methods the app
   enables. Covers the Result shape, its error codes, and toReturnPath.
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91-alpha.1
+  library_version: 0.0.91
 ---
 
 **Boundary.** `auth` lives on `@softr/sdk/server` and runs only inside a `createServerFn` handler — importing it into a component fails the build.
@@ -55,6 +55,13 @@ Signing out:
 | --- | --- |
 | `auth.signOut()` | Ends every session that visitor has in this app, on every device |
 
+Finishing a sign-in that wants a code from the visitor's inbox:
+
+| Call | Does |
+| --- | --- |
+| `auth.verifyEmailCode({ code })` | Answers it with the code that was emailed |
+| `auth.resendEmailCode()` | Emails that code again |
+
 Finishing a sign-in that wants an authenticator app:
 
 | Call | Does |
@@ -197,6 +204,8 @@ Those calls take only what the visitor typed. The sign-in they finish is the one
 
 An app with no authenticator app configured never answers `authenticatorRequired`. The type still has both arms either way, so `result.data.user` does not exist until you have narrowed on `status`.
 
+`signIn` has a third answer, `{ status: 'emailCodeRequired' }`, for an app that asks a password sign-in for a code from the visitor's inbox as well. The code is already on its way. Show a code field as the next step and finish with `auth.verifyEmailCode({ code })`, see [Finishing a sign-in that needs an emailed code](#finishing-a-sign-in-that-needs-an-emailed-code). That call answers like `signIn` does, so an app that also wants an authenticator app goes on to that step after it.
+
 ## Landing after sign-in
 
 A guard that turns a signed-out visitor away sends them to the page `softr.json` names for that, usually the login page. The page they wanted rides along in the search param named for the login page. `toReturnPath` from `@softr/sdk` reads it back:
@@ -255,10 +264,13 @@ if (answer.message !== null) return setMessage(answer.message)
 if (answer.outcome.status === 'authenticatorRequired') {
   return setStep({ name: 'secondFactor', opensOn: answer.outcome.step })
 }
+if (answer.outcome.status === 'emailCodeRequired') {
+  return setStep({ name: 'emailCode' })
+}
 await navigate({ href: target })
 ```
 
-Three exits: a message for the form to render, the second-factor step, the return target.
+Four exits: a message for the form to render, the emailed-code step, the authenticator step, the return target.
 
 A server function that throws `redirect` needs the hook. Call the imported function directly and the throw never reaches the router, so a successful sign-in leaves the visitor on the form.
 
@@ -385,6 +397,22 @@ The UI has to carry email into step two, plus the name if step one collected one
 
 `password` is what the account is created with. Leave it out only for an app that signs people in with an emailed code. An app that expects a password rejects a sign-up without one, and an app that does not expect one rejects a sign-up that sends it.
 
+### Finishing a sign-in that needs an emailed code
+
+After `signIn` answers `emailCodeRequired`, the visitor owes the code that was just emailed to them:
+
+```ts
+// invalidCode for a wrong or expired code, otherwise the same two-armed result as signIn.
+const result = await auth.verifyEmailCode({ code })
+
+// For a "Resend code" link.
+const sent = await auth.resendEmailCode()
+```
+
+Send `authenticatorRequired` on to the authenticator step, never into the app.
+
+Asking for a resend too soon sends nothing and still succeeds. It answers `notAuthenticated` once the sign-in has run out of time, and the visitor then signs in again from the start.
+
 ### Finishing a sign-in that needs an authenticator app
 
 On `step: 'verify'` the visitor already has an app, and owes a code from it:

package/skills/softr-sdk/charts-and-metrics/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91-alpha.1
+  library_version: 0.0.91
 ---
 
 **Boundary.** `ds` lives on `@softr/sdk/server` and runs only inside a `createServerFn` handler or a server-side route hook — importing it into a component fails the build. `defineQuery` and every type come from `@softr/sdk` and can be imported anywhere.

package/skills/softr-sdk/current-user/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91-alpha.1
+  library_version: 0.0.91
 ---
 
 # The current user
@@ -56,9 +56,9 @@ It returns `User | null` and never suspends or fetches. It selects off root rout
 ```tsx
 export const Route = createFileRoute('/_app/invoices')({
   beforeLoad: guardRoute(pageSettings),
-  loader: (opts) => {
+  loader: async (opts) => {
     assertRouteAccess(pageSettings, opts)
-    return fetchInvoicesFor({ data: { userId: opts.context.user.id } })
+    return { name: opts.context.user.fullName, invoices: await getMyInvoices() }
   },
   head: pageHead(pageSettings),
 })
@@ -66,6 +66,8 @@ export const Route = createFileRoute('/_app/invoices')({
 
 A `guardRoute` in `beforeLoad` guarantees a visitor at runtime, but it does not change what the compiler sees. `context.user` is still `User | null` in the loader. `assertRouteAccess(pageSettings, opts)` at the top of the loader narrows it there, so prefer that over `!`. Take `opts` whole: a destructured `context` does not narrow. See [routes-and-visibility](../routes-and-visibility/SKILL.md).
 
+Never pass the visitor's id from a loader into a server function. The loader also runs in the browser, so the id arrives as an argument anyone can set. `getMyInvoices` below reads the visitor from its own `context`.
+
 ### In a server function: `context`
 
 ```ts

package/skills/softr-sdk/file-uploads/SKILL.md

@@ -7,7 +7,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91-alpha.1
+  library_version: 0.0.91
 ---
 
 **Boundary.** `upload` lives on `@softr/sdk/server` and runs inside server functions. `useFileUpload` and `FileItem` live on `@softr/sdk` and run in components. `FileAttachment` comes from `@softr/sdk` and can be imported anywhere.

package/skills/softr-sdk/formatting/SKILL.md

@@ -8,7 +8,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91-alpha.1
+  library_version: 0.0.91
 ---
 
 # Dates, times and numbers

package/skills/softr-sdk/integrations/SKILL.md

@@ -7,21 +7,21 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91-alpha.1
+  library_version: 0.0.91
 ---
 
 **Boundary.** `integration` lives on `@softr/sdk/server` and runs only inside a `createServerFn` handler — importing it into a component fails the build. `defineIntegration` and every type come from `@softr/sdk` and can be imported anywhere.
 
 # Integrations
 
-`integration.createFetcher` calls a third-party API through Softr's authenticated proxy. It handles authorization automatically — you never set API keys or auth headers yourself.
+`integration.createFetcher` calls a third-party API through Softr's authenticated proxy. It adds the connected account's credentials automatically — you never set API keys or auth headers yourself. **Every call acts as that one account, whoever the visitor is**, so take what a call reaches, such as a customer or a channel, from the session or a record the server read, never from the arguments the browser sends.
 
 ## Setup
 
 ```ts
 import { createServerFn } from '@tanstack/react-start'
 import { defineIntegration } from '@softr/sdk'
-import { integration } from '@softr/sdk/server'
+import { auth, integration } from '@softr/sdk/server'
 ```
 
 ## Reading connected integrations from the prompt
@@ -77,7 +77,7 @@ const getCalendarEvents = createServerFn().handler(async () => {
 })
 ```
 
-For a dynamic path segment, pass `params` matching each `{placeholder}` token:
+For a dynamic path segment, pass `params` matching each `{placeholder}` token. Here the customer comes from the visitor's own Users row, which `auth.currentUserRow` finds through `usersQuery`, the app's `defineQuery` on the Users table:
 
 ```ts
 const getStripeCustomer = defineIntegration({
@@ -89,10 +89,12 @@ const getStripeCustomer = defineIntegration({
 })
 
 const fetchCustomer = createServerFn({ method: 'GET' })
-  .validator((data: { customerId: string }) => data)
-  .handler(async ({ data }) => {
+  .handler(async ({ context }) => {
+    const me = await auth.currentUserRow(context.user, usersQuery, 'email')
+    const customerId = me?.fields.stripeCustomerId
+    if (!customerId) throw new Error('No Stripe customer for this visitor')
     const stripe = integration.createFetcher(getStripeCustomer)
-    const res = await stripe({ params: { id: data.customerId } })
+    const res = await stripe({ params: { id: customerId } })
     if (!res.ok) throw new Error(`Stripe error: ${res.status} ${await res.text()}`)
     return res.json()
   })
@@ -110,12 +112,12 @@ const postSlackMessage = defineIntegration({
 })
 
 const sendSlackMessage = createServerFn({ method: 'POST' })
-  .validator((data: { channel: string; text: string }) => data)
+  .validator((data: { text: string }) => data)
   .handler(async ({ data }) => {
     const slack = integration.createFetcher(postSlackMessage)
     const res = await slack({
       headers: { 'Content-Type': 'application/json' },
-      body: JSON.stringify({ channel: data.channel, text: data.text }),
+      body: JSON.stringify({ channel: '#sales', text: data.text }),
     })
     if (!res.ok) throw new Error(`Slack error: ${res.status} ${await res.text()}`)
     return res.json()

package/skills/softr-sdk/mcp/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91-alpha.1
+  library_version: 0.0.91
 ---
 
 **Boundary.** `softrMcpMiddleware` lives on `@softr/sdk` and is registered once, in `src/start.ts`. The actions you hand it are the same `defineQuery` / `defineMutation` values the app's own pages use — declared wherever they already live, not duplicated for MCP.
@@ -53,25 +53,10 @@ The list is the whole tool surface. Write it out:
 
 - An action you leave out is invisible to the assistant, even where the app's pages use it freely.
 - An action you list still obeys its own `permissions`. Listing it does not widen who may run it — the assistant runs as whoever signed in, with that user's groups.
-- The assistant calls the action directly and skips server functions, so a row filter written in one does not apply. A listed read returns every row the user's data restrictions allow, and a listed update or delete takes any id that passes them. On a table whose rows belong to people, list an action only once a data restriction scopes the table to the user's own rows.
-- A create on a table whose rows belong to a person gets its owner from `owner`, never from the assistant. See below.
 - Two actions with the same `id` throw at startup. So does anything that is not a `defineQuery` or `defineMutation` value.
 
 Reads first. Add a write only when the user asked for one, and name it back to them.
 
-## The owner of a person's record
-
-The assistant knows the caller's login, not their row in the people table. Left to fill an owner link, it writes the login id, which shows as a stray name, or anyone's row it likes. `owner` takes the field out of the tool and fills it with the caller's own row, found the way `auth.currentUserRow` finds it:
-
-```ts
-softrMcpMiddleware({
-  actions: [listRequests, requestTimeOff],
-  owner: { users: usersQuery, email: 'email', fields: { requestTimeOff: 'employee' } },
-})
-```
-
-`fields` maps each create or update action id to its owner link. A caller with no row in the people table is refused, and nothing is created. On an update the field is only taken out, so nobody moves a record to someone else.
-
 ## The login round trip
 
 Connecting starts with an approval page the app serves. Most people hit it signed out, and that page cannot sign anyone in. It sends them to the login page named in `softr.json` (`auth.routes.login.path`), with the approval page in the search param named there (`auth.routes.login.redirectParam`).

package/skills/softr-sdk/pwa/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91-alpha.1
+  library_version: 0.0.91
 ---
 
 # Installing the app

package/skills/softr-sdk/record-mutations/SKILL.md

@@ -8,7 +8,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91-alpha.1
+  library_version: 0.0.91
 ---
 
 **Boundary.** `ds` lives on `@softr/sdk/server` and runs only inside a `createServerFn` handler — importing it into a component fails the build. `defineMutation` and every type come from `@softr/sdk` and can be imported anywhere.

package/skills/softr-sdk/record-queries/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91-alpha.1
+  library_version: 0.0.91
 ---
 
 **Boundary.** `ds` lives on `@softr/sdk/server` and runs only inside a `createServerFn` handler or a server-side route hook — importing it into a component fails the build. The same holds for any helper that calls `ds`: declare it inside the handler. A function at module level that calls `ds` keeps the server-only import in the browser bundle, and every page stops loading until it moves. `defineQuery` and every type come from `@softr/sdk` and can be imported anywhere.

package/skills/softr-sdk/record-queries/references/filters-and-sorting.md

@@ -127,6 +127,8 @@ Both take filters or nested groups:
 
 Nesting goes two levels, a group inside a group. A third level throws `Cannot nest filter groups more than three levels deep.` Flatten by distributing the outer condition rather than nesting further.
 
+**An `$or` with no members matches every row.** When its members come from a list that can be empty, return no rows for an empty list instead of reading the table.
+
 ## Sorting
 
 ```ts

package/skills/softr-sdk/region-visibility/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91-alpha.1
+  library_version: 0.0.91
 ---
 
 **Boundary.** `Audience` and `defineVisibility` come from `@softr/sdk` and work anywhere.

package/skills/softr-sdk/routes-and-visibility/SKILL.md

@@ -3,13 +3,13 @@ name: routes-and-visibility
 description: >-
   Add a route file and declare its settings: definePage with its visibility
   (LOGGED_IN_USERS, NON_LOGGED_IN_USERS and customGroups) and its title,
-  guardRoute or assertRouteAccess in beforeLoad, pageHead in head, isAuthorized
-  and checkAccess anywhere, rendering an access error, and the lint rules that
-  require the declaration.
+  guardRoute or assertRouteAccess in beforeLoad, pageHead in head,
+  isAuthorized and checkAccess anywhere, rendering an access error, and the
+  lint rules that require the declaration.
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91-alpha.1
+  library_version: 0.0.91
 ---
 
 **Boundary.** `definePage`, `pageHead`, the access functions and the error predicates come from `@softr/sdk` and work anywhere.
@@ -73,6 +73,8 @@ Everyone is both audiences, as in the first line above. A set names each audienc
 
 Take every id in `customGroups` from `docs/user-groups.md`, which lists each group the app has with its name and id. An id the app does not have is a type error.
 
+**`visibility` guards the page, not the server functions it calls.** A call can reach them without the page and with any arguments, so the queries and mutations behind a page carry its groups in their own `permissions` and reach only the rows the visitor's role allows.
+
 ## Core Patterns
 
 ### Guard a whole section with one layout route

package/skills/softr-sdk/workflows/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.91-alpha.1
+  library_version: 0.0.91
 ---
 
 **Boundary.** `workflow` lives on `@softr/sdk/server` and runs only inside a `createServerFn` handler — importing it into a component fails the build. `defineWorkflow` and every type come from `@softr/sdk` and can be imported anywhere.

package/dist/agent/agent-fns.d.ts

@@ -1,30 +0,0 @@
-import { z } from "zod";
-import * as _tanstack_react_start8 from "@tanstack/react-start";
-
-//#region src/agent/agent-fns.d.ts
-
-declare const agentSchema: z.ZodObject<{
-  id: z.ZodString;
-  title: z.ZodString;
-  avatar: z.ZodOptional<z.ZodNullable<z.ZodString>>;
-  thumbnail: z.ZodOptional<z.ZodNullable<z.ZodString>>;
-}, z.core.$strip>;
-/** An agent the visitor may chat with. */
-type Agent = z.infer<typeof agentSchema>;
-/**
- * The agents the visitor may chat with in this app. The builder attaches them
- * in Studio, and each one's visibility settings decide who sees it.
- */
-declare const listAgents: _tanstack_react_start8.OptionalFetcher<undefined, undefined, Promise<{
-  id: string;
-  title: string;
-  avatar?: string | null | undefined;
-  thumbnail?: string | null | undefined;
-}[]>>;
-/** One past chat with an agent. `title` is null until the agent names the chat. */
-type AgentChatSummary = {
-  id: string;
-  title: string | null;
-};
-//#endregion
-export { Agent, AgentChatSummary, listAgents };

package/dist/agent/agent-fns.js

@@ -1,215 +0,0 @@
-import { assert } from "../assertions.js";
-import { softrApiUrl } from "../softr-api.js";
-import { fetch } from "../fetch.js";
-import { sessionConfig } from "../auth/config.js";
-import { readSessionToken } from "../auth/session.js";
-import { describeFailure, refererHeader } from "../datasource/record.js";
-import { z } from "zod";
-import { createServerFn } from "@tanstack/react-start";
-import { getRequest } from "@tanstack/react-start/server";
-
-//#region src/agent/agent-fns.ts
-const AGENTS_PRODUCTION = "https://agents-api.softr.io";
-const PLATFORM_HOST = /^(platform-api|platform-preview-api|preview-api)(?=[.-])/;
-/**
-* Where the agents service is. It sits next to the platform API, so unless
-* `SOFTR_AGENTS_API_URL` says otherwise, it's the platform's host with
-* `agents-api` in place of the platform's name. Live and preview share one
-* agents service.
-*/
-function agentsApiUrl() {
-	const explicit = process.env.SOFTR_AGENTS_API_URL;
-	if (explicit) return explicit.replace(/\/+$/, "");
-	if (!process.env.SOFTR_PLATFORM_API_URL) return AGENTS_PRODUCTION;
-	const platform = new URL(softrApiUrl("SOFTR_PLATFORM_API_URL"));
-	assert(PLATFORM_HOST.test(platform.hostname), () => `can't tell the agents API from ${platform.origin}, set SOFTR_AGENTS_API_URL`);
-	platform.hostname = platform.hostname.replace(PLATFORM_HOST, "agents-api");
-	return platform.origin;
-}
-function agentsFetch(path, init = {}) {
-	const token = readSessionToken();
-	return fetch(`${agentsApiUrl()}/v1/agents/${path}`, {
-		method: init.method ?? "GET",
-		signal: init.signal,
-		headers: {
-			"Content-Type": "application/json",
-			...token ? { Authorization: `Bearer ${token}` } : {},
-			"Softr-Application-ID": sessionConfig().applicationId,
-			...refererHeader(),
-			...init.headers
-		},
-		body: init.body === void 0 ? void 0 : JSON.stringify(init.body)
-	});
-}
-const chatSchema = z.object({
-	agentId: z.string().min(1),
-	message: z.string(),
-	sessionId: z.string().nullable(),
-	timezone: z.string(),
-	pageName: z.string(),
-	pageUrl: z.string(),
-	record: z.object({
-		id: z.string(),
-		fields: z.record(z.string(), z.unknown())
-	}).nullable()
-});
-/**
-* Sends one message and streams the reply back as it comes, one JSON event per line.
-*
-* Takes FormData so the browser can call it with plain `fetch` and read the
-* stream itself. A failed call passes the agents service's status and message on.
-*/
-const agentChatFn = createServerFn({ method: "POST" }).validator((data) => {
-	const payload = data.get("payload");
-	assert(typeof payload === "string", "agent chat: payload is required");
-	return chatSchema.parse(JSON.parse(payload));
-}).handler(async ({ data }) => {
-	const upstream = await agentsFetch(`${encodeURIComponent(data.agentId)}/chat`, {
-		method: "POST",
-		signal: getRequest().signal,
-		headers: {
-			Accept: "application/x-ndjson",
-			"X-User-Timezone": data.timezone
-		},
-		body: {
-			message: data.message,
-			...data.sessionId ? { sessionId: data.sessionId } : {},
-			context: {
-				pageName: data.pageName,
-				pageUrl: data.pageUrl,
-				...data.record ? { currentRecord: { data: data.record } } : {}
-			}
-		}
-	});
-	return new Response(upstream.body, {
-		status: upstream.status,
-		headers: { "Content-Type": upstream.headers.get("Content-Type") ?? "application/x-ndjson" }
-	});
-});
-const agentSchema = z.object({
-	id: z.string(),
-	title: z.string(),
-	avatar: z.string().nullish(),
-	thumbnail: z.string().nullish()
-});
-/**
-* The agents the visitor may chat with in this app. The builder attaches them
-* in Studio, and each one's visibility settings decide who sees it.
-*/
-const listAgents = createServerFn({ method: "GET" }).handler(async () => {
-	const token = readSessionToken();
-	const res = await fetch(`${softrApiUrl("SOFTR_PLATFORM_API_URL")}/v1/vibe/applications/${sessionConfig().applicationId}/agents`, { headers: token ? { Authorization: `Bearer ${token}` } : {} });
-	if (!res.ok) throw new Error(`Loading agents failed: ${await describeFailure(res)}`);
-	return z.array(agentSchema).parse(await res.json());
-});
-const listAgentChatsFn = createServerFn({ method: "POST" }).validator(z.object({ agentId: z.string().min(1) })).handler(async ({ data }) => {
-	const res = await agentsFetch(`${encodeURIComponent(data.agentId)}/sessions`);
-	if (!res.ok) throw new Error(`Loading chats failed: ${await describeFailure(res)}`);
-	return z.array(z.object({
-		id: z.string(),
-		title: z.string().nullable()
-	})).parse(await res.json());
-});
-const historySchema = z.object({
-	messages: z.array(z.object({
-		id: z.string(),
-		role: z.enum(["USER", "ASSISTANT"]),
-		content: z.string(),
-		createdAt: z.number()
-	})),
-	toolCalls: z.array(z.object({
-		id: z.string(),
-		messageId: z.string(),
-		toolName: z.string(),
-		input: z.string(),
-		createdAt: z.number(),
-		metadata: z.object({
-			innerThought: z.string().nullish(),
-			durationMs: z.number().nullish(),
-			failed: z.boolean().nullish()
-		})
-	}))
-});
-const CHAT_GONE = [
-	401,
-	403,
-	404,
-	410
-];
-/** What a past chat holds, or `null` when it's gone or belongs to someone else. */
-const loadAgentChatFn = createServerFn({ method: "POST" }).validator(z.object({
-	agentId: z.string().min(1),
-	sessionId: z.string().min(1)
-})).handler(async ({ data }) => {
-	const res = await agentsFetch(`${encodeURIComponent(data.agentId)}/sessions/${encodeURIComponent(data.sessionId)}`);
-	if (CHAT_GONE.includes(res.status)) return null;
-	if (!res.ok) throw new Error(`Loading the chat failed: ${await describeFailure(res)}`);
-	return historySchema.parse(await res.json());
-});
-/** Saves the visitor's answer. `false` when the chat is gone, see `loadAgentChatFn`. */
-const decideAgentToolFn = createServerFn({ method: "POST" }).validator(z.object({
-	agentId: z.string().min(1),
-	sessionId: z.string().min(1),
-	toolCallId: z.string().min(1),
-	toolName: z.string().min(1),
-	decision: z.enum(["APPROVE", "REJECT"]),
-	scope: z.enum([
-		"ONCE",
-		"SESSION",
-		"USER"
-	])
-})).handler(async ({ data: { agentId,...decision } }) => {
-	const res = await agentsFetch(`${encodeURIComponent(agentId)}/tool-permission-decisions`, {
-		method: "POST",
-		body: decision
-	});
-	if (CHAT_GONE.includes(res.status)) return false;
-	if (!res.ok) throw new Error(`Saving the answer failed: ${await describeFailure(res)}`);
-	return true;
-});
-const connectionSchema = z.object({
-	integration: z.string().min(1),
-	requestId: z.string().min(1)
-});
-function connectionUrl({ integration, requestId }, step) {
-	const { applicationId } = sessionConfig();
-	const provider = encodeURIComponent(integration.toLowerCase());
-	return `${`${softrApiUrl("SOFTR_DATASOURCE_API_URL")}/v1/datasource/applications/${applicationId}`}/integrations/${provider}/oauth/${step}?${new URLSearchParams({ requestId })}`;
-}
-/** The sign-in page to open in the popup. */
-const startAgentConnectionFn = createServerFn({ method: "POST" }).validator(connectionSchema).handler(async ({ data }) => {
-	const token = readSessionToken();
-	const res = await fetch(connectionUrl(data, "register"), {
-		method: "POST",
-		headers: {
-			...token ? { Authorization: `Bearer ${token}` } : {},
-			...refererHeader()
-		}
-	});
-	if (!res.ok) throw new Error(`Starting the connection failed: ${await describeFailure(res)}`);
-	return z.object({ url: z.string() }).parse(await res.json()).url;
-});
-/** Waits a while for the visitor to finish signing in. `false` when they haven't yet. */
-const awaitAgentConnectionFn = createServerFn({ method: "POST" }).validator(connectionSchema).handler(async ({ data }) => {
-	const res = await fetch(connectionUrl(data, "register-result"), { signal: getRequest().signal });
-	if (res.status === 503) return false;
-	if (!res.ok) throw new Error(`Connecting failed: ${await describeFailure(res)}`);
-	return true;
-});
-/** Tells the agent the account is connected. `false` when the chat is gone, see `loadAgentChatFn`. */
-const finishAgentConnectionFn = createServerFn({ method: "POST" }).validator(z.object({
-	agentId: z.string().min(1),
-	sessionId: z.string().min(1),
-	toolCallId: z.string().min(1)
-})).handler(async ({ data: { agentId,...completion } }) => {
-	const res = await agentsFetch(`${encodeURIComponent(agentId)}/integration-auth-completions`, {
-		method: "POST",
-		body: completion
-	});
-	if (CHAT_GONE.includes(res.status)) return false;
-	if (!res.ok) throw new Error(`Finishing the connection failed: ${await describeFailure(res)}`);
-	return true;
-});
-
-//#endregion
-export { agentChatFn, awaitAgentConnectionFn, decideAgentToolFn, finishAgentConnectionFn, listAgentChatsFn, listAgents, loadAgentChatFn, startAgentConnectionFn };