mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-01 21:28:10 +00:00
* feat: adopt directory-based docs versioning with Edge channel Switch docs.crewai.com from navigation-only versioning (every version selector entry rendered the same docs/<lang>/* source files) to Mintlify's directory-based versioning so each version selector entry renders its own snapshot. Add an "Edge" channel under docs/edge/<lang>/* that always reflects main HEAD for unreleased work, eliminating pre-release leakage onto frozen release labels. External links to canonical /<lang>/* URLs are preserved via wildcard redirects that always land on the current default version. Layout: - docs/edge/<lang>/* rolling source (you edit here) - docs/edge/enterprise-api.*.yaml - docs/v<X.Y.Z>/<lang>/* frozen, immutable snapshots - docs/v<X.Y.Z>/enterprise-api.*.yaml - docs/images/ shared, append-only - docs/docs.json nav + redirects URLs follow the Mintlify-idiomatic shape: /edge/<lang>/<page> for Edge, /v<X.Y.Z>/<lang>/<page> for every frozen snapshot. The wildcard redirects /<lang>/:slug* -> /<default>/<lang>/:slug* keep stale links working, and every freeze rewrites them (plus all per-section/per-page redirects) so destinations always resolve to the current default without depending on a second redirect hop. Release flow integration (devtools release): - New module crewai_devtools.docs_versioning.freeze() materialises docs/v<X.Y.Z>/ from docs/edge/, rewrites openapi: refs inside the snapshot, inserts the version into every language block in docs.json, and refreshes all redirect destinations. - _update_docs_and_create_pr() in cli.py now calls that freeze during Phase 2 of devtools release. Edge changelogs are updated first (so the snapshot freeze picks them up), then the snapshot is staged alongside docs.json, branched as docs/freeze-v<X.Y.Z>, and the PR is titled [docs-freeze] docs: snapshot and changelog for v<X.Y.Z> — the title prefix the new CI guard reads. - The PR still gates tag, GitHub release, PyPI publish, and the enterprise release as before; no new PRs are added. - Pre-releases (1.X.YaN, 1.X.YbN, ...) skip the snapshot — they ride Edge — and the docs PR title omits the [docs-freeze] prefix. - docs_check (AI-generated docs scaffolding) writes to docs/edge/<lang>/* so newly-generated unreleased docs land in Edge and never accidentally touch a frozen snapshot. Migration scripts (one-shot): - scripts/docs/freeze_historical_versions.py reconstructs all 16 historical snapshots (v1.10.0 .. v1.14.7) from git tags via git archive | tar, rewriting openapi: MDX refs so each snapshot reads its own enterprise-api YAML rather than the live one. - scripts/docs/prefix_version_paths.py one-shot-migrates docs.json: rewrites every page path in 16 versioned blocks to point under docs/v<X.Y.Z>/, inserts a new Edge entry per language, tags v1.14.7 as Latest (default), prunes pages whose target file doesn't exist in the snapshot (e.g. docs/ar/ didn't exist before v1.12.0), and writes the wildcard + per-section redirects. - scripts/docs/freeze_current_edge.py is now a thin CLI wrapper around docs_versioning.freeze for manual one-off freezes (e.g. retroactively snapshotting a forgotten release). CI guards (.github/workflows/docs-snapshots.yml): - Frozen snapshots under docs/v[0-9]*/ are immutable; only PRs whose title contains [docs-freeze] (i.e. release-cut PRs generated by devtools release or the manual wrapper) may modify them. - Images under docs/images/ are append-only since snapshots share a single image directory. Deleting or renaming an image breaks every historical snapshot that still references it. Restored docs/images/crewai-otel-export.png from PR #3673; it was deleted in PR #4908 but v1.10.0 / v1.10.1 snapshots still reference it. Restoring instead of editing the snapshots preserves historical rendering fidelity and validates the new append-only rule retroactively. Tests: - lib/devtools/tests/test_docs_versioning.py covers the freeze: file copy, openapi rewrite, version insertion, default demotion, redirect upserts, per-section redirect rewriting, idempotency, and invalid inputs. Verified locally with mintlify broken-links: 0 broken links across the full site (Edge + 16 frozen versions, 4 locales). AGENTS.md (repo root) is the contributor guide for the new model; RELEASING.md is the release-cut runbook; README's Contribution section links to both. Co-authored-by: Cursor <cursoragent@cursor.com> * style: resolve linter issues --------- Co-authored-by: Cursor <cursoragent@cursor.com>
215 lines
8.1 KiB
Plaintext
215 lines
8.1 KiB
Plaintext
---
|
||
title: Code Interpreter
|
||
description: The `CodeInterpreterTool` is a powerful tool designed for executing Python 3 code within a secure, isolated environment.
|
||
icon: code-simple
|
||
mode: "wide"
|
||
---
|
||
|
||
# `CodeInterpreterTool`
|
||
|
||
<Warning>
|
||
**Deprecated:** `CodeInterpreterTool` has been removed from `crewai-tools`. The `allow_code_execution` and `code_execution_mode` parameters on `Agent` are also deprecated. Use a dedicated sandbox service — [E2B](https://e2b.dev) or [Modal](https://modal.com) — for secure, isolated code execution.
|
||
</Warning>
|
||
|
||
## Description
|
||
|
||
The `CodeInterpreterTool` enables CrewAI agents to execute Python 3 code that they generate autonomously. This functionality is particularly valuable as it allows agents to create code, execute it, obtain the results, and utilize that information to inform subsequent decisions and actions.
|
||
|
||
There are several ways to use this tool:
|
||
|
||
### Docker Container (Recommended)
|
||
|
||
This is the primary option. The code runs in a secure, isolated Docker container, ensuring safety regardless of its content.
|
||
Make sure Docker is installed and running on your system. If you don’t have it, you can install it from [here](https://docs.docker.com/get-docker/).
|
||
|
||
### Sandbox environment
|
||
|
||
If Docker is unavailable — either not installed or not accessible for any reason — the code will be executed in a restricted Python environment - called sandbox.
|
||
This environment is very limited, with strict restrictions on many modules and built-in functions.
|
||
|
||
### Unsafe Execution
|
||
|
||
**NOT RECOMMENDED FOR PRODUCTION**
|
||
This mode allows execution of any Python code, including dangerous calls to `sys, os..` and similar modules. [Check out](/en/tools/ai-ml/codeinterpretertool#enabling-unsafe-mode) how to enable this mode
|
||
|
||
## Logging
|
||
|
||
The `CodeInterpreterTool` logs the selected execution strategy to STDOUT
|
||
|
||
|
||
## Installation
|
||
|
||
To use this tool, you need to install the CrewAI tools package:
|
||
|
||
```shell
|
||
pip install 'crewai[tools]'
|
||
```
|
||
|
||
## Example
|
||
|
||
The following example demonstrates how to use the `CodeInterpreterTool` with a CrewAI agent:
|
||
|
||
```python Code
|
||
from crewai import Agent, Task, Crew, Process
|
||
from crewai_tools import CodeInterpreterTool
|
||
|
||
# Initialize the tool
|
||
code_interpreter = CodeInterpreterTool()
|
||
|
||
# Define an agent that uses the tool
|
||
programmer_agent = Agent(
|
||
role="Python Programmer",
|
||
goal="Write and execute Python code to solve problems",
|
||
backstory="An expert Python programmer who can write efficient code to solve complex problems.",
|
||
tools=[code_interpreter],
|
||
verbose=True,
|
||
)
|
||
|
||
# Example task to generate and execute code
|
||
coding_task = Task(
|
||
description="Write a Python function to calculate the Fibonacci sequence up to the 10th number and print the result.",
|
||
expected_output="The Fibonacci sequence up to the 10th number.",
|
||
agent=programmer_agent,
|
||
)
|
||
|
||
# Create and run the crew
|
||
crew = Crew(
|
||
agents=[programmer_agent],
|
||
tasks=[coding_task],
|
||
verbose=True,
|
||
process=Process.sequential,
|
||
)
|
||
result = crew.kickoff()
|
||
```
|
||
|
||
You can also enable code execution directly when creating an agent:
|
||
|
||
```python Code
|
||
from crewai import Agent
|
||
|
||
# Create an agent with code execution enabled
|
||
programmer_agent = Agent(
|
||
role="Python Programmer",
|
||
goal="Write and execute Python code to solve problems",
|
||
backstory="An expert Python programmer who can write efficient code to solve complex problems.",
|
||
allow_code_execution=True, # This automatically adds the CodeInterpreterTool
|
||
verbose=True,
|
||
)
|
||
```
|
||
|
||
### Enabling `unsafe_mode`
|
||
|
||
```python Code
|
||
from crewai_tools import CodeInterpreterTool
|
||
|
||
code = """
|
||
import os
|
||
os.system("ls -la")
|
||
"""
|
||
|
||
CodeInterpreterTool(unsafe_mode=True).run(code=code)
|
||
```
|
||
|
||
## Parameters
|
||
|
||
The `CodeInterpreterTool` accepts the following parameters during initialization:
|
||
|
||
- **user_dockerfile_path**: Optional. Path to a custom Dockerfile to use for the code interpreter container.
|
||
- **user_docker_base_url**: Optional. URL to the Docker daemon to use for running the container.
|
||
- **unsafe_mode**: Optional. Whether to run code directly on the host machine instead of in a Docker container or sandbox. Default is `False`. Use with caution!
|
||
- **default_image_tag**: Optional. Default Docker image tag. Default is `code-interpreter:latest`
|
||
|
||
When using the tool with an agent, the agent will need to provide:
|
||
|
||
- **code**: Required. The Python 3 code to execute.
|
||
- **libraries_used**: Optional. A list of libraries used in the code that need to be installed. Default is `[]`
|
||
|
||
## Agent Integration Example
|
||
|
||
Here's a more detailed example of how to integrate the `CodeInterpreterTool` with a CrewAI agent:
|
||
|
||
```python Code
|
||
from crewai import Agent, Task, Crew
|
||
from crewai_tools import CodeInterpreterTool
|
||
|
||
# Initialize the tool
|
||
code_interpreter = CodeInterpreterTool()
|
||
|
||
# Define an agent that uses the tool
|
||
data_analyst = Agent(
|
||
role="Data Analyst",
|
||
goal="Analyze data using Python code",
|
||
backstory="""You are an expert data analyst who specializes in using Python
|
||
to analyze and visualize data. You can write efficient code to process
|
||
large datasets and extract meaningful insights.""",
|
||
tools=[code_interpreter],
|
||
verbose=True,
|
||
)
|
||
|
||
# Create a task for the agent
|
||
analysis_task = Task(
|
||
description="""
|
||
Write Python code to:
|
||
1. Generate a random dataset of 100 points with x and y coordinates
|
||
2. Calculate the correlation coefficient between x and y
|
||
3. Create a scatter plot of the data
|
||
4. Print the correlation coefficient and save the plot as 'scatter.png'
|
||
|
||
Make sure to handle any necessary imports and print the results.
|
||
""",
|
||
expected_output="The correlation coefficient and confirmation that the scatter plot has been saved.",
|
||
agent=data_analyst,
|
||
)
|
||
|
||
# Run the task
|
||
crew = Crew(
|
||
agents=[data_analyst],
|
||
tasks=[analysis_task],
|
||
verbose=True,
|
||
process=Process.sequential,
|
||
)
|
||
result = crew.kickoff()
|
||
```
|
||
|
||
## Implementation Details
|
||
|
||
The `CodeInterpreterTool` uses Docker to create a secure environment for code execution:
|
||
|
||
```python Code
|
||
class CodeInterpreterTool(BaseTool):
|
||
name: str = "Code Interpreter"
|
||
description: str = "Interprets Python3 code strings with a final print statement."
|
||
args_schema: Type[BaseModel] = CodeInterpreterSchema
|
||
default_image_tag: str = "code-interpreter:latest"
|
||
|
||
def _run(self, **kwargs) -> str:
|
||
code = kwargs.get("code", self.code)
|
||
libraries_used = kwargs.get("libraries_used", [])
|
||
|
||
if self.unsafe_mode:
|
||
return self.run_code_unsafe(code, libraries_used)
|
||
else:
|
||
return self.run_code_safety(code, libraries_used)
|
||
```
|
||
|
||
The tool performs the following steps:
|
||
1. Verifies that the Docker image exists or builds it if necessary
|
||
2. Creates a Docker container with the current working directory mounted
|
||
3. Installs any required libraries specified by the agent
|
||
4. Executes the Python code in the container
|
||
5. Returns the output of the code execution
|
||
6. Cleans up by stopping and removing the container
|
||
|
||
## Security Considerations
|
||
|
||
By default, the `CodeInterpreterTool` runs code in an isolated Docker container, which provides a layer of security. However, there are still some security considerations to keep in mind:
|
||
|
||
1. The Docker container has access to the current working directory, so sensitive files could potentially be accessed.
|
||
2. If the Docker container is unavailable and the code needs to run safely, it will be executed in a sandbox environment. For security reasons, installing arbitrary libraries is not allowed
|
||
3. The `unsafe_mode` parameter allows code to be executed directly on the host machine, which should only be used in trusted environments.
|
||
4. Be cautious when allowing agents to install arbitrary libraries, as they could potentially include malicious code.
|
||
|
||
## Conclusion
|
||
|
||
The `CodeInterpreterTool` provides a powerful way for CrewAI agents to execute Python code in a relatively secure environment. By enabling agents to write and run code, it significantly expands their problem-solving capabilities, especially for tasks involving data analysis, calculations, or other computational work. This tool is particularly useful for agents that need to perform complex operations that are more efficiently expressed in code than in natural language.
|