langroid 0.1.244__tar.gz → 0.1.246__tar.gz

{langroid-0.1.244 → langroid-0.1.246}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: langroid
-Version: 0.1.244
+Version: 0.1.246
 Summary: Harness LLMs with Multi-Agent Programming
 License: MIT
 Author: Prasad Chalasani

{langroid-0.1.244 → langroid-0.1.246}/langroid/agent/callbacks/chainlit.py

@@ -579,17 +579,18 @@ class ChainlitTaskCallbacks(ChainlitAgentCallbacks):
         top-level agent"""
 
         super().__init__(task.agent, msg, config)
-        ChainlitTaskCallbacks._inject_callbacks(task)
+        self._inject_callbacks(task)
         self.task = task
         self.task.callbacks.show_subtask_response = self.show_subtask_response
 
-    @staticmethod
+    @classmethod
     def _inject_callbacks(
-        task: lr.Task, config: ChainlitCallbackConfig = ChainlitCallbackConfig()
+        cls, task: lr.Task, config: ChainlitCallbackConfig = ChainlitCallbackConfig()
     ) -> None:
         # recursively apply ChainlitAgentCallbacks to agents of sub-tasks
         for t in task.sub_tasks:
-            ChainlitTaskCallbacks(t, config=config)
+            cls(t, config=config)
+            # ChainlitTaskCallbacks(t, config=config)
 
     def show_subtask_response(
         self, task: lr.Task, content: str, is_tool: bool = False

{langroid-0.1.244 → langroid-0.1.246}/langroid/agent/chat_document.py

@@ -166,6 +166,21 @@ class ChatDocument(Document):
         message = message.strip()
         if message in ["''", '""']:
             message = ""
+        if response.function_call is not None:
+            # Sometimes an OpenAI LLM (esp gpt-4o) may generate a function-call
+            # with odditities:
+            # (a) the `name` is set, as well as `arugments.request` is set,
+            #  and in langroid we use the `request` value as the `name`.
+            #  In this case we override the `name` with the `request` value.
+            # (b) the `name` looks like "functions blah" or just "functions"
+            #   In this case we strip the "functions" part.
+            fc = response.function_call
+            fc.name = fc.name.replace("functions", "").strip()
+            if fc.arguments is not None:
+                request = fc.arguments.get("request")
+                if request is not None and request != "":
+                    fc.name = request
+                    fc.arguments.pop("request")
         return ChatDocument(
             content=message,
             function_call=response.function_call,

{langroid-0.1.244 → langroid-0.1.246}/langroid/agent/special/lance_rag/critic_agent.py

@@ -50,10 +50,10 @@ class QueryPlanCriticConfig(LanceQueryPlanAgentConfig):
       In general the REPHRASED QUERY should be relied upon to match the CONTENT 
       of the docs. Thus the REPHRASED QUERY itself acts like a 
       SEMANTIC/LEXICAL/FUZZY FILTER since the Assistant is able to use it to match 
-      the CONTENT of the docs in various ways (semantic, lexical, fuzzy, etc.).
-         
-    - DATAFRAME CALCULATION, which must be a SINGLE LINE calculation, and 
-    - ANSWER recieved from an assistant that used this QUERY PLAN.
+      the CONTENT of the docs in various ways (semantic, lexical, fuzzy, etc.).         
+    - DATAFRAME CALCULATION, which must be a SINGLE LINE calculation (or empty),
+        [NOTE ==> This calculation is applied AFTER the FILTER and REPHRASED QUERY.],
+    - ANSWER received from an assistant that used this QUERY PLAN.
 
     In addition to the above SCHEMA fields there is a `content` field which:
     - CANNOT appear in a FILTER, 
@@ -66,6 +66,10 @@ class QueryPlanCriticConfig(LanceQueryPlanAgentConfig):
     Here is how you must examine the QUERY PLAN + ANSWER:
     - ALL filtering conditions in the original query must be EXPLICITLY 
       mentioned in the FILTER, and the QUERY field should not be used for filtering.
+    - If the ANSWER contains an ERROR message, then this means that the query
+      plan execution FAILED, and your feedback should say INVALID along 
+      with the ERROR message, `suggested_fix` that aims to help the assistant 
+      fix the problem (or simply equals "address the the error shown in feedback")
     - If the ANSWER is in the expected form, then the QUERY PLAN is likely VALID,
       and your feedback should say VALID, with empty `suggested_fix`.
     - If the ANSWER is {NO_ANSWER} or of the wrong form, 
@@ -84,6 +88,10 @@ class QueryPlanCriticConfig(LanceQueryPlanAgentConfig):
       - If the REPHRASED QUERY looks correct, then check if the FILTER makes sense.
         REMEMBER: A filter should ONLY be used if EXPLICITLY REQUIRED BY THE QUERY.
      
+     
+     IMPORTANT!! The DATAFRAME CALCULATION is done AFTER applying the 
+         FILTER and REPHRASED QUERY! Keep this in mind when evaluating 
+         the correctness of the DATAFRAME CALCULATION.
     
     ALWAYS use `query_plan_feedback` tool/fn to present your feedback
     in the `feedback` field, and if any fix is suggested,

{langroid-0.1.244 → langroid-0.1.246}/langroid/agent/special/lance_rag/query_planner_agent.py

@@ -67,6 +67,9 @@ class LanceQueryPlanAgentConfig(ChatAgentConfig):
         or EMPTY string if no calc is needed. 
         The dataframe calc CAN refer to the `content` field.
         If a DataFrame calculation is NOT needed, leave this field EMPTY.
+        
+        IMPORTANT: The DataFrame `df` in this calculation is the result of 
+        applying the FILTER AND REPHRASED QUERY to the documents.
     
     
     EXAMPLE:
@@ -87,7 +90,9 @@ class LanceQueryPlanAgentConfig(ChatAgentConfig):
          ASSISTANT does not know about them and only uses the query to 
          match the CONTENT of the docs.]
     DATAFRAME CALCULATION: "df["num_deaths"].sum()"
-
+        NOTE!!! The DataFrame `df` in this calculation is the result of
+        applying the FILTER AND REPHRASED QUERY to the documents, 
+        hence this computation will give the total deaths in shoplifting crimes.
     ------------- END OF EXAMPLE ----------------
     
     The FILTER must be a SQL-like condition, e.g. 

{langroid-0.1.244 → langroid-0.1.246}/langroid/agent/special/table_chat_agent.py

@@ -143,6 +143,13 @@ class PandasEvalTool(ToolMessage):
             cls(expression="df[(df['gender'] == 'Male')]['income'].mean()"),
         ]
 
+    @classmethod
+    def instructions(cls) -> str:
+        return """
+            Use the `pandas_eval` tool/function to evaluate a pandas expression
+            involving the dataframe 'df' to answer the user's question.
+            """
+
 
 class TableChatAgent(ChatAgent):
     """

{langroid-0.1.244 → langroid-0.1.246}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "langroid"
-version = "0.1.244"
+version = "0.1.246"
 description = "Harness LLMs with Multi-Agent Programming"
 authors = ["Prasad Chalasani <pchalasani@gmail.com>"]
 readme = "README.md"