nvidia-nat 1.2.0a20250813__py3-none-any.whl → 1.2.0rc6__py3-none-any.whl

nat/tool/code_execution/test_code_execution_sandbox.py

@@ -50,7 +50,7 @@ class TestCodeExecutionSandbox:
         except (ConnectionError, Timeout, RequestException):
             pytest.skip(
                 f"Sandbox server is not running at {sandbox_config['url']}. "
-                "Please start it with: cd src/aiq/tool/code_execution/local_sandbox && ./start_local_sandbox.sh")
+                "Please start it with: cd src/nat/tool/code_execution/local_sandbox && ./start_local_sandbox.sh")
 
     def execute_code(self, sandbox_config: dict[str, Any], code: str, language: str = "python") -> dict[str, Any]:
         """

nat/tool/mcp/exceptions.py

@@ -108,7 +108,7 @@ class MCPToolNotFoundError(MCPError):
                          url=url,
                          category=MCPErrorCategory.TOOL_NOT_FOUND,
                          suggestions=[
-                             "Use 'aiq info mcp --detail' to see available tools",
+                             "Use 'nat info mcp --detail' to see available tools",
                              "Check that the tool name is spelled correctly"
                          ],
                          original_exception=original_exception)

nat/tool/mcp/mcp_tool.py

@@ -50,7 +50,7 @@ class MCPToolConfig(FunctionBaseConfig, name="mcp_tool_wrapper"):
 @register_function(config_type=MCPToolConfig)
 async def mcp_tool(config: MCPToolConfig, builder: Builder):  # pylint: disable=unused-argument
     """
-    Generate an AIQ Toolkit Function that wraps a tool provided by the MCP server.
+    Generate a NAT Function that wraps a tool provided by the MCP server.
     """
 
     from nat.tool.mcp.mcp_client import MCPBuilder

nat/tool/retriever.py

@@ -30,9 +30,9 @@ from nat.retriever.models import RetrieverOutput
 logger = logging.getLogger(__name__)
 
 
-class RetrieverConfig(FunctionBaseConfig, name="aiq_retriever"):
+class RetrieverConfig(FunctionBaseConfig, name="nat_retriever"):
     """
-    AIQRetriever tool which provides a common interface for different vectorstores. Its
+    Retriever tool which provides a common interface for different vectorstores. Its
     configuration uses clients, which are the vectorstore-specific implementaiton of the retriever interface.
     """
     retriever: RetrieverRef = Field(description="The retriever instance name from the workflow configuration object.")
@@ -58,7 +58,7 @@ def _get_description_from_config(config: RetrieverConfig) -> str:
 @register_function(config_type=RetrieverConfig)
 async def retriever_tool(config: RetrieverConfig, builder: Builder):
     """
-    Configure an AIQ Toolkit Retriever Tool which supports different clients such as Milvus and Nemo Retriever.
+    Configure a NAT Retriever Tool which supports different clients such as Milvus and Nemo Retriever.
 
     Args:
         config: A config object with required parameters 'client' and 'client_config'

nat/tool/server_tools.py

@@ -38,18 +38,18 @@ async def current_request_attributes(config: RequestAttributesTool, builder: Bui
     async def _get_request_attributes(unused: str) -> str:
 
         from nat.builder.context import Context
-        aiq_context = Context.get()
+        nat_context = Context.get()
 
-        method: str | None = aiq_context.metadata.method
-        url_path: str | None = aiq_context.metadata.url_path
-        url_scheme: str | None = aiq_context.metadata.url_scheme
-        headers: Headers | None = aiq_context.metadata.headers
-        query_params: QueryParams | None = aiq_context.metadata.query_params
-        path_params: dict[str, str] | None = aiq_context.metadata.path_params
-        client_host: str | None = aiq_context.metadata.client_host
-        client_port: int | None = aiq_context.metadata.client_port
-        cookies: dict[str, str] | None = aiq_context.metadata.cookies
-        conversation_id: str | None = aiq_context.conversation_id
+        method: str | None = nat_context.metadata.method
+        url_path: str | None = nat_context.metadata.url_path
+        url_scheme: str | None = nat_context.metadata.url_scheme
+        headers: Headers | None = nat_context.metadata.headers
+        query_params: QueryParams | None = nat_context.metadata.query_params
+        path_params: dict[str, str] | None = nat_context.metadata.path_params
+        client_host: str | None = nat_context.metadata.client_host
+        client_port: int | None = nat_context.metadata.client_port
+        cookies: dict[str, str] | None = nat_context.metadata.cookies
+        conversation_id: str | None = nat_context.conversation_id
 
         return (f"Method: {method}, "
                 f"URL Path: {url_path}, "

nat/utils/settings/global_settings.py

@@ -66,7 +66,7 @@ def configure_registry_channel(config_type: RegistryHandlerBaseConfig, channel_n
 
 
 def add_channel_interative(channel_type: str) -> None:
-    """Add a remote registry channel to publish/search/pull AIQ Toolkit plugin packages.
+    """Add a remote registry channel to publish/search/pull NAT plugin packages.
 
     Args:
         channel_type (str): They type of channel to configure.

{nvidia_nat-1.2.0a20250813.dist-info → nvidia_nat-1.2.0rc6.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: nvidia-nat
-Version: 1.2.0a20250813
+Version: 1.2.0rc6
 Summary: NVIDIA NeMo Agent toolkit
 Author: NVIDIA Corporation
 Maintainer: NVIDIA Corporation
@@ -320,11 +320,11 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-![NVIDIA NeMo Agent Toolkit](https://media.githubusercontent.com/media/NVIDIA/NeMo-Agent-Toolkit/refs/heads/main/docs/source/_static/aiqtoolkit_banner.png "NeMo Agent toolkit banner image")
+![NVIDIA NeMo Agent Toolkit](https://media.githubusercontent.com/media/NVIDIA/NeMo-Agent-Toolkit/refs/heads/main/docs/source/_static/banner.png "NeMo Agent toolkit banner image")
 
 # NVIDIA NeMo Agent Toolkit
 
-AIQ toolkit is a flexible library designed to seamlessly integrate your enterprise agents—regardless of framework—with various data sources and tools. By treating agents, tools, and agentic workflows as simple function calls, AIQ toolkit enables true composability: build once and reuse anywhere.
+NeMo Agent toolkit is a flexible library designed to seamlessly integrate your enterprise agents—regardless of framework—with various data sources and tools. By treating agents, tools, and agentic workflows as simple function calls, NeMo Agent toolkit enables true composability: build once and reuse anywhere.
 
 ## Key Features
 
@@ -334,16 +334,16 @@ AIQ toolkit is a flexible library designed to seamlessly integrate your enterpri
 - [**Profiling:**](https://docs.nvidia.com/nemo/agent-toolkit/1.2.0/workflows/profiler.html) Profile entire workflows down to the tool and agent level, track input/output tokens and timings, and identify bottlenecks.
 - [**Observability:**](https://docs.nvidia.com/nemo/agent-toolkit/1.2.0/workflows/observe/observe-workflow-with-phoenix.html) Monitor and debug your workflows with any OpenTelemetry-compatible observability tool, with examples using [Phoenix](https://docs.nvidia.com/nemo/agent-toolkit/1.2.0/workflows/observe/observe-workflow-with-phoenix.html) and [W&B Weave](https://docs.nvidia.com/nemo/agent-toolkit/1.2.0/workflows/observe/observe-workflow-with-weave.html).
 - [**Evaluation System:**](https://docs.nvidia.com/nemo/agent-toolkit/1.2.0/workflows/evaluate.html) Validate and maintain accuracy of agentic workflows with built-in evaluation tools.
-- [**User Interface:**](https://docs.nvidia.com/nemo/agent-toolkit/1.2.0/quick-start/launching-ui.html) Use the AIQ toolkit UI chat interface to interact with your agents, visualize output, and debug workflows.
-- [**MCP Compatibility**](https://docs.nvidia.com/nemo/agent-toolkit/1.2.0/workflows/mcp/mcp-client.html) Compatible with Model Context Protocol (MCP), allowing tools served by MCP Servers to be used as AIQ toolkit functions.
+- [**User Interface:**](https://docs.nvidia.com/nemo/agent-toolkit/1.2.0/quick-start/launching-ui.html) Use the NeMo Agent toolkit UI chat interface to interact with your agents, visualize output, and debug workflows.
+- [**MCP Compatibility**](https://docs.nvidia.com/nemo/agent-toolkit/1.2.0/workflows/mcp/mcp-client.html) Compatible with Model Context Protocol (MCP), allowing tools served by MCP Servers to be used as NeMo Agent toolkit functions.
 
-With AIQ toolkit, you can move quickly, experiment freely, and ensure reliability across all your agent-driven projects.
+With NeMo Agent toolkit, you can move quickly, experiment freely, and ensure reliability across all your agent-driven projects.
 
 ## Links
- * [Documentation](https://docs.nvidia.com/nemo/agent-toolkit/1.2.0/index.html): Explore the full documentation for AIQ toolkit.
+ * [Documentation](https://docs.nvidia.com/nemo/agent-toolkit/1.2.0/index.html): Explore the full documentation for NeMo Agent toolkit.
 
 ## First time user?
- If this is your first time using AIQ toolkit, it is recommended to install the latest version from the [source repository](https://github.com/NVIDIA/NeMo-Agent-Toolkit?tab=readme-ov-file#quick-start) on GitHub. This package is intended for users who are familiar with AIQ toolkit applications and need to add AIQ toolkit as a dependency to their project.
+ If this is your first time using NeMo Agent toolkit, it is recommended to install the latest version from the [source repository](https://github.com/NVIDIA/NeMo-Agent-Toolkit?tab=readme-ov-file#quick-start) on GitHub. This package is intended for users who are familiar with NeMo Agent toolkit applications and need to add NeMo Agent toolkit as a dependency to their project.
 
 ## Feedback
 
@@ -351,7 +351,7 @@ We would love to hear from you! Please file an issue on [GitHub](https://github.
 
 ## Acknowledgements
 
-We would like to thank the following open source projects that made AIQ toolkit possible:
+We would like to thank the following open source projects that made NeMo Agent toolkit possible:
 
 - [CrewAI](https://github.com/crewAIInc/crewAI)
 - [FastAPI](https://github.com/tiangolo/fastapi)