You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
code_interpreter() and local_code_interpreter() were deprecated in favour of python_tool(). Several examples and docs pages still reference the old functions, producing DeprecationWarning at runtime.
Deprecation mapping
Old
New
code_interpreter(code)
python_tool(tier='docker_unsafe').run(code=code)
local_code_interpreter(code)
python_tool(tier='local_unsafe').run(code=code)
MelleaTool.from_callable(local_code_inter…)
python_tool(tier='local_unsafe')
uses_tool(local_code_interpreter)
uses_tool(python_tool(tier='local_unsafe'))
result.tool_calls["local_code_interpreter"]
result.tool_calls["python_tool"]
Note: python_tool() returns a MelleaTool directly, so MelleaTool.from_callable() wrapping is no longer needed.
python_tool() requires an explicit tier argument; omitting it raises a warning. Use tier='local_unsafe' for local execution (replaces local_code_interpreter) and tier='docker_unsafe' for sandboxed execution (replaces code_interpreter)
The tool name exposed to the LLM changes from "local_code_interpreter" / "code_interpreter" to "python_tool" — .tool_calls key lookups in examples need updating accordingly
code_interpreter() and local_code_interpreter() were deprecated in favour of python_tool(). Several examples and docs pages still reference the old functions, producing DeprecationWarning at runtime.
Deprecation mapping
Note: python_tool() returns a MelleaTool directly, so MelleaTool.from_callable() wrapping is no longer needed.
Files to update
Additional context