lemma-sdk 0.2.34 → 0.2.36

package/README.md

@@ -1,8 +1,8 @@
 # Lemma TypeScript SDK
 
-`lemma-sdk` is the headless TypeScript SDK for Lemma. Use `lemma-sdk` for the core client, `lemma-sdk/react` for hooks and auth primitives, and the Lemma shadcn registry for stock UI blocks.
+`lemma-sdk` is the headless TypeScript SDK for Lemma. Use `lemma-sdk` for the core client and shared helpers, and use `lemma-sdk/react` as the main app-building surface for hooks and auth primitives.
 
-`AuthGuard` intentionally stays in `lemma-sdk/react`. Stock assistant, table, workflow, agent, member, and function UI lives in the registry.
+`AuthGuard` intentionally stays in `lemma-sdk/react`. The product direction remains hooks-first and shell-agnostic, and the registry ships stock Lemma UI blocks when you want installable assistant, records, file, workflow, collaboration, or shell surfaces.
 
 ## Install
 
@@ -10,7 +10,7 @@
 npm install lemma-sdk
 ```
 
-If your app uses shadcn/ui, configure the Lemma registry with:
+If your app wants stock Lemma UI installs, configure the registry with:
 
 ```bash
 npx lemma-sdk init-shadcn
@@ -74,10 +74,10 @@ import {
 | Area | Hooks | Stability | Use when |
 | --- | --- | --- | --- |
 | Auth | `AuthGuard`, `useAuth`, `useCurrentUser`, `usePodAccess` | Stable | Gate an app, read signed-in user state, or request pod access. |
-| Tables | `useTables`, `useTable`, `useRecords`, `useRecord`, `useJoinedRecords`, `useRelatedRecords`, `useReverseRelatedRecords`, `useReferencingRecords` | Stable | Build custom table browsers, details views, related-record views, and relational reads. |
+| Tables | `useTables`, `useTable`, `useRecords`, `useRecord`, `useJoinedRecords`, `useRelatedRecords`, `useReverseRelatedRecords`, `useReferencingRecords`, `useDatastoreQuery`, `useRecordAggregates` | Stable | Build custom table browsers, details views, related-record views, raw SQL-backed reads, and chart/KPI queries. |
 | Record mutations | `useCreateRecord`, `useUpdateRecord`, `useDeleteRecord`, `useBulkRecords` | Stable | Create, update, delete, or bulk-delete rows from headless UI. Function-backed mutations via `createVia`/`updateVia` options. |
 | Record forms | `useRecordSchema`, `useRecordForm`, `useForeignKeyOptions`, `useSchemaForm` | Stable | Render schema-driven record forms, enum fields, and foreign-key selectors. `useRecordForm` is the canonical table-bound form hook; `useSchemaForm` remains available for raw JSON-schema flows. |
-| Files | `useFiles`, `useFile`, `useFileSearch`, `useFileTree`, `useFilePreview` | Stable | Browse datastore folders, resolve file metadata, search indexed files, load directory trees, and preview converted or raw file content. |
+| Files | `useFiles`, `useFile`, `useUploadFile`, `useUpdateFile`, `useDeleteFile`, `useCreateFolder`, `useFileSearch`, `useFileTree`, `useFilePreview`, `useGlobalSearch` | Stable | Browse datastore folders, mutate file state, search indexed files, load directory trees, preview content, and compose multi-source desk search. |
 | Assistant | `useConversations`, `useConversation`, `useConversationMessages`, `useAssistantRun`, `useAssistantSession`, `useAssistantRuntime`, `useAssistantController` | Stable except controller/runtime | Build custom chat, conversation lists, streaming output, and final-output views. |
 | Agents | `useAgentRun`, `useAgentRuns`, `useAgentInputSchema`, `useTaskSession` | Stable except raw session | Start agent tasks, submit follow-up input, read task history, and inspect input/output schemas. |
 | Workflows | `useWorkflowStart`, `useWorkflowRun`, `useWorkflowRuns`, `useWorkflowResume` | Stable | Start, poll, resume, cancel, retry, and inspect workflow runs. |
@@ -85,6 +85,13 @@ import {
 | Functions | `useFunctionRun`, `useFunctionRuns`, `useFunctionSession` | Stable except raw session | Run functions, poll function runs, and list function history. |
 | Members and org | `useMembers`, `useAddPodMember`, `useUpdatePodMemberRole`, `useRemovePodMember`, `useOrganizationMembers` | Stable | Read pod and organization members, add existing org members into a pod, update pod roles, and remove pod access. The current checked-in client does not yet expose direct email-to-pod invites. |
 
+### Headless Helpers
+
+Alongside hooks, `lemma-sdk` exports shared headless helpers for common desk logic:
+
+- record display helpers: `formatRecordDisplayValue`, `humanizeRecordFieldName`, `detectRecordStatusColumn`
+- form/schema helpers: `buildRecordSchemaFields`, `buildSchemaFormFields`
+
 ### Common Hook Shapes
 
 For business-facing examples and a decision guide mapping "I want to..." to the right hook, see [docs/hooks-guide.md](docs/hooks-guide.md).
@@ -209,9 +216,9 @@ function WorkflowButton({ client }: { client: LemmaClient }) {
 }
 ```
 
-## Shadcn Registry
+## Registry
 
-Lemma UI lives in the registry, not in `lemma-sdk/react`.
+The registry is optional UI scaffolding for teams that want stock Lemma blocks on top of the headless SDK.
 
 After running `npx lemma-sdk init-shadcn`, install blocks like:
 
@@ -221,32 +228,21 @@ npx shadcn@latest add @lemma/lemma-detail-panel
 npx shadcn@latest add @lemma/lemma-record-form
 npx shadcn@latest add @lemma/lemma-global-search
 npx shadcn@latest add @lemma/lemma-file-browser
-npx shadcn@latest add @lemma/lemma-file-viewer
 npx shadcn@latest add @lemma/lemma-document-workspace
-npx shadcn@latest add @lemma/lemma-document-creator
-npx shadcn@latest add @lemma/lemma-document-viewer
-npx shadcn@latest add @lemma/lemma-document-editor
-npx shadcn@latest add @lemma/lemma-members
 npx shadcn@latest add @lemma/lemma-comments
-npx shadcn@latest add @lemma/lemma-insights
 npx shadcn@latest add @lemma/lemma-assistant-experience
 ```
 
-Those commands are representative. The registry currently ships 22 canonical blocks.
-
-Current registry items:
+The registry currently ships 19 canonical blocks:
 
 | Area | Items |
 | --- | --- |
-| Assistant | `lemma-assistant-experience` |
-| Navigation | `lemma-breadcrumbs`, `lemma-global-search`, `lemma-page-tree` |
-| Records | `lemma-records-view`, `lemma-detail-panel`, `lemma-record-form`, `lemma-status-flow` |
-| Files | `lemma-file-browser`, `lemma-file-viewer` |
-| Documents | `lemma-document-workspace`, `lemma-document-creator`, `lemma-document-viewer`, `lemma-document-editor`, `lemma-markdown-editor` |
-| People | `lemma-members`, `lemma-notification-bell`, `lemma-user-menu` |
-| Analytics | `lemma-insights` |
-| Collaboration | `lemma-activity-feed`, `lemma-comments` |
-| Automation | `lemma-workflow-runner` |
+| Core operator blocks | `lemma-records-view`, `lemma-detail-panel`, `lemma-record-form`, `lemma-status-flow` |
+| Search, files, and pages | `lemma-global-search`, `lemma-breadcrumbs`, `lemma-file-browser`, `lemma-markdown-editor`, `lemma-page-tree`, `lemma-document-workspace` |
+| Collaboration and analytics | `lemma-comments`, `lemma-activity-feed`, `lemma-insights`, `lemma-action-surface`, `lemma-workflow-runner` |
+| Assistant and shell | `lemma-assistant-experience`, `lemma-members`, `lemma-notification-bell`, `lemma-user-menu` |
+
+Registry blocks now install against a shared `lemma-ui` primitive layer that ships with this registry. Consumers no longer need a pre-existing app-local `@/components/ui/*` shadcn tree just to use Lemma blocks.
 
 The registry is currently served from jsDelivr against this public repo:
 
@@ -261,54 +257,44 @@ Blocks that install a CSS file, such as records view, should be imported by your
 @import "@/styles/lemma-records-view.css";
 ```
 
-### Records Workspace Customization
-
-The records blocks are meant to be configured with props before you reach for a fork.
-
-`lemma-records-view` supports:
-
-- `preset="triage" | "issues" | "crm" | "docs"` for opinionated defaults without installing duplicate workflow blocks
-- `defaultView` and `availableViews` across `grid`, `list`, `grouped`, `kanban`, `linear`, `calendar`, `timeline`, and `matrix`
-- `tableName`, `visibleColumns`, and `hiddenFields` for schema-aware display
-- `pinnedColumns`, `columnWidths`, `columnLabels`, `primaryField`, `defaultSort`, and `paginationMode` for stronger operator-table defaults
-- `groupBy`, `calendarField`, `timelineField`, `matrixRowsBy`, and `matrixColumnsBy` for consolidated view configuration
-- `renderCell` and `renderCard` for custom record rendering
-- `foreignKeyLabels` for human-readable FK values in cards, detail views, and create/edit forms
-- `detailTabs`, `detailFieldGroups`, `detailRelatedRecords`, `detailSectionLabels`, and `detailSectionVisibility` for canonical detail composition
-- `quickActions`, `bulkActions`, `detailActions`, `quickActionMode`, and `onQuickActionSuccess` for direct, function, or workflow-backed actions
-- `onCreateOptions` and `onUpdateOptions` for function-backed mutations, including conditional field and section visibility in the create sheet
-- `createMode="sheet" | "modal" | "page"` and `detailMode="sheet" | "modal" | "page" | "inline"` for app-specific interaction patterns
-- `headerActions`, `emptyState`, `onRecordClick`, `renderFilesTab`, `renderCommentsTab`, and `renderActivityTab` for app-specific extensions
-- `appearance="default" | "minimal" | "borderless" | "contained"` and `density="compact" | "comfortable" | "spacious"` for host-level block chrome; `minimal` is the cardless mode
-
-`lemma-detail-panel` supports:
-
-- standalone record detail rendering outside the full records workspace, using the same canonical detail internals as `lemma-records-view`
-- `mode`, `variant`, and `layout` controls for embedded, sheet, modal, or full-page use
-- built-in detail tabs plus custom `tabs`, `relatedRecords`, and `renderFiles` / `renderComments` / `renderActivity` sections
-- direct, function-backed, and workflow-aware `actions`, plus `updateVia` / `updateFunctionName` for inline edits
-- shared `appearance`, `density`, and `radius` controls for use in inline, sheet, modal, or page layouts
-
-`lemma-record-form` supports:
-
-- `mode="inline" | "modal" | "sheet"`
-- `submitVia="direct" | "function"` and `submitFunctionName`
-- `submitFunctionInput` when the backing function expects a different payload shape
-- `hiddenFields`, `visibleFields`, `fieldOrder`, and `fieldGroups`
-- searchable FK inputs through the shared `record-form-fields` control layer
-- `fieldVisibility` and `sectionVisibility` for conditional forms
-- `foreignKeyLabels` for FK select labels
-- `initialValues`, `onSuccess`, and `onClose`
-- `appearance`, `density`, and `radius` using the same values as `lemma-records-view`
-
-`lemma-insights` supports:
-
-- table-backed count, sum, average, and grouped chart cards
-- bar, line, area, pie, and funnel charts with count/sum/avg aggregation
-- `aggregationMode="client" | "function"` with optional `aggregateFunctionName` for shared server-side aggregation
-- chart descriptions, value/category formatters, limits, sorting, empty states, and optional footers
-- function-backed stats and charts
-- shared `appearance`, `density`, `radius`, and card-column controls
+Core registry blocks:
+
+- `lemma-records-view` for a lean records browser by default, with explicit workspace presets for grid, list, grouped, kanban, and linear operator flows
+- `lemma-detail-panel` for standalone record detail rendering with shared records-detail internals
+- `lemma-record-form` for schema-aware create and edit flows with searchable foreign-key controls
+- `lemma-status-flow` for interactive status transitions and lifecycle display
+- `lemma-global-search` for a stock command-bar style omnibox
+- `lemma-file-browser` and `lemma-document-workspace` for file browsing, editing, preview, and document-native workflows
+- `lemma-comments`, `lemma-activity-feed`, and `lemma-insights` for collaboration and reporting
+- `lemma-action-surface` and `lemma-workflow-runner` for long-running actions and workflow history
+- `lemma-assistant-experience`, `lemma-members`, `lemma-notification-bell`, and `lemma-user-menu` for assistant and shell surfaces
+
+### Block Defaults
+
+The registry now treats generic blocks as read-first and low-chrome by default.
+
+- base blocks should render useful data without assuming a full workspace shell
+- presets are the place for opinionated operator UX such as inline detail, multi-view boards, and heavier toolbars
+- `appearance`, `density`, and `radius` remain available as local override props on major blocks, but they are optional; prefer setting visual defaults in your app shell or wrapper components instead of passing them everywhere
+
+`lemma-records-view` now defaults to:
+
+- one explicit view instead of an inferred multi-view workspace
+- no search bar unless you opt in through `chrome.search` or pass search config
+- no filter launcher unless you opt in through `chrome.filters` or provide default filters
+- no create button unless you opt in through `chrome.create` or pass create config
+- no row-selection chrome unless you opt in through `chrome.selection` or provide bulk actions
+- `detailMode="sheet"` for the base block, with inline detail reserved for explicit presets or explicit props
+- no schema-name heuristics that silently promote a table into `kanban` or `linear`
+
+For records workspaces, the split is:
+
+- use the base block for simple table/list browsing
+- pass `availableViews` only when you want a view switcher
+- pass `chrome={{ search: true, filters: true, create: true, viewSwitcher: true, selection: true }}` when you want workspace controls on the base block
+- use `preset="triage" | "issues" | "crm" | "docs"` when you want a stock operator workspace
+
+`lemma-members` now defaults to a read-only membership list. Add management behavior explicitly with `allowAdd`, `allowRoleEdit`, and `allowRemove`.
 
 `lemma-global-search` supports:
 
@@ -318,80 +304,81 @@ The records blocks are meant to be configured with props before you reach for a
 - `minQueryLength`, `debounceMs`, `appearance`, `density`, trigger label, and placeholder customization
 - assistant handoff by `assistantName`, with optional query/results message shaping and conversation routing
 
-Navigation blocks support:
-
-- route, record, and file-path breadcrumb builders through `lemma-breadcrumbs`
-- self-referential page hierarchies through `lemma-page-tree`, with selection, expansion, and create/reorder hooks
-
-File blocks support:
-
-- datastore folder navigation and path breadcrumbs through `lemma-file-browser`
-- pod-level file browsing and search, not only record-linked attachments
-- upload, download, search, rename, move, folder creation, picker mode, and composition-friendly link actions
-- selection-aware file browsing so `lemma-file-browser` can drive a paired workspace preview
-- image, PDF, text, markdown, converted HTML, metadata, and breadcrumb-aware previews through `lemma-file-viewer`
-
 Document blocks support:
 
-- Notion/Coda-style block documents through `lemma-document-workspace`, with Tiptap JSON content, page/modal modes, title and summary chrome, file/reference/assistant blocks, save state, metadata, backlinks, and assistant-context rails
-- docstore-native creation through `lemma-document-workspace` or the simpler `lemma-document-creator`, with folder targeting, title/summary setup, pod-file metadata, and `mode="page" | "modal"`
-- long-form reading surfaces through `lemma-document-workspace` or `lemma-document-viewer`, with full-page and modal presentation, metadata, backlinks, references, and assistant-context rails
-- long-form authoring through `lemma-document-workspace` or `lemma-document-editor`, with full-page and modal presentation, title/summary chrome, save-state affordances, outline, references, and assistant-context rails
-- a clean separation between richer document UX and the lower-level pod file workspace, while keeping pod files as the primary document store and avoiding embedded-first document editing
+- Notion/Coda-style block documents through `lemma-document-workspace`, with ProseKit JSON content, page/modal modes, title and summary chrome, file/reference/assistant blocks, save state, metadata, backlinks, and assistant-context rails
+- pod-file-native creation, reading, editing, and preview through one workspace, with folder targeting, title/summary setup, pod-file metadata, and `mode="page" | "modal"`
+- non-document file previews through the same workspace, including image, PDF, text, markdown, converted HTML, and download fallback behavior
+- records and attachments should pass pod file paths into `lemma-document-workspace`; records should not own document bodies directly
 
 People blocks support:
 
 - `LemmaMemberChip`, `LemmaAvatarGroup`, `LemmaMemberSelect`, and `LemmaUserField`
-- a stock `LemmaMembers` admin workspace for pod membership, role changes, removal, and add-from-organization flows via `organizationId`, `allowAdd`, `allowRoleEdit`, and `allowRemove`
+- a stock `LemmaMembers` surface that is read-only by default, and upgrades into a membership admin workspace only when `allowAdd`, `allowRoleEdit`, or `allowRemove` are enabled
 - pod member labels for owner, creator, assignee, participant, and author fields
 - searchable member picking backed by `useMembers`
 
 Workflow primitives support:
 
 - lifecycle/status rendering and transitions through `lemma-status-flow`
-- read-only tracker layouts and compact step progress through `lemma-status-flow`
-- workflow run inspection through `lemma-workflow-runner`
-- reusable history and collaboration surfaces through `lemma-activity-feed` and `lemma-comments`
-- table-backed defaults with escape hatches for custom action payloads and render slots
+- direct, function-backed, workflow-backed, and agent-backed launches through `lemma-action-surface`
+- inline, row, and panel presentation modes for long-running actions with inspectable progress
+- native workflow run inspection through `lemma-workflow-runner`
+
+Navigation and file blocks support:
+
+- route, record, and file-path breadcrumb builders through `lemma-breadcrumbs`
+- native pod-file hierarchy navigation through `lemma-page-tree`
+- datastore folder navigation, upload, rename, move, folder creation, picker mode, and delete handling through `lemma-file-browser`
+- write, preview, and split modes through `lemma-markdown-editor`
 
-`lemma-markdown-editor` supports:
+Collaboration and analytics blocks support:
 
-- write, preview, and split modes
-- controlled and uncontrolled values
-- GitHub-flavored markdown preview via `react-markdown` and `remark-gfm`
-- a lightweight interim editing lane for plain markdown notes beside the richer block-native `lemma-document-workspace`
+- record-scoped discussion through `lemma-comments`
+- unified audit and history timelines through `lemma-activity-feed`
+- dashboard-style stat cards and charts through `lemma-insights`
 
 Assistant blocks support:
 
 - assistant-name-first configuration through `assistantName`
 - shared `appearance` and `density` controls on the assistant experience surface
 - `chromeStyle`, `statusPlacement`, `radius`, model picker, conversation list, and render overrides for deeper customization
-
-Shell blocks support:
-
-- `lemma-notification-bell` for unread counts, popover inboxes, and mark-as-read flows
-- `lemma-user-menu` for current-user presentation, custom menu actions, and sign-out affordances
+- bounded default heights for `page` and `side-panel` modes so the message viewport scrolls instead of stretching with content; pass `className="h-full min-h-0"` inside an explicit-height parent when you want a fill-layout assistant like inbox CRM
 
 ```tsx
 import { LemmaRecordsView } from "@/components/lemma/lemma-records-view";
+import { LemmaAssistantExperience } from "@/components/lemma/assistant/assistant-experience";
+import { LemmaActionSurface } from "@/components/lemma/lemma-action-surface";
 import { LemmaGlobalSearch } from "@/components/lemma/lemma-global-search";
 
+<LemmaRecordsView
+  client={client}
+  podId={podId}
+  tableName="tickets"
+/>;
+
 <LemmaRecordsView
   client={client}
   podId={podId}
   tableName="deals"
-  preset="crm"
+  defaultView="list"
+  availableViews={["list", "grid"]}
+  chrome={{ search: true, filters: true, create: true, viewSwitcher: true, selection: true }}
   hiddenFields={["id", "created_at", "updated_at"]}
   foreignKeyLabels={{ company_id: "name" }}
-  appearance="minimal"
-  density="compact"
-  createMode="sheet"
   onCreateOptions={{
     submitVia: "function",
     submitFunctionName: "create-deal",
   }}
 />;
 
+<LemmaRecordsView
+  client={client}
+  podId={podId}
+  tableName="deals"
+  preset="crm"
+/>;
+
 <LemmaGlobalSearch
   client={client}
   podId={podId}
@@ -413,8 +400,19 @@ import { LemmaGlobalSearch } from "@/components/lemma/lemma-global-search";
   }}
   minQueryLength={3}
   debounceMs={450}
-  appearance="minimal"
-  density="compact"
+/>;
+
+<LemmaActionSurface
+  client={client}
+  podId={podId}
+  label="Run triage"
+  kind="workflow"
+  workflowName="triage-lead"
+/>;
+
+<LemmaAssistantExperience
+  client={client}
+  assistantName="sales-copilot"
 />;
 ```
 
@@ -455,14 +453,14 @@ npm run build
 npm run registry:build
 ```
 
-To build the canonical example desk:
+To build the single local sandbox app:
 
 ```bash
 cd examples/inbox-crm
 npm run build
 ```
 
-`examples/inbox-crm` now mirrors the kept registry surface only. Its local `src/components/lemma` folder is a copied install target of the current canonical registry blocks, and `src/main.tsx` demonstrates those blocks in one routed operator desk.
+`examples/inbox-crm` is the only kept example app in this repo. It is a local sandbox for visualizing the current direction, not a promise that every copied component inside it is a published registry block.
 
 This repo includes:
 

package/dist/browser/lemma-client.js

@@ -2675,19 +2675,27 @@ exports.IconsService = IconsService;
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.IntegrationsNamespace = void 0;
+const AgentToolsService_js_1 = require("./openapi_client/services/AgentToolsService.js");
 const ApplicationsService_js_1 = require("./openapi_client/services/ApplicationsService.js");
 const IntegrationsService_js_1 = require("./openapi_client/services/IntegrationsService.js");
 class IntegrationsNamespace {
     constructor(client) {
         this.client = client;
         this.operations = {
-            list: (applicationId) => this.client.request(() => ApplicationsService_js_1.ApplicationsService.applicationOperationList(applicationId)),
+            discover: (applicationId, options = {}) => this.client.request(() => ApplicationsService_js_1.ApplicationsService.applicationOperationDiscover(applicationId, options.query, options.limit ?? 100)),
+            list: async (applicationId, options = {}) => {
+                const response = await this.client.request(() => ApplicationsService_js_1.ApplicationsService.applicationOperationDiscover(applicationId, options.query, options.limit ?? 100));
+                return response.items ?? [];
+            },
             get: (applicationId, operationName) => this.client.request(() => ApplicationsService_js_1.ApplicationsService.applicationOperationDetail(applicationId, operationName)),
+            details: (applicationId, operationNames) => {
+                const body = { operation_names: operationNames };
+                return this.client.request(() => ApplicationsService_js_1.ApplicationsService.applicationOperationDetailsBatch(applicationId, body));
+            },
             execute: (applicationId, operationName, payload, accountId) => {
                 const body = { payload, account_id: accountId };
                 return this.client.request(() => ApplicationsService_js_1.ApplicationsService.applicationOperationExecute(applicationId, operationName, body));
             },
-            descriptor: (applicationId) => this.client.request(() => ApplicationsService_js_1.ApplicationsService.applicationDescriptor(applicationId)),
         };
         this.triggers = {
             list: (options = {}) => this.client.request(() => ApplicationsService_js_1.ApplicationsService.applicationTriggerList(options.applicationId, options.search, options.limit ?? 100, options.pageToken)),
@@ -2706,6 +2714,13 @@ class IntegrationsNamespace {
     get(applicationId) {
         return this.client.request(() => ApplicationsService_js_1.ApplicationsService.applicationGet(applicationId));
     }
+    helperAgent(goal, appNames) {
+        const body = {
+            app_names: appNames,
+            goal,
+        };
+        return this.client.request(() => AgentToolsService_js_1.AgentToolsService.toolIntegrationHelperAgent(body));
+    }
     createConnectRequest(applicationId) {
         const payload = { application_id: applicationId };
         return this.client.request(() => IntegrationsService_js_1.IntegrationsService.integrationConnectRequestCreate(payload));
@@ -2713,6 +2728,89 @@ class IntegrationsNamespace {
 }
 exports.IntegrationsNamespace = IntegrationsNamespace;
 
+},
+"./openapi_client/services/AgentToolsService.js": function (module, exports, require) {
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.AgentToolsService = void 0;
+const OpenAPI_js_1 = require("./openapi_client/core/OpenAPI.js");
+const request_js_1 = require("./openapi_client/core/request.js");
+class AgentToolsService {
+    /**
+     * Integration Helper Agent
+     * Plan how to use one or more integration applications for a goal and return recommended operations.
+     * @param requestBody
+     * @returns IntegrationHelperAgentResponse Successful Response
+     * @throws ApiError
+     */
+    static toolIntegrationHelperAgent(requestBody) {
+        return (0, request_js_1.request)(OpenAPI_js_1.OpenAPI, {
+            method: 'POST',
+            url: '/tools/integration-helper-agent',
+            body: requestBody,
+            mediaType: 'application/json',
+            errors: {
+                422: `Validation Error`,
+            },
+        });
+    }
+    /**
+     * Report Feedback
+     * Record a maintainer-facing feedback report about system issues, skill issues, incorrect knowledge, or other unexpected behavior.
+     * @param requestBody
+     * @returns ReportFeedbackResponse Successful Response
+     * @throws ApiError
+     */
+    static toolReportFeedback(requestBody) {
+        return (0, request_js_1.request)(OpenAPI_js_1.OpenAPI, {
+            method: 'POST',
+            url: '/tools/report-feedback',
+            body: requestBody,
+            mediaType: 'application/json',
+            errors: {
+                422: `Validation Error`,
+            },
+        });
+    }
+    /**
+     * Web Search
+     * Run a raw web search and return structured results.
+     * @param requestBody
+     * @returns WebSearchResponse Successful Response
+     * @throws ApiError
+     */
+    static toolWebSearch(requestBody) {
+        return (0, request_js_1.request)(OpenAPI_js_1.OpenAPI, {
+            method: 'POST',
+            url: '/tools/web-search',
+            body: requestBody,
+            mediaType: 'application/json',
+            errors: {
+                422: `Validation Error`,
+            },
+        });
+    }
+    /**
+     * Web Search Agent
+     * Run the multi-step web search agent and return a synthesized answer.
+     * @param requestBody
+     * @returns WebSearchAgentResponse Successful Response
+     * @throws ApiError
+     */
+    static toolWebSearchAgent(requestBody) {
+        return (0, request_js_1.request)(OpenAPI_js_1.OpenAPI, {
+            method: 'POST',
+            url: '/tools/web-search-agent',
+            body: requestBody,
+            mediaType: 'application/json',
+            errors: {
+                422: `Validation Error`,
+            },
+        });
+    }
+}
+exports.AgentToolsService = AgentToolsService;
+
 },
 "./openapi_client/services/ApplicationsService.js": function (module, exports, require) {
 "use strict";
@@ -2806,15 +2904,14 @@ class ApplicationsService {
         });
     }
     /**
-     * List Application Operations
+     * Discover Application Operations
      * @param applicationId
      * @param query
      * @param limit
-     * @param pageToken
-     * @returns OperationListResponse Successful Response
+     * @returns OperationDiscoverResponse Successful Response
      * @throws ApiError
      */
-    static applicationOperationList(applicationId, query, limit = 100, pageToken) {
+    static applicationOperationDiscover(applicationId, query, limit = 100) {
         return (0, request_js_1.request)(OpenAPI_js_1.OpenAPI, {
             method: 'GET',
             url: '/integrations/applications/{application_id}/operations',
@@ -2824,7 +2921,6 @@ class ApplicationsService {
             query: {
                 'query': query,
                 'limit': limit,
-                'page_token': pageToken,
             },
             errors: {
                 422: `Validation Error`,
@@ -2832,18 +2928,21 @@ class ApplicationsService {
         });
     }
     /**
-     * Get Application Descriptor
+     * Get Application Operation Details In Batch
      * @param applicationId
-     * @returns AppDescriptorResponse Successful Response
+     * @param requestBody
+     * @returns OperationDetailsBatchResponse Successful Response
      * @throws ApiError
      */
-    static applicationDescriptor(applicationId) {
+    static applicationOperationDetailsBatch(applicationId, requestBody) {
         return (0, request_js_1.request)(OpenAPI_js_1.OpenAPI, {
-            method: 'GET',
-            url: '/integrations/applications/{application_id}/operations/descriptor',
+            method: 'POST',
+            url: '/integrations/applications/{application_id}/operations/details',
             path: {
                 'application_id': applicationId,
             },
+            body: requestBody,
+            mediaType: 'application/json',
             errors: {
                 422: `Validation Error`,
             },
@@ -3005,15 +3104,17 @@ class IntegrationsService {
      * OAuth Callback
      * Handle OAuth callback and complete account connection. This endpoint is public and uses state parameter for security.
      * @param error
-     * @returns AccountResponseSchema Successful Response
+     * @param format
+     * @returns string Successful Response
      * @throws ApiError
      */
-    static integrationOauthCallback(error) {
+    static integrationOauthCallback(error, format) {
         return (0, request_js_1.request)(OpenAPI_js_1.OpenAPI, {
             method: 'GET',
             url: '/integrations/connect-requests/oauth/callback',
             query: {
                 'error': error,
+                'format': format,
             },
             errors: {
                 422: `Validation Error`,
@@ -3207,6 +3308,46 @@ class OrganizationsService {
             },
         });
     }
+    /**
+     * Check Organization Slug Availability
+     * Check whether an organization slug is available
+     * @param slug
+     * @returns OrganizationSlugAvailabilityResponse Successful Response
+     * @throws ApiError
+     */
+    static orgSlugAvailability(slug) {
+        return (0, request_js_1.request)(OpenAPI_js_1.OpenAPI, {
+            method: 'GET',
+            url: '/organizations/slug-availability',
+            query: {
+                'slug': slug,
+            },
+            errors: {
+                422: `Validation Error`,
+            },
+        });
+    }
+    /**
+     * Get Suggested Organizations
+     * Get auto-join organizations matching the current user's email domain
+     * @param limit
+     * @param pageToken
+     * @returns OrganizationListResponse Successful Response
+     * @throws ApiError
+     */
+    static orgSuggested(limit = 100, pageToken) {
+        return (0, request_js_1.request)(OpenAPI_js_1.OpenAPI, {
+            method: 'GET',
+            url: '/organizations/suggested',
+            query: {
+                'limit': limit,
+                'page_token': pageToken,
+            },
+            errors: {
+                422: `Validation Error`,
+            },
+        });
+    }
     /**
      * Get Organization
      * Get organization details
@@ -5091,6 +5232,27 @@ class WorkflowsService {
             },
         });
     }
+    /**
+     * List Workflow Installs
+     * List the current user's installations for a workflow.
+     * @param podId
+     * @param workflowName
+     * @returns WorkflowInstallListResponse Successful Response
+     * @throws ApiError
+     */
+    static workflowInstallList(podId, workflowName) {
+        return (0, request_js_1.request)(OpenAPI_js_1.OpenAPI, {
+            method: 'GET',
+            url: '/pods/{pod_id}/workflows/{workflow_name}/installs',
+            path: {
+                'pod_id': podId,
+                'workflow_name': workflowName,
+            },
+            errors: {
+                422: `Validation Error`,
+            },
+        });
+    }
     /**
      * Uninstall Workflow
      * Remove a previously created workflow installation binding.