@softr/sdk 0.0.89-alpha.2 → 0.0.89-alpha.4

package/dist/agent/use-agent-chat.d.ts

@@ -34,7 +34,10 @@ type AgentQuestion = {
   }>;
   multiSelect: boolean;
 };
-/** One piece of a message, in the order the agent produced it. */
+/**
+ * One piece of a message, in the order the agent produced it. A tool waiting for
+ * the visitor comes last, below the text that asks for it, until they answer.
+ */
 type AgentBlock = {
   type: "text";
   text: string;
@@ -74,7 +77,7 @@ type AgentChat = {
   openChat: (chatId: string) => void;
   /** The visitor's past chats with this agent. */
   listChats: () => Promise<AgentChatSummary[]>;
-  /** Lets a tool waiting for approval run, once, for this chat, or always for this visitor. */
+  /** Lets a tool waiting for approval run: once, for the rest of this chat, or for this agent from now on. */
   approve: (toolCallId: string, scope?: "ONCE" | "SESSION" | "USER") => void;
   reject: (toolCallId: string) => void;
   /** Opens the sign-in for a tool's `integration` in a popup. Call it from a click, or the browser blocks the popup. */

package/dist/agent/use-agent-chat.js

@@ -262,11 +262,11 @@ function useAgentChat(agentId, options = {}) {
 		reset
 	]);
 	return {
-		messages: live === null ? messages : [...messages, {
+		messages: (live === null ? messages : [...messages, {
 			id: "live",
 			role: "assistant",
 			blocks: live
-		}],
+		}]).map(waitingLast),
 		status,
 		loading,
 		error,
@@ -281,6 +281,15 @@ function useAgentChat(agentId, options = {}) {
 		connect
 	};
 }
+const waitsForVisitor = (b) => b.type === "tool" && (b.status === "awaiting-approval" || b.status === "awaiting-connection" || b.status === "connecting");
+function waitingLast(message) {
+	if (!message.blocks.some(waitsForVisitor)) return message;
+	const blocks = [...message.blocks.filter((b) => !waitsForVisitor(b)), ...message.blocks.filter(waitsForVisitor)];
+	return {
+		...message,
+		blocks
+	};
+}
 const CONNECT_TIMEOUT_MS = 5 * 6e4;
 const CONNECT_RETRY_MS = 3e3;
 function popupFeatures(width, height) {
@@ -449,18 +458,22 @@ function fromHistory(history) {
 	});
 }
 const CHAT_GONE_MESSAGE = "This chat is no longer available. Start a new one.";
-const chatKey = (agentId, userId) => `softr-agent-chat:${agentId}:${userId ?? "visitor"}`;
+const VISITOR = "visitor";
+const chatKey = (agentId, userId) => `softr-code-app:agent-chat:${agentId}:${userId ?? VISITOR}`;
+function chatStore(key) {
+	return key.endsWith(`:${VISITOR}`) ? sessionStorage : localStorage;
+}
 function savedChatId(key) {
 	try {
-		return localStorage.getItem(key);
+		return chatStore(key).getItem(key);
 	} catch {
 		return null;
 	}
 }
 function saveChatId(key, chatId) {
 	try {
-		if (chatId) localStorage.setItem(key, chatId);
-		else localStorage.removeItem(key);
+		if (chatId) chatStore(key).setItem(key, chatId);
+		else chatStore(key).removeItem(key);
 	} catch {}
 }
 async function failureMessage(res) {

package/dist/mcp.js

@@ -244,7 +244,8 @@ const WHOAMI = {
 		type: "object",
 		properties: {},
 		additionalProperties: false
-	}
+	},
+	annotations: { readOnlyHint: true }
 };
 /** How many records a read returns when the caller does not say. */
 const DEFAULT_LIMIT = 20;
