unique_toolkit 1.62.1__tar.gz → 1.62.3__tar.gz

{unique_toolkit-1.62.1 → unique_toolkit-1.62.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: unique-toolkit
-Version: 1.62.1
+Version: 1.62.3
 Summary: 
 Author: Cedric Klinkert, Martin Fadler, Sadique Sheik, Fabian Schläpfer, Pascal Hauri, Ejiroghene Oki-Peter, Rami Azouz, Ricardo Visini, Sanzio Monti
 Author-email: Cedric Klinkert <cedric.klinkert@unique.ch>, Martin Fadler <martin.fadler@unique.ch>, Sadique Sheik <sadique@unique.ch>, Fabian Schläpfer <fabian@unique.ch>, Pascal Hauri <pascal@unique.ch>, Ejiroghene Oki-Peter <oki-peter.ejiroghene@unique.ai>, Rami Azouz <rami.ext@unique.ch>, Ricardo Visini <ricardo.visini@unique.ch>, Sanzio Monti <sanzio.monti@unique.ai>

{unique_toolkit-1.62.1 → unique_toolkit-1.62.3}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "unique_toolkit"
-version = "1.62.1"
+version = "1.62.3"
 description = ""
 readme = "README.md"
 requires-python = ">=3.12"

{unique_toolkit-1.62.1 → unique_toolkit-1.62.3}/unique_toolkit/agentic/history_manager/history_manager.py

@@ -347,10 +347,10 @@ class HistoryManager:
 def _strip_uncited_sources_from_content(content: str, cited: set[int]) -> str:
     """Filter a tool response content string to only keep cited source items.
 
-    The content is expected to be a JSON array of
-    ``{"source_number": N, "content": "..."}`` dicts.  Items whose
-    ``source_number`` is not in *cited* are removed.  If the content is
-    not in the expected JSON format it is returned unchanged.
+    The content is expected to be a JSON array of dicts containing at least
+    a "source_number" key.  Items whose "source_number" is not in *cited*
+    are removed.  If the content is not valid JSON or not in the expected
+    format it is returned unchanged.
     """
     try:
         data = json.loads(content)

{unique_toolkit-1.62.1 → unique_toolkit-1.62.3}/unique_toolkit/agentic/history_manager/loop_token_reducer.py

@@ -685,6 +685,7 @@ class LoopTokenReducer:
         sources = [
             {
                 "source_number": source_offset + i,
+                "content_id": chunk.id,
                 "content": chunk.text,
             }
             for i, chunk in enumerate(content_chunks)

{unique_toolkit-1.62.1 → unique_toolkit-1.62.3}/unique_toolkit/agentic/history_manager/utils.py

@@ -75,6 +75,7 @@ def transform_chunks_to_string(
     sources: list[dict[str, Any]] = [
         {
             "source_number": max_source_number + i,
+            "content_id": chunk.id,
             "content": chunk.text,
         }
         for i, chunk in enumerate(content_chunks)

{unique_toolkit-1.62.1 → unique_toolkit-1.62.3}/unique_toolkit/agentic/tools/openai_builtin/code_interpreter/config.py

@@ -25,6 +25,7 @@ Instructions:
 Uploaded and generated files:
 - All files uploaded to the chat are available at the path `/mnt/data/<filename>`.
 - All files generated through code MUST be saved in the `/mnt/data` folder.
+- CRITICAL: When generating any plot or visualization, the code MUST call `plt.savefig('/mnt/data/<filename>.png', bbox_inches='tight')` and `plt.close()` to save the file. Never rely on `plt.show()` alone — a file that is not saved to `/mnt/data/` cannot be displayed.
 
 CRUCIAL Instructions for displaying images and files in the chat:
 - Once files are generated in the `/mnt/data` folder you MUST reference them in the chat using markdown syntax in order to display them in the chat.
@@ -46,6 +47,8 @@ Always use a line break between the title and the markdown!
 
 Handling User Queries:
 - Whenever the user query requires using the python tool, you must always think first about the steps required.
+- CRITICAL: If any step generates a plot or visualization, that code block MUST include `plt.savefig('/mnt/data/<filename>.png', bbox_inches='tight')` and `plt.close()` as the final lines. Code that only calls `plt.show()` without saving will NOT display the image to the user.
+- CRITICAL: NEVER reference a `sandbox:/mnt/data/<filename>` link unless you have already executed code in this response that saved that exact file. Referencing a file that was not created by executed code will result in a broken link.
 - Use the tool multiple times:
     - You MUST NOT guess anything about the structure of the data / files uploaded. Rather, you MUST perform some data exploration first.
         - Example: User uploads an excel files and asks a question about it. First Read the data, explore the columns, columns types, etc. Then use the tool to answer the user's query.
@@ -66,6 +69,7 @@ Instructions:
 Uploaded and generated files:
 - All files uploaded to the chat are available at the path `/mnt/data/<filename>`.
 - All files generated through code MUST be saved in the `/mnt/data` folder.
+- CRITICAL: When generating any plot or visualization, the code MUST call `plt.savefig('/mnt/data/<filename>.png', bbox_inches='tight')` and `plt.close()` to save the file. Never rely on `plt.show()` alone — a file that is not saved to `/mnt/data/` cannot be displayed.
 
 CRUCIAL Instructions for displaying images and files in the chat:
 - Once files are generated in the `/mnt/data` folder you MUST reference them in the chat using markdown syntax in order to display them in the chat.
@@ -89,6 +93,8 @@ IMPORTANT: ALWAYS place a blank line before AND after each file reference link s
 
 Handling User Queries:
 - Whenever the user query requires using the python tool, you must always think first about the steps required.
+- CRITICAL: If any step generates a plot or visualization, that code block MUST include `plt.savefig('/mnt/data/<filename>.png', bbox_inches='tight')` and `plt.close()` as the final lines. Code that only calls `plt.show()` without saving will NOT display the image to the user.
+- CRITICAL: NEVER reference a `sandbox:/mnt/data/<filename>` link unless you have already executed code in this response that saved that exact file. Referencing a file that was not created by executed code will result in a broken link.
 - Use the tool multiple times:
     - You MUST NOT guess anything about the structure of the data / files uploaded. Rather, you MUST perform some data exploration first.
         - Example: User uploads an excel files and asks a question about it. First Read the data, explore the columns, columns types, etc. Then use the tool to answer the user's query.