langroid 0.2.4__tar.gz → 0.2.6__tar.gz

{langroid-0.2.4 → langroid-0.2.6}/PKG-INFO

@@ -1,15 +1,16 @@
 Metadata-Version: 2.1
 Name: langroid
-Version: 0.2.4
+Version: 0.2.6
 Summary: Harness LLMs with Multi-Agent Programming
 License: MIT
 Author: Prasad Chalasani
 Author-email: pchalasani@gmail.com
-Requires-Python: >=3.10,<3.12
+Requires-Python: >=3.10,<4.0
 Classifier: License :: OSI Approved :: MIT License
 Classifier: Programming Language :: Python :: 3
 Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
 Provides-Extra: all
 Provides-Extra: chainlit
 Provides-Extra: chromadb
@@ -149,7 +150,7 @@ This Multi-Agent paradigm is inspired by the
 `Langroid` is a fresh take on LLM app-development, where considerable thought has gone 
 into simplifying the developer experience; it does not use `Langchain`.
 
-Companies are using/adapting Langroid in production. Here is a quote from one of them:
+📢 Companies are using/adapting Langroid in **production**. Here is a quote:
 
 >[Nullify](https://www.nullify.ai) uses AI Agents for secure software development. 
 > It finds, prioritizes and fixes vulnerabilities. We have internally adapted Langroid's multi-agent orchestration framework in production, after evaluating CrewAI, Autogen, LangChain, Langflow, etc. We found Langroid to be far superior to those frameworks in terms of ease of setup and flexibility. Langroid's Agent and Task abstractions are intuitive, well thought out, and provide a great developer  experience. We wanted the quickest way to get something in production. With other frameworks it would have taken us weeks, but with Langroid we got to good results in minutes. Highly recommended! <br> -- Jacky Wong, Head of AI at Nullify.
@@ -460,17 +461,17 @@ such as [ollama](https://github.com/ollama), [oobabooga](https://github.com/ooba
 - **Observability, Logging, Lineage:** Langroid generates detailed logs of multi-agent interactions and
   maintains provenance/lineage of messages, so that you can trace back
   the origin of a message.
-- **[Tools/Plugins/Function-calling](https://langroid.github.io/langroid/quick-start/chat-agent-tool/)**: Langroid supports OpenAI's recently
-  released [function calling](https://platform.openai.com/docs/guides/gpt/function-calling)
-  feature. In addition, Langroid has its own native equivalent, which we
-  call **tools** (also known as "plugins" in other contexts). Function
-  calling and tools have the same developer-facing interface, implemented
+- **[Tools/Plugins/Function-calling](https://langroid.github.io/langroid/quick-start/chat-agent-tool/)**:
+  Langroid supports OpenAI's [function calling](https://platform.openai.com/docs/guides/gpt/function-calling), as
+  well as an equivalent `ToolMessage` mechanism which works with
+  any LLM, not just OpenAI's.
+  Function calling and tools have the same developer-facing interface, implemented
   using [Pydantic](https://docs.pydantic.dev/latest/),
   which makes it very easy to define tools/functions and enable agents
   to use them. Benefits of using Pydantic are that you never have to write
   complex JSON specs for function calling, and when the LLM
   hallucinates malformed JSON, the Pydantic error message is sent back to
-  the LLM so it can fix it!
+  the LLM so it can fix it.
 
 --- 
 

{langroid-0.2.4 → langroid-0.2.6}/README.md

@@ -46,7 +46,7 @@ This Multi-Agent paradigm is inspired by the
 `Langroid` is a fresh take on LLM app-development, where considerable thought has gone 
 into simplifying the developer experience; it does not use `Langchain`.
 
-Companies are using/adapting Langroid in production. Here is a quote from one of them:
+📢 Companies are using/adapting Langroid in **production**. Here is a quote:
 
 >[Nullify](https://www.nullify.ai) uses AI Agents for secure software development. 
 > It finds, prioritizes and fixes vulnerabilities. We have internally adapted Langroid's multi-agent orchestration framework in production, after evaluating CrewAI, Autogen, LangChain, Langflow, etc. We found Langroid to be far superior to those frameworks in terms of ease of setup and flexibility. Langroid's Agent and Task abstractions are intuitive, well thought out, and provide a great developer  experience. We wanted the quickest way to get something in production. With other frameworks it would have taken us weeks, but with Langroid we got to good results in minutes. Highly recommended! <br> -- Jacky Wong, Head of AI at Nullify.
@@ -357,17 +357,17 @@ such as [ollama](https://github.com/ollama), [oobabooga](https://github.com/ooba
 - **Observability, Logging, Lineage:** Langroid generates detailed logs of multi-agent interactions and
   maintains provenance/lineage of messages, so that you can trace back
   the origin of a message.
-- **[Tools/Plugins/Function-calling](https://langroid.github.io/langroid/quick-start/chat-agent-tool/)**: Langroid supports OpenAI's recently
-  released [function calling](https://platform.openai.com/docs/guides/gpt/function-calling)
-  feature. In addition, Langroid has its own native equivalent, which we
-  call **tools** (also known as "plugins" in other contexts). Function
-  calling and tools have the same developer-facing interface, implemented
+- **[Tools/Plugins/Function-calling](https://langroid.github.io/langroid/quick-start/chat-agent-tool/)**:
+  Langroid supports OpenAI's [function calling](https://platform.openai.com/docs/guides/gpt/function-calling), as
+  well as an equivalent `ToolMessage` mechanism which works with
+  any LLM, not just OpenAI's.
+  Function calling and tools have the same developer-facing interface, implemented
   using [Pydantic](https://docs.pydantic.dev/latest/),
   which makes it very easy to define tools/functions and enable agents
   to use them. Benefits of using Pydantic are that you never have to write
   complex JSON specs for function calling, and when the LLM
   hallucinates malformed JSON, the Pydantic error message is sent back to
-  the LLM so it can fix it!
+  the LLM so it can fix it.
 
 --- 
 

{langroid-0.2.4 → langroid-0.2.6}/langroid/agent/task.py

@@ -41,7 +41,6 @@ from langroid.parsing.routing import parse_addressed_message
 from langroid.pydantic_v1 import BaseModel
 from langroid.utils.configuration import settings
 from langroid.utils.constants import (
-    AT,  # regex for start of an addressed recipient e.g. "@"
     DONE,
     NO_ANSWER,
     PASS,
@@ -74,6 +73,18 @@ class TaskConfig(BaseModel):
         inf_loop_wait_factor (int): wait this * cycle_len msgs before loop-check
         restart_subtask_run (bool): whether to restart *every* run of this task
             when run as a subtask.
+        addressing_prefix (str): prefix an agent can use to address other
+            agents, or entities of the agent. E.g., if this is "@", the addressing
+            string would be "@Alice", or "@user", "@llm", "@agent", etc.
+            If this is an empty string, then addressing is disabled.
+            Default is empty string "".
+            CAUTION: this is a deprecated practice, since normal prompts
+            can accidentally contain such addressing prefixes, and will break
+            your runs. This could happen especially when your prompt/context
+            contains code, but of course could occur in normal text as well.
+            Instead, use the `RecipientTool` to have agents address other agents or
+            entities. If you do choose to use `addressing_prefix`, the recommended
+            setting is to use `langroid.utils.constants.AT`, which currently is "|@|".
     """
 
     inf_loop_cycle_len: int = 10
@@ -81,6 +92,7 @@ class TaskConfig(BaseModel):
     inf_loop_wait_factor: int = 5
     restart_as_subtask: bool = False
     logs_dir: str = "logs"
+    addressing_prefix: str = ""
 
 
 class Task:
@@ -1190,7 +1202,10 @@ class Task:
         if result is None:
             return None
         # if result content starts with @name, set recipient to name
-        is_pass, recipient, content = parse_routing(result)
+        is_pass, recipient, content = parse_routing(
+            result,
+            addressing_prefix=self.config.addressing_prefix,
+        )
         if is_pass is None:  # no routing, i.e. neither PASS nor SEND
             return result
         if is_pass:
@@ -1648,6 +1663,7 @@ class Task:
 
 def parse_routing(
     msg: ChatDocument | str,
+    addressing_prefix: str = "",
 ) -> Tuple[bool | None, str | None, str | None]:
     """
     Parse routing instruction if any, of the form:
@@ -1656,6 +1672,8 @@ def parse_routing(
     @<recipient> <content> (send content to recipient)
     Args:
         msg (ChatDocument|str|None): message to parse
+        addressing_prefix (str): prefix to address other agents or entities,
+             (e.g. "@". See documentation of `TaskConfig` for details).
     Returns:
         Tuple[bool|None, str|None, str|None]:
             bool: true=PASS, false=SEND, or None if neither
@@ -1682,8 +1700,12 @@ def parse_routing(
         else:
             return False, addressee, content_to_send
     if (
-        AT in content
-        and (addressee_content := parse_addressed_message(content, AT))[0] is not None
+        addressing_prefix != ""
+        and addressing_prefix in content
+        and (addressee_content := parse_addressed_message(content, addressing_prefix))[
+            0
+        ]
+        is not None
     ):
         (addressee, content_to_send) = addressee_content
         # if no content then treat same as PASS_TO

{langroid-0.2.4 → langroid-0.2.6}/langroid/mytypes.py

@@ -22,11 +22,17 @@ class Entity(str, Enum):
     SYSTEM = "System"
 
     def __eq__(self, other: object) -> bool:
-        """Allow case-insensitive comparison with strings."""
+        """Allow case-insensitive equality (==) comparison with strings."""
+        if other is None:
+            return False
         if isinstance(other, str):
             return self.value.lower() == other.lower()
         return super().__eq__(other)
 
+    def __ne__(self, other: object) -> bool:
+        """Allow case-insensitive non-equality (!=) comparison with strings."""
+        return not self.__eq__(other)
+
     def __hash__(self) -> int:
         """Override this to ensure hashability of the enum,
         so it can be used sets and dictionary keys.

{langroid-0.2.4 → langroid-0.2.6}/langroid/utils/constants.py

@@ -18,6 +18,11 @@ DONE = "DONE"
 USER_QUIT_STRINGS = ["q", "x", "quit", "exit", "bye", DONE]
 PASS = "__PASS__"
 PASS_TO = PASS + ":"
-SEND_TO = "SEND:"
+SEND_TO = "__SEND__:"
 TOOL = "TOOL"
-AT = "@"
+# This is a recommended setting for TaskConfig.addressing_prefix if using it at all;
+# prefer to use `RecipientTool` to allow agents addressing others.
+# Caution the AT string should NOT contain any 'word' characters, i.e.
+# it no letters, digits or underscores.
+# See tests/main/test_msg_routing for example usage
+AT = "|@|"

{langroid-0.2.4 → langroid-0.2.6}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "langroid"
-version = "0.2.4"
+version = "0.2.6"
 description = "Harness LLMs with Multi-Agent Programming"
 authors = ["Prasad Chalasani <pchalasani@gmail.com>"]
 readme = "README.md"
@@ -10,7 +10,7 @@ include = ["pyproject.toml"]
 
 # =============== MAIN DEPS ==============
 [tool.poetry.dependencies]
-python = ">=3.10,<3.12"
+python = "^3.10"
 
 # =========== OPTIONALS ==============================
 chromadb = {version=">=0.4.21, <=0.4.23", optional=true}