@@ -265,6 +266,7 @@ function describeTool(action) {
 		case "read": return {
 			name: action.id,
 			description: `Read records from "${action.id}". Returns the fields ${names.join(", ")}. Only records the signed-in user may see come back.`,
+			annotations: { readOnlyHint: true },
 			inputSchema: {
 				type: "object",
 				properties: {

package/dist/package.js

@@ -1,5 +1,5 @@
 //#region package.json
-var version = "0.0.89-alpha.2";
+var version = "0.0.89-alpha.4";
 
 //#endregion
 export { version };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@softr/sdk",
-  "version": "0.0.89-alpha.2",
+  "version": "0.0.89-alpha.4",
   "type": "module",
   "exports": {
     ".": { "types": "./dist/index.d.ts", "import": "./dist/index.js" },

package/skills/softr-sdk/SKILL.md

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: core
   library: softr-sdk
-  library_version: 0.0.89-alpha.2
+  library_version: 0.0.89-alpha.4
 ---
 
 # Softr SDK core
@@ -86,7 +86,7 @@ Calling a connected third-party API (Slack, Stripe, Gmail, Google Calendar, …)
 Opening the app to an AI assistant over MCP?
   load softr-sdk/mcp
 
-Adding a chat with one of the app's Softr agents?
+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?

package/skills/softr-sdk/agent-chat/SKILL.md

@@ -3,14 +3,16 @@ name: agent-chat
 description: >-
   Let visitors chat with one of the app's Softr agents: listAgents() from
   @softr/sdk gives the agents the visitor may use, and useAgentChat(agentId, {
-  record }) returns the messages, the reply as it streams, and
-  send, stop, approve and reject, with no UI. Build the chat from the app's own
+  record }) returns the messages, the reply as it streams, past chats, and
+  send, stop, approve, reject and connect, with no UI. Load it for an agent
+  chat panel, approving the agent's actions, or connecting the visitor's own
+  account (Gmail, Slack…) that a tool needs. Build the chat from the app's own
   components. The agent acts on the app's data through the app's MCP, so
   softrMcpMiddleware must list the actions it may use.
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.89-alpha.2
+  library_version: 0.0.89-alpha.4
 ---
 
 **Boundary.** `listAgents` and `useAgentChat` live on `@softr/sdk`. `listAgents` runs in a route loader, `useAgentChat` in a component. Neither needs a route, server function or registration of its own. It chats as the signed-in visitor, or anonymously when no one is signed in.
@@ -56,13 +58,13 @@ function AgentPanel({ agentId, ticket }: { agentId: string; ticket: Ticket | nul
 
 ## What the hook returns
 
-- `messages`: the whole chat, oldest first. While the agent answers, its reply is the last message and grows as it streams.
+- `messages`: the whole chat, oldest first. While the agent answers, its reply is the last message and grows as it streams. A tool waiting for Approve or Connect comes last in its message, so render blocks in the order given.
 - `status`: `thinking` until the first part of the reply arrives, `replying` until it ends, then `idle`. Show a typing hint while it's `thinking`.
 - `loading`: `true` while a past chat loads. Show a spinner, not the empty-chat greeting.
 - `error`: why the last request failed, or `null`.
 - `send(text)`, `stop()`, `newChat()`.
-- `listChats()` resolves to the visitor's past chats, `{ id, title }[]`, with `title` `null` until the agent names the chat. `openChat(id)` loads one. `chatId` is the open one, `null` for a new chat. The open chat is kept in the browser for each visitor, so the hook reopens it after a remount or a reload.
-- `approve(toolCallId, scope?)` and `reject(toolCallId)` answer a tool waiting for approval. `scope` is `ONCE` (default), `SESSION` for the rest of this chat, or `USER` for always.
+- `listChats()` resolves to the visitor's past chats, `{ id, title }[]`, with `title` `null` until the agent names the chat. `openChat(id)` loads one. `chatId` is the open one, `null` for a new chat. The open chat is kept in the browser for each signed-in user, so the hook reopens it after a remount or a reload. A signed-out visitor keeps it only until the tab closes.
+- `approve(toolCallId, scope?)` and `reject(toolCallId)` answer a tool waiting for approval. `scope` is `ONCE` (default), `SESSION` for the rest of this chat, or `USER` for this agent from now on.
 - `connect(toolCallId)` signs the visitor in to a tool's `integration` in a popup. Call it straight from the click, or the browser blocks the popup.
 
 ## Rendering a message
@@ -77,7 +79,7 @@ Each message has `role` (`user` or `assistant`) and `blocks`, in the order the a
 | `question` | The questions with their options. One question with a single choice sends its label with `send` on click. Several questions, or `multiSelect`, collect the picks and show a Send button, enabled once each question has one. It sends one line per question, picked labels joined by ", ". |
 | `error` | An error line inside the reply |
 
-A `tool` with status `awaiting-approval` blocks the agent until the visitor answers. Show Approve and Reject buttons on it. The agent continues on its own after an approval.
+A `tool` with status `awaiting-approval` blocks the agent until the visitor answers. Give it a split Approve button and a Reject button, as classic apps do. The button says "Approve once" (`approve(id)`), and its menu offers "Approve for this session" (`approve(id, 'SESSION')`) and "Approve for this agent" (`approve(id, 'USER')`). With only one Approve, the visitor has to approve the same action again on every call. The agent continues on its own after an approval.
 
 A `tool` with status `awaiting-connection` needs the visitor's own `integration` account, such as their Gmail. Say "You need to connect to {integration} for this request. You'll only need to connect once.", with the name in readable case, and show a Connect button that calls `connect`. While it's `connecting`, show "Connecting…" and disable the button. The agent continues on its own once they're signed in. Any integration works the same way, so don't build one per integration.
 
@@ -92,8 +94,7 @@ Classic Softr apps ship a chat panel. Visitors expect the same from yours:
 - Text renders as Markdown, tables included.
 - The input says "Ask {agent title}…". Enter sends. Shift+Enter adds a line.
 - A line under the input: "AI can make mistakes. Please double-check responses."
-- A question with one choice sends on click. One with `multiSelect` or several questions sends once all are answered. An answered question stays locked.
-- Approve offers the three scopes: once, for this chat, always for this agent.
+- An answered question stays locked.
 - A tool's `input` is JSON. Show it readable: one `Label: value` line per field, with line breaks kept, never the raw JSON. Leave out `thought`, `input`, `error` or the duration when it's empty.
 - A tool that needs the visitor's account shows a Connect button.
 
@@ -113,12 +114,10 @@ The agent reads and changes data through the app's own MCP, as the visitor who i
 
 **Rendering only `text` blocks.** A tool waiting for approval never shows, and the agent waits forever. Render every block type.
 
-**The hook inside a panel that unmounts when it closes.** Closing it stops a reply that is still coming. Call `useAgentChat` in the component that owns the open state, such as the layout, and pass `chat` into the panel. Keep the selected agent there too, or closing the panel resets it.
+**The hook inside a panel that unmounts when it closes.** Closing it stops a reply that is still coming. Call `useAgentChat` in the component that owns the open state, such as `AppLayout` in `src/routes/_app.tsx`, and pass `chat` into the panel. Keep the selected agent there too, or closing the panel resets it.
 
 **An agent id written by hand.** The chat fails on the first message, and an agent hidden from the visitor still shows. Take the id from `listAgents`.
 
-**Expecting the agent to change data with no MCP wired.** It answers but can't act. List the actions it needs in `softrMcpMiddleware`.
-
 ## References
 
 - [mcp/SKILL.md](../mcp/SKILL.md): the actions the agent may call

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

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.89-alpha.2
+  library_version: 0.0.89-alpha.4
 ---
 
 **Boundary.** `auth` lives on `@softr/sdk/server` and runs only inside a `createServerFn` handler — importing it into a component fails the build.

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.89-alpha.2
+  library_version: 0.0.89-alpha.4
 ---
 
 **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.89-alpha.2
+  library_version: 0.0.89-alpha.4
 ---
 
 # The current user

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

@@ -7,7 +7,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.89-alpha.2
+  library_version: 0.0.89-alpha.4
 ---
 
 **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.89-alpha.2
+  library_version: 0.0.89-alpha.4
 ---
 
 # Dates, times and numbers

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

@@ -7,7 +7,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.89-alpha.2
+  library_version: 0.0.89-alpha.4
 ---
 
 **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.

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

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.89-alpha.2
+  library_version: 0.0.89-alpha.4
 ---
 
 **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.

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

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.89-alpha.2
+  library_version: 0.0.89-alpha.4
 ---
 
 # 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.89-alpha.2
+  library_version: 0.0.89-alpha.4
 ---
 
 **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.89-alpha.2
+  library_version: 0.0.89-alpha.4
 ---
 
 **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/region-visibility/SKILL.md

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

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

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.89-alpha.2
+  library_version: 0.0.89-alpha.4
 ---
 
 **Boundary.** `definePage`, `pageHead`, the access functions and the error predicates come from `@softr/sdk` and work anywhere.

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

@@ -9,7 +9,7 @@ description: >-
 metadata:
   type: sub-skill
   library: softr-sdk
-  library_version: 0.0.89-alpha.2
+  library_version: 0.0.89-alpha.4
 ---
 
 **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.