@blocksdiy/react-common 1.26.0 → 1.27.0

package/dist/components/new-agent-chat.js

@@ -30,10 +30,10 @@ const generateId = (length = 10) => {
  * Walk the conversation and return every assistant-emitted tool call
  * that has no matching ToolMessage (i.e. is awaiting a result). With
  * our current setup, the only tool that ends up in this state is the
- * frontend HITL `ask_user`; backend tools resolve in the same agent
- * run and never appear pending in the UI. Used by `sendFromInputs`
- * to auto-skip dangling questions when the user types a new message
- * instead of clicking an answer.
+ * frontend user-choice tool; backend tools resolve in the same agent
+ * run and never appear pending in the UI. Used by `sendFromInputs` to
+ * auto-skip dangling answer UIs when the user types a new message
+ * instead of choosing an answer.
  */
 const _collectPendingToolCalls = (messages) => {
     const toolMessageIds = new Set();
@@ -307,14 +307,14 @@ const ChatInitializer = ({ agentId, agentChatId, chatId, token, appId, component
         // const currentAttachments = attachments;
         setPrompt("");
         setAttachments([]);
-        // Auto-skip any HITL tool call that's still waiting for an answer.
+        // Auto-skip any frontend user-choice tool call that's still waiting.
         //
         // If the user types a new message instead of clicking an answer on
-        // an `ask_user` form, the agent had returned an assistant message
-        // with a tool call and is parked awaiting a ToolMessage that never
-        // arrives. Without intervention here:
-        //   * `executingToolCallIds` keeps the toolCallId (the parked HITL
-        //     Promise from useHumanInTheLoop never resolves, so
+        // the inline form, the agent had returned an assistant message with
+        // a tool call and is parked awaiting a ToolMessage that never arrives.
+        // Without intervention here:
+        //   * `executingToolCallIds` keeps the toolCallId (the parked Promise
+        //     from useHumanInTheLoop never resolves, so
         //     onToolExecutionEnd never fires).
         //   * No ToolMessage is ever added, so the render code stays on
         //     "executing" → the form looks live forever, the next refresh
@@ -330,10 +330,10 @@ const ChatInitializer = ({ agentId, agentChatId, chatId, token, appId, component
         //     (assistant_tool_call → skip_result → new user turn) so the
         //     agent can respond coherently.
         //
-        // Caveat: we don't (and can't, with the current useHumanInTheLoop
-        // API) resolve the parked HITL Promise itself — it lingers in
-        // memory until page reload. Acceptable: one closure per skip,
-        // cleared on refresh, no functional impact.
+        // Caveat: we don't (and can't, with the current useHumanInTheLoop API)
+        // resolve the parked Promise itself — it lingers in memory until page
+        // reload. Acceptable: one closure per skip, cleared on refresh, no
+        // functional impact.
         if (copilotAgent) {
             const pending = _collectPendingToolCalls(copilotAgent.messages);
             for (const toolCall of pending) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@blocksdiy/react-common",
-  "version": "1.26.0",
+  "version": "1.27.0",
   "type": "module",
   "description": "React common",
   "keywords": [],