mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-01 13:18:10 +00:00
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>
223 lines
7.6 KiB
Plaintext
223 lines
7.6 KiB
Plaintext
---
|
|
title: Installation
|
|
description: Get started with CrewAI - Install, configure, and build your first AI crew
|
|
icon: wrench
|
|
mode: "wide"
|
|
---
|
|
|
|
### Watch: Building CrewAI Agents & Flows with Coding Agent Skills
|
|
|
|
Install our coding agent skills (Claude Code, Codex, ...) to quickly get your coding agents up and running with CrewAI.
|
|
|
|
You can install it with `npx skills add crewaiinc/skills`
|
|
|
|
<iframe src="https://www.loom.com/embed/befb9f68b81f42ad8112bfdd95a780af" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen style={{width: "100%", height: "400px"}}></iframe>
|
|
|
|
## Video Tutorial
|
|
|
|
Watch this video tutorial for a step-by-step demonstration of the installation process:
|
|
|
|
<iframe
|
|
className="w-full aspect-video rounded-xl"
|
|
src="https://www.youtube.com/embed/-kSOTtYzgEw"
|
|
title="CrewAI Installation Guide"
|
|
frameBorder="0"
|
|
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
|
|
allowFullScreen
|
|
></iframe>
|
|
|
|
## Text Tutorial
|
|
|
|
<Note>
|
|
**Python Version Requirements**
|
|
|
|
CrewAI requires `Python >=3.10 and <3.14`. Here's how to check your version:
|
|
|
|
```bash
|
|
python3 --version
|
|
```
|
|
|
|
If you need to update Python, visit [python.org/downloads](https://python.org/downloads)
|
|
|
|
</Note>
|
|
|
|
<Note>
|
|
**OpenAI SDK Requirement**
|
|
|
|
CrewAI 0.175.0 requires `openai >= 1.13.3`. If you manage dependencies yourself, ensure your environment satisfies this constraint to avoid import/runtime issues.
|
|
|
|
</Note>
|
|
|
|
CrewAI uses the `uv` as its dependency management and package handling tool. It simplifies project setup and execution, offering a seamless experience.
|
|
|
|
If you haven't installed `uv` yet, follow **step 1** to quickly get it set up on your system, else you can skip to **step 2**.
|
|
|
|
<Steps>
|
|
<Step title="Install uv">
|
|
- **On macOS/Linux:**
|
|
|
|
Use `curl` to download the script and execute it with `sh`:
|
|
|
|
```shell
|
|
curl -LsSf https://astral.sh/uv/install.sh | sh
|
|
```
|
|
If your system doesn't have `curl`, you can use `wget`:
|
|
|
|
```shell
|
|
wget -qO- https://astral.sh/uv/install.sh | sh
|
|
```
|
|
|
|
- **On Windows:**
|
|
|
|
Use `irm` to download the script and `iex` to execute it:
|
|
|
|
```shell
|
|
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
|
|
```
|
|
If you run into any issues, refer to [UV's installation guide](https://docs.astral.sh/uv/getting-started/installation/) for more information.
|
|
</Step>
|
|
|
|
<Step title="Install CrewAI 🚀">
|
|
- Run the following command to install `crewai` CLI:
|
|
```shell
|
|
uv tool install crewai
|
|
```
|
|
<Warning>
|
|
If you encounter a `PATH` warning, run this command to update your shell:
|
|
```shell
|
|
uv tool update-shell
|
|
```
|
|
</Warning>
|
|
|
|
<Warning>
|
|
If you encounter the `chroma-hnswlib==0.7.6` build error (`fatal error C1083: Cannot open include file: 'float.h'`) on Windows, install [Visual Studio Build Tools](https://visualstudio.microsoft.com/downloads/) with *Desktop development with C++*.
|
|
</Warning>
|
|
|
|
- To verify that `crewai` is installed, run:
|
|
```shell
|
|
uv tool list
|
|
```
|
|
- You should see something like:
|
|
```shell
|
|
crewai v0.102.0
|
|
- crewai
|
|
```
|
|
- If you need to update `crewai`, run:
|
|
```shell
|
|
uv tool install crewai --upgrade
|
|
```
|
|
<Note>
|
|
This upgrades the **global `crewai` CLI tool** only. To upgrade the `crewai` version inside your project's virtual environment, see [Upgrading CrewAI in a project](/en/guides/migration/upgrading-crewai).
|
|
</Note>
|
|
<Check>Installation successful! You're ready to create your first crew! 🎉</Check>
|
|
</Step>
|
|
|
|
</Steps>
|
|
|
|
# Creating a CrewAI Project
|
|
|
|
`crewai create crew` now creates a JSON-first crew project. Agents live in `agents/*.jsonc`, tasks and crew-level settings live in `crew.jsonc`, and `crewai run` loads that JSON definition directly.
|
|
|
|
<Steps>
|
|
<Step title="Generate Project Scaffolding">
|
|
- Run the `crewai` CLI command:
|
|
```shell
|
|
crewai create crew <your_project_name>
|
|
```
|
|
|
|
- This creates a new project with the following structure:
|
|
```
|
|
my_project/
|
|
├── .gitignore
|
|
├── .env
|
|
├── agents/
|
|
│ └── researcher.jsonc
|
|
├── crew.jsonc
|
|
├── knowledge/
|
|
├── pyproject.toml
|
|
├── README.md
|
|
├── skills/
|
|
└── tools/
|
|
```
|
|
|
|
- If you need the older Python/YAML scaffold with `crew.py`, `config/agents.yaml`, and `config/tasks.yaml`, run:
|
|
```shell
|
|
crewai create crew <your_project_name> --classic
|
|
```
|
|
|
|
</Step>
|
|
|
|
<Step title="Customize Your Project">
|
|
- Your project will contain these essential files:
|
|
| File | Purpose |
|
|
| --- | --- |
|
|
| `crew.jsonc` | Configure the crew, task order, process, and input defaults |
|
|
| `agents/*.jsonc` | Define each agent's role, goal, backstory, LLM, tools, and behavior |
|
|
| `.env` | Store API keys and environment variables |
|
|
| `tools/` | Optional Python files for `custom:<name>` tools |
|
|
| `knowledge/` | Optional knowledge files for agents |
|
|
| `skills/` | Optional skill files applied to the crew |
|
|
|
|
- Start by editing `crew.jsonc` and the files in `agents/` to define your crew's behavior.
|
|
- Use `{placeholder}` values in agent and task text, then set defaults in `crew.jsonc` under `inputs`. When you run `crewai run`, the CLI prompts for any missing values.
|
|
- Keep sensitive information like API keys in `.env`.
|
|
|
|
</Step>
|
|
|
|
<Step title="Run your Crew">
|
|
- Before you run your crew, make sure to run:
|
|
```bash
|
|
crewai install
|
|
```
|
|
- If you need to install additional packages, use:
|
|
```shell
|
|
uv add <package-name>
|
|
```
|
|
<Note>
|
|
As a supply-chain security measure, CrewAI's internal packages use `exclude-newer = "3 days"` in their `pyproject.toml` files. This means transitive dependencies pulled in by CrewAI won't resolve packages released less than 3 days ago. Your own direct dependencies are not affected by this policy. If you notice a transitive dependency is behind, you can pin the version you want explicitly in your project's dependencies.
|
|
</Note>
|
|
- To run your crew, execute the following command in the root of your project:
|
|
```bash
|
|
crewai run
|
|
```
|
|
</Step>
|
|
</Steps>
|
|
|
|
## Enterprise Installation Options
|
|
|
|
<Note type="info">
|
|
For teams and organizations, CrewAI offers enterprise deployment options that eliminate setup complexity:
|
|
|
|
### CrewAI AMP (SaaS)
|
|
|
|
- Zero installation required - just sign up for free at [app.crewai.com](https://app.crewai.com)
|
|
- Automatic updates and maintenance
|
|
- Managed infrastructure and scaling
|
|
- Build Crews with no Code
|
|
|
|
### CrewAI Factory (Self-hosted)
|
|
|
|
- Containerized deployment for your infrastructure
|
|
- Supports any hyperscaler including on prem deployments
|
|
- Integration with your existing security systems
|
|
|
|
<Card title="Explore Enterprise Options" icon="building" href="https://share.hsforms.com/1Ooo2UViKQ22UOzdr7i77iwr87kg">
|
|
Learn about CrewAI's enterprise offerings and schedule a demo
|
|
</Card>
|
|
</Note>
|
|
|
|
## Next Steps
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="Quickstart: Flow + agent" icon="code" href="/en/quickstart">
|
|
Follow the quickstart to scaffold a Flow, run a one-agent crew, and produce a report.
|
|
</Card>
|
|
<Card
|
|
title="Join the Community"
|
|
icon="comments"
|
|
href="https://community.crewai.com"
|
|
>
|
|
Connect with other developers, get help, and share your CrewAI experiences.
|
|
</Card>
|
|
</CardGroup>
|