unique_toolkit 1.65.0__tar.gz → 1.65.1__tar.gz

{unique_toolkit-1.65.0 → unique_toolkit-1.65.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: unique-toolkit
-Version: 1.65.0
+Version: 1.65.1
 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.65.0 → unique_toolkit-1.65.1}/pyproject.toml

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

{unique_toolkit-1.65.0 → unique_toolkit-1.65.1}/unique_toolkit/agentic/tools/openai_builtin/code_interpreter/config.py

@@ -106,6 +106,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, 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.
+- 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.
 - 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.
@@ -138,10 +139,12 @@ class OpenAICodeInterpreterConfig(BaseToolConfig):
     tool_description_for_system_prompt: Annotated[
         str,
         RJSFMetaTag.StringWidget.textarea(
-            rows=int(len(DEFAULT_TOOL_DESCRIPTION_FOR_SYSTEM_PROMPT.split("\n")) / 2)
+            rows=int(
+                len(DEFAULT_TOOL_DESCRIPTION_FOR_SYSTEM_PROMPT_FENCE.split("\n")) / 2
+            )
         ),
     ] = Field(
-        default=DEFAULT_TOOL_DESCRIPTION_FOR_SYSTEM_PROMPT,
+        default=DEFAULT_TOOL_DESCRIPTION_FOR_SYSTEM_PROMPT_FENCE,
         description="The description of the tool that will be included in the system prompt.",
     )
     tool_description_for_user_prompt: SkipJsonSchema[str] = (

{unique_toolkit-1.65.0 → unique_toolkit-1.65.1}/unique_toolkit/agentic/tools/openai_builtin/code_interpreter/service.py

@@ -15,8 +15,6 @@ from unique_toolkit.agentic.tools.openai_builtin.base import (
     OpenAIBuiltInToolName,
 )
 from unique_toolkit.agentic.tools.openai_builtin.code_interpreter.config import (
-    DEFAULT_TOOL_DESCRIPTION_FOR_SYSTEM_PROMPT,
-    DEFAULT_TOOL_DESCRIPTION_FOR_SYSTEM_PROMPT_FENCE,
     OpenAICodeInterpreterConfig,
 )
 from unique_toolkit.agentic.tools.schemas import ToolPrompts
@@ -243,33 +241,11 @@ class OpenAICodeInterpreterTool(OpenAIBuiltInTool[CodeInterpreter]):
 
     @override
     def get_tool_prompts(self) -> ToolPrompts:
-        # When the fence feature flag is on the frontend derives the artifact title
-        # from the filename, so the LLM no longer needs to produce a markdown heading.
-        # We only substitute the fence-aware default when the operator has NOT
-        # customised the prompt — a custom value is always respected regardless of FF.
-        # When FF is off we always use the operator-configured prompt as-is.
-        fence_ff_on = feature_flags.enable_code_execution_fence_un_17972.is_enabled(
-            self._company_id
-        )
-        # A prompt is considered operator-customised only when it differs from every
-        # known default variant. Comparing against both defaults ensures spaces whose
-        # stored value was written by an earlier deployment (which may have used the
-        # non-fence default) are still treated as uncustomised once the fence FF is on.
-        stored = self._config.tool_description_for_system_prompt
-        operator_customised = stored not in {
-            DEFAULT_TOOL_DESCRIPTION_FOR_SYSTEM_PROMPT,
-            DEFAULT_TOOL_DESCRIPTION_FOR_SYSTEM_PROMPT_FENCE,
-        }
-        if fence_ff_on and not operator_customised:
-            system_prompt = DEFAULT_TOOL_DESCRIPTION_FOR_SYSTEM_PROMPT_FENCE
-        else:
-            system_prompt = stored
-
         return ToolPrompts(
             name="python",  # https://platform.openai.com/docs/guides/tools-code-interpreter
             display_name=self.DISPLAY_NAME,
             tool_description=self._config.tool_description,
-            tool_system_prompt=system_prompt,
+            tool_system_prompt=self._config.tool_description_for_system_prompt,
             tool_format_information_for_system_prompt="",
             tool_user_prompt=self._config.tool_description_for_user_prompt,
             tool_format_information_for_user_prompt="",