@alquimia-ai/ui 2.2.4 → 2.3.0

package/dist/tool-approval-K8aLzb1_.d.mts

@@ -0,0 +1,26 @@
+import * as react_jsx_runtime from 'react/jsx-runtime';
+import { ToolApproval } from '@alquimia-ai/tools/hooks';
+
+/** The subset of a `useAlquimia` `ToolApproval` this card reads. */
+type ToolApprovalView = Pick<ToolApproval, "controlId" | "toolName" | "arguments" | "channelOwned" | "status" | "reason" | "decidedHere" | "canAnswer" | "lastResult">;
+interface ToolApprovalCardProps {
+    approval: ToolApprovalView;
+    /** Usually `useAlquimia().approveTool`. */
+    onDecide: (controlId: string, approved: boolean, reason?: string) => unknown;
+    /**
+     * Name of the channel that owns a channel-bound gate ("WhatsApp", "Slack"…),
+     * for the explanation shown in place of the buttons. The runtime's refusal
+     * does not name it, so only the app can.
+     */
+    channelName?: string;
+    className?: string;
+}
+/**
+ * A human-approval gate: what the agent wants to run, with what arguments, and
+ * Approve / Reject. The card never decides the gate is settled on its own — it
+ * reflects `approval.status`, which the hook drives from the stream, so a
+ * decision made by another operator or on the originating channel shows here too.
+ */
+declare function ToolApprovalCard({ approval, onDecide, channelName, className }: ToolApprovalCardProps): react_jsx_runtime.JSX.Element;
+
+export { ToolApprovalCard as T, type ToolApprovalCardProps as a, type ToolApprovalView as b };

package/dist/tool-approval-K8aLzb1_.d.ts

@@ -0,0 +1,26 @@
+import * as react_jsx_runtime from 'react/jsx-runtime';
+import { ToolApproval } from '@alquimia-ai/tools/hooks';
+
+/** The subset of a `useAlquimia` `ToolApproval` this card reads. */
+type ToolApprovalView = Pick<ToolApproval, "controlId" | "toolName" | "arguments" | "channelOwned" | "status" | "reason" | "decidedHere" | "canAnswer" | "lastResult">;
+interface ToolApprovalCardProps {
+    approval: ToolApprovalView;
+    /** Usually `useAlquimia().approveTool`. */
+    onDecide: (controlId: string, approved: boolean, reason?: string) => unknown;
+    /**
+     * Name of the channel that owns a channel-bound gate ("WhatsApp", "Slack"…),
+     * for the explanation shown in place of the buttons. The runtime's refusal
+     * does not name it, so only the app can.
+     */
+    channelName?: string;
+    className?: string;
+}
+/**
+ * A human-approval gate: what the agent wants to run, with what arguments, and
+ * Approve / Reject. The card never decides the gate is settled on its own — it
+ * reflects `approval.status`, which the hook drives from the stream, so a
+ * decision made by another operator or on the originating channel shows here too.
+ */
+declare function ToolApprovalCard({ approval, onDecide, channelName, className }: ToolApprovalCardProps): react_jsx_runtime.JSX.Element;
+
+export { ToolApprovalCard as T, type ToolApprovalCardProps as a, type ToolApprovalView as b };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@alquimia-ai/ui",
-  "version": "2.2.4",
+  "version": "2.3.0",
   "author": "Alquimia AI",
   "description": "UI components for Alquimia SDK",
   "private": false,