# CrewAI 1.15.30: our test log

Canonical: https://theagenticweekly.com/tests/crewai · Last verified: 2026-10-25 · Published: 2026-10-25 · Author: Agentic Weekly (operated independently from Texas, US) · Evidence: Tested by us on 2026-10-25. Local open-weight model, not the vendor's hosted models. A smoke test on a CPU-only box, not a benchmark.

> CrewAI 1.15.30 passed our one-tool task on a local 3B model: 3 of 3 trials; cold uv install 8.4 s.

## Result at a glance

Table: CrewAI test record

| Field | Value |
|---|---|
| Result | Passed |
| Version tested | 1.15.30 |
| Date and time | 2026-10-25, 23:20 to 23:21 CDT (America/Chicago) |
| Task | Give a local model one Python function, add_numbers(a, b), and ask it to use that tool to compute 17 + 25 and report the result. Pass means the function was called with 17 and 25 and the final answer contains 42. Three trials per tool, all on the same local model. |
| Model used | Qwen2.5-3B-Instruct (Q4_K_M) through Ollama 0.40.11 |
| Hardware | Linux x86_64 virtual machine (Debian 13), 8 vCPU (Intel Xeon, 1 thread per core), 15 GiB RAM, no GPU |
| Installed size (uv) | 819 MB in 137 packages |
| Install time (uv, cold) | 8.4 s |
| Install time (pip, cold) | 32.2 s |
| Installed size (pip) | 973 MB in 138 packages |
| Task trials passed | 3 of 3 |
| Task wall time (median, includes imports) | 5.9 s (range 5.5 to 7.1 s) |
| Machine load during trials | 8.3 to 8.9 (1-minute load average, 8 vCPU) |

## What we found

- 3 of 3 task trials passed: the model's tool call reached the framework, the function ran with 17 and 25, and the final answer contained 42.
- Cold install took 8.4 s with uv and 32.2 s with pip, and left 819 MB in 137 packages (uv).
- The largest install in our set (hundreds of MB, 130+ packages), roughly 10x the plain SDK.

## What we ran, step by step

Table: Commands run, wall-clock time and exit code

| Step | Wall time | Exit code | Notes |
|---|---|---|---|
| Install with uv (cold, no cache) | 8.4 s | 0 | Machine load average before the run: 0.83. |
| Install with pip (cold, no cache) | 32.2 s | 0 | Load average before: 2.14. Second run; the first pip run was discarded (see the research page). |
| Task command (all trials) | n/a | n/a | Run from a directory that contains common.py (shown below). Telemetry switches were set for tools that have them. |
| Task trial 1 | 7.1 s | 0 | Tool called with [[17, 25]]; answer: The sum of 17 and 25 is 42. Load 8.91. |
| Task trial 2 | 5.5 s | 0 | Tool called with [[17, 25], [42, 0]]; answer: The sum of 17 and 25 is 42. Load 8.92. |
| Task trial 3 | 5.9 s | 0 | Tool called with [[17, 25], [42, 0]]; answer: The sum of 17 and 25 is 42. Load 8.28. |

Exact commands (paths shortened)

```
# Install with uv (cold, no cache)
uv venv -q -p 3.13 work/py/crewai && VIRTUAL_ENV=work/py/crewai uv pip install --no-cache -q crewai

# Install with pip (cold, no cache)
uv venv -q --seed -p 3.13 work/pip/crewai && work/pip/crewai/bin/pip install --no-cache-dir -q crewai

# Task command (all trials)
OTEL_SDK_DISABLED=true work/py/crewai/bin/python tasks/crewai_agent.py
```

## Raw output (excerpts)

tasks/crewai_agent.py, the whole script for this test

```
from common import *
import os
os.environ["CREWAI_TELEMETRY_OPT_OUT"]="true"; os.environ["OTEL_SDK_DISABLED"]="true"
from crewai import Agent, Task, Crew, LLM
from crewai.tools import tool
t = tool("add_numbers")(add_numbers)
llm = LLM(model=f"openai/{MODEL}", base_url=BASE, api_key=KEY, temperature=0)
a = Agent(role="Calculator", goal="Add numbers with the tool", backstory="You always use the add_numbers tool.", tools=[t], llm=llm, verbose=False)
task = Task(description=TASK, expected_output="The sum as a number", agent=a)
r = Crew(agents=[a], tasks=[task], verbose=False).kickoff()
report(r.raw)
```

common.py, the shared helper every framework script imports

```
import json, os
BASE = "http://127.0.0.1:11434/v1"
MODEL = os.environ.get("MODEL", "qwen2.5-3b")
KEY = "ollama"
TASK = "Use the add_numbers tool to compute 17 + 25, then tell me the result."
CALLS = []
def add_numbers(a: int, b: int) -> int:
    """Add two integers and return the sum."""
    CALLS.append((a, b))
    return int(a) + int(b)
def report(final):
    ok = any({int(x), int(y)} == {17, 25} for x, y in CALLS) and "42" in str(final)
    print("RESULT_JSON " + json.dumps({"calls": CALLS, "final": str(final)[:300], "ok": ok}))
```

Result line printed by trial 1 (2026-10-25 23:20:57 CDT)

```
RESULT_JSON {"calls": [[17, 25]], "final": "The sum of 17 and 25 is 42.", "ok": true}
```

## Gotchas and things that broke

- Telemetry is on by default; we set CREWAI_TELEMETRY_OPT_OUT=true and OTEL_SDK_DISABLED=true for every run.

## What we did not test

- Any vendor-hosted model: everything ran on a local 3B model, so tool-call reliability with frontier models is not measured here.
- Multi-agent flows, memory, long conversations, streaming, tracing and cloud deployment.
- Anything beyond one tool and one question; three trials is a smoke test, not a benchmark.

## Reproduce it

Versions change. These commands install whatever is latest on the day you run them unless a version is pinned, so expect different results later. The version we measured is in the table above.

```
# 1. Serve any local model that supports tool calling behind an OpenAI-compatible endpoint, registered as qwen2.5-3b:
#    http://127.0.0.1:11434/v1  (we used Ollama with a Qwen2.5-3B-Instruct Q4_K_M GGUF)
uv venv -p 3.13 .venv && VIRTUAL_ENV=.venv uv pip install crewai
# 2. Save common.py (above) and the task script next to each other, then:
.venv/bin/python crewai_agent.py
```

## How to read this test

Every number on this page was measured on this one machine, which also ran other jobs, so timings are indicative and vary run to run. A pass means our small task worked once or as stated, a fail means it did not work as we ran it; neither says how the tool behaves with a vendor's frontier model, on a GPU, or at scale. Where a tool could not run without an account or a GPU, we say so instead of guessing.

See the [testing rig](https://theagenticweekly.com/methodology#testing-rig) for the hardware, the local model and the rules we follow, and the [test hub](https://theagenticweekly.com/tests) for every other test.

## FAQ

### Does CrewAI work with a local model?

In our run it did for this one task: 3 of 3 trials passed against a local Qwen2.5-3B model served by Ollama. We did not test other models, and results depend heavily on the model's tool-calling ability.

### How big is a fresh CrewAI install?

819 MB in 137 packages with uv on 1.15.30, measured on 2026-10-25.

## Sources

- [CrewAI repository](https://github.com/crewAIInc/crewAI) (fetched 2026-10-25)

## Related

- [All test logs](https://theagenticweekly.com/tests)
- [Methodology and testing rig](https://theagenticweekly.com/methodology#testing-rig)
- [Study: install size and first-task results across 16 frameworks](https://theagenticweekly.com/research/agent-framework-install-and-first-task)
- [CrewAI facts and sources](https://theagenticweekly.com/tools/crewai)

## How to cite

Agentic Weekly, "CrewAI 1.15.30: our test log", last updated 2026-10-25, https://theagenticweekly.com/tests/crewai