unique-toolkit 2026.24.0.dev0__tar.gz → 2026.24.0.dev2__tar.gz

{unique_toolkit-2026.24.0.dev0 → unique_toolkit-2026.24.0.dev2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: unique-toolkit
-Version: 2026.24.0.dev0
+Version: 2026.24.0.dev2
 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>
@@ -16,7 +16,7 @@ Requires-Dist: sseclient>=0.0.27,<0.0.28
 Requires-Dist: openai>=1.105.0,<3
 Requires-Dist: platformdirs>=4.0.0,<5
 Requires-Dist: pillow>=12.1.1
-Requires-Dist: unique-sdk>=2026.24.0.dev0,<2026.24.0rc0
+Requires-Dist: unique-sdk>=2026.24.0.dev2,<2026.24.0rc0
 Requires-Dist: jambo>=0.1.2,<0.2
 Requires-Dist: jinja2>=3.1.6,<4
 Requires-Dist: docxtpl>=0.20.1,<0.21

{unique_toolkit-2026.24.0.dev0 → unique_toolkit-2026.24.0.dev2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "unique_toolkit"
-version = "2026.24.0.dev0"
+version = "2026.24.0.dev2"
 description = ""
 readme = "README.md"
 requires-python = ">=3.12"
@@ -28,7 +28,7 @@ dependencies = [
     "openai>=1.105.0,<3",
     "platformdirs>=4.0.0,<5",
     "pillow>=12.1.1",
-    "unique-sdk>=2026.24.0.dev0,<2026.24.0rc0",
+    "unique-sdk>=2026.24.0.dev2,<2026.24.0rc0",
     "jambo>=0.1.2,<0.2",
     "jinja2>=3.1.6,<4",
     "docxtpl>=0.20.1,<0.21",

{unique_toolkit-2026.24.0.dev0 → unique_toolkit-2026.24.0.dev2}/unique_toolkit/agentic/tools/openai_builtin/code_interpreter/config.py

@@ -147,6 +147,7 @@ HTML files — CRITICAL rules:
     - The main content container MUST have a bounded, measurable height. For charts/dashboards either (a) give the chart container an explicit pixel height (e.g. `height: 500px`) or (b) use `aspect-ratio` together with a `width` so height is derived. Do NOT leave the top-level container with no intrinsic height.
     - Do NOT use `position: fixed` or `position: absolute` on top-level layout elements — they remove the element from the flow and the iframe cannot measure it.
     - Plotly users — CRITICAL: Plotly's `fig.write_html(...)` / `fig.to_html(...)` defaults emit a `<div class="plotly-graph-div" style="height:100%; width:100%;">` with no wrapper height (iframe collapse) **and** inline the entire Plotly JS bundle (~3MB), which often fails KB upload. You MUST pass `include_plotlyjs="cdn"`, `full_html=True`, and `default_height` (and `default_width` when relevant). Example: `fig.write_html(path, full_html=True, include_plotlyjs="cdn", default_height="600px")`. If you hand-write the wrapper HTML around a Plotly div, wrap the `plotly-graph-div` in a container with an explicit pixel height and never leave the graph div at `height:100%`.
+    - Plotly header overlap — CRITICAL: When a chart combines a horizontal legend positioned above the axes (`legend.y > 1`), range-selector buttons (`rangeselector`), and subplot title annotations, all three compete for the same top region and will overlap unless you reserve enough space. Rules: (1) set `fig.update_layout(margin=dict(t=150))` (or more) whenever any two of those elements coexist; (2) place a horizontal legend at `y=1.15` or higher (not `y=1.0`–`1.05`) so it clears the range-selector row; (3) for annotation-based subplot titles use `y` values ≥ 0.05 above the legend's `y` value; (4) if a chart also has range-sliders at the bottom, add sufficient bottom margin (`margin.b ≥ 80`) to avoid clipping the slider. Never rely on Plotly's default top margin of 80 px when the header contains more than a single title.
     - Single-chart HTML files — always add an outer wrapper with an explicit `height` (e.g. `<div style="height:600px">…chart…</div>`) so the document has a non-zero intrinsic height, even if the chart library defaults to percentage sizing.
   - Apply clean, readable typography: prefer system fonts (`-apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif`) and sufficient contrast (WCAG AA minimum).
   - Use semantic HTML elements (`<table>` for tabular data, `<button>` for actions, `<h1>`–`<h6>` for headings, `alt` attributes on `<img>` tags). Avoid using `<div>` for everything.
@@ -160,6 +161,7 @@ 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 as a PNG, use **matplotlib** — 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.
+  - Self-check before writing any sandbox link: look back at the code blocks you executed in this response. Is there a block that explicitly saves this exact filename to `/mnt/data/`? If not, execute the code first — then reference the file.
 - CRITICAL: The sandbox has NO internet access. NEVER use `requests`, `httpx`, `urllib`, or any other HTTP library to fetch data from the web — these calls will always fail. If the user's query requires live web data (e.g. market prices, news, APIs), you MUST retrieve it using the web search tool first and then pass the result into the code interpreter.
 - CRITICAL: For Excel files (`.xls`, `.xlsx`) and CSV files uploaded to the chat, ALWAYS use this tool to read and process them (e.g. `pandas.read_excel`, `pandas.read_csv`, `openpyxl`). Do NOT rely on the chat's text content or prior ingestion for spreadsheet data — the raw file contents are only accessible via code execution from `/mnt/data/<filename>`.
 - For calculation, retrieval, or exploratory-analysis answers, return the result concisely in the chat as markdown (key numbers inline, short tables where useful). Do NOT produce a separate artifact file (HTML, PDF, etc.) unless the user explicitly asked for a downloadable output or the request clearly calls for a dashboard/report.

{unique_toolkit-2026.24.0.dev0 → unique_toolkit-2026.24.0.dev2}/unique_toolkit/agentic/tools/openai_builtin/code_interpreter/postprocessors/generated_files.py

@@ -620,13 +620,16 @@ class DisplayCodeInterpreterFilesPostProcessor(
                 self._log.info("Fence injection modified the message text")
 
         _warn_missing_content_ids(loop_response.message.text or "", self._content_map)
+        ci_ran = bool(loop_response.code_interpreter_calls)
         loop_response.message.text, dangling_replaced = _replace_dangling_sandbox_links(
-            loop_response.message.text
+            loop_response.message.text, ci_ran=ci_ran
         )
         changed |= dangling_replaced
         if dangling_replaced:
             self._log.warning(
-                "apply_postprocessing found and replaced dangling sandbox links"
+                "apply_postprocessing found and replaced dangling sandbox links "
+                "(ci_ran=%s)",
+                ci_ran,
             )
 
         apply_ms = (time.monotonic() - apply_t0) * 1000
@@ -1254,7 +1257,9 @@ _SANDBOX_MARKDOWN_LINK_RE = re.compile(r"!?\[.*?\]\(sandbox:/mnt/data/\S+?\)")
 _SANDBOX_FILENAME_RE = re.compile(r"sandbox:/mnt/data/([^)\s]+)")
 
 
-def _replace_dangling_sandbox_links(text: str) -> tuple[str, bool]:
+def _replace_dangling_sandbox_links(
+    text: str, *, ci_ran: bool = True
+) -> tuple[str, bool]:
     """Replace any remaining sandbox:/mnt/data/ markdown links with a per-file notice.
 
     A dangling link means either the LLM hallucinated a file reference (the sandbox
@@ -1263,6 +1268,12 @@ def _replace_dangling_sandbox_links(text: str) -> tuple[str, bool]:
     cases the user would see a broken link; this function replaces each such link with
     an actionable message that names the specific file, and logs a warning so the
     incident is visible in production logs.
+
+    Args:
+        text: The message text to scan for dangling sandbox links.
+        ci_ran: Whether the code interpreter was called at all this turn.  When
+            ``False`` the LLM emitted a sandbox link without invoking the tool
+            (hallucination); a more accurate message is shown to the user.
     """
     if not _SANDBOX_MARKDOWN_LINK_RE.search(text):
         return text, False
@@ -1271,11 +1282,17 @@ def _replace_dangling_sandbox_links(text: str) -> tuple[str, bool]:
         filename_match = _SANDBOX_FILENAME_RE.search(m.group())
         filename = filename_match.group(1) if filename_match else "the file"
         logger.warning(
-            "Dangling sandbox link found in final text: '%s'. "
-            "The file was either never uploaded or the link format did not match "
+            "Dangling sandbox link found in final text: '%s'. ci_ran=%s. "
+            "The file was either never generated or the link format did not match "
             "the expected pattern — replacing with per-file notice.",
             m.group(),
+            ci_ran,
         )
+        if not ci_ran:
+            return (
+                f"⚠️ The file *{filename}* was not generated. "
+                "Please ask me to create it."
+            )
         return f"⚠️ The file *{filename}* could not be retrieved. You can ask me to regenerate it."
 
     return _SANDBOX_MARKDOWN_LINK_RE.sub(_replacement, text), True