mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-04 22:49:23 +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>
143 lines
4.4 KiB
Plaintext
143 lines
4.4 KiB
Plaintext
---
|
|
title: Crie sua primeira Crew
|
|
description: Tutorial passo a passo para criar uma equipe colaborativa de IA com configuração JSON-first.
|
|
icon: users-gear
|
|
mode: "wide"
|
|
---
|
|
|
|
## Crie uma Crew de Pesquisa
|
|
|
|
Neste guia, você criará uma crew com dois agentes que pesquisa um tópico e escreve um relatório em markdown. Novos projetos de crew são JSON-first: agentes ficam em `agents/*.jsonc`, tarefas e configurações ficam em `crew.jsonc`, e `crewai run` carrega essa definição diretamente.
|
|
|
|
### Pré-requisitos
|
|
|
|
Antes de começar:
|
|
|
|
1. Instale o CrewAI seguindo o [guia de instalação](/pt-BR/installation)
|
|
2. Configure sua chave de LLM seguindo o [guia de LLMs](/pt-BR/concepts/llms#setting-up-your-llm)
|
|
3. Tenha uma chave [Serper.dev](https://serper.dev/) se quiser usar busca web
|
|
|
|
## Etapa 1: Criar uma nova Crew
|
|
|
|
```bash
|
|
crewai create crew research_crew
|
|
cd research_crew
|
|
```
|
|
|
|
Estrutura criada:
|
|
|
|
```text
|
|
research_crew/
|
|
├── .gitignore
|
|
├── .env
|
|
├── agents/
|
|
│ └── researcher.jsonc
|
|
├── crew.jsonc
|
|
├── knowledge/
|
|
├── pyproject.toml
|
|
├── README.md
|
|
├── skills/
|
|
└── tools/
|
|
```
|
|
|
|
<Tip>
|
|
Precisa do layout antigo com `crew.py`, `config/agents.yaml` e `config/tasks.yaml`? Use `crewai create crew research_crew --classic`.
|
|
</Tip>
|
|
|
|
## Etapa 2: Definir os agentes
|
|
|
|
Substitua o arquivo gerado `agents/researcher.jsonc` e adicione `agents/analyst.jsonc`. Os nomes dos arquivos são os nomes referenciados em `crew.jsonc`.
|
|
|
|
```jsonc agents/researcher.jsonc
|
|
{
|
|
"role": "Senior Research Specialist for {topic}",
|
|
"goal": "Find comprehensive and accurate information about {topic}, with a focus on recent developments and key insights.",
|
|
"backstory": "You are an experienced research specialist who organizes complex information into clear, useful notes.",
|
|
// Substitua pelo seu modelo, por exemplo "openai/gpt-4o".
|
|
"llm": "provider/model-id",
|
|
"tools": ["SerperDevTool"],
|
|
"settings": {
|
|
"verbose": true,
|
|
"allow_delegation": false
|
|
}
|
|
}
|
|
```
|
|
|
|
```jsonc agents/analyst.jsonc
|
|
{
|
|
"role": "Report Analyst for {topic}",
|
|
"goal": "Turn research findings into a clear, well-structured report.",
|
|
"backstory": "You are a careful analyst with strong technical writing skills and a talent for extracting useful insights.",
|
|
// Substitua pelo seu modelo, por exemplo "openai/gpt-4o".
|
|
"llm": "provider/model-id",
|
|
"settings": {
|
|
"verbose": true,
|
|
"allow_delegation": false
|
|
}
|
|
}
|
|
```
|
|
|
|
Substitua `provider/model-id` pelo modelo usado, como `openai/gpt-4o`, `anthropic/claude-sonnet-4-6` ou `gemini/gemini-2.0-flash-001`.
|
|
|
|
## Etapa 3: Definir tarefas e configurações
|
|
|
|
Substitua `crew.jsonc` por:
|
|
|
|
```jsonc crew.jsonc
|
|
{
|
|
"name": "Research Crew",
|
|
"agents": ["researcher", "analyst"],
|
|
"tasks": [
|
|
{
|
|
"name": "research_task",
|
|
"description": "Conduct thorough research on {topic}. Focus on key concepts, recent developments, major challenges, notable applications, and future outlook.",
|
|
"expected_output": "A comprehensive research document with organized sections, specific facts, and useful examples about {topic}.",
|
|
"agent": "researcher"
|
|
},
|
|
{
|
|
"name": "analysis_task",
|
|
"description": "Analyze the research findings and create a polished report on {topic}. Include an executive summary, key insights, trend analysis, and recommendations.",
|
|
"expected_output": "A professional markdown report with clear headings, a concise summary, main findings, and recommendations.",
|
|
"agent": "analyst",
|
|
"context": ["research_task"],
|
|
"output_file": "output/report.md",
|
|
"markdown": true
|
|
}
|
|
],
|
|
"process": "sequential",
|
|
"verbose": true,
|
|
"memory": true,
|
|
"inputs": {
|
|
"topic": "Artificial Intelligence in Healthcare"
|
|
}
|
|
}
|
|
```
|
|
|
|
`context` aponta para tarefas anteriores, então o analista recebe a saída da pesquisa. `inputs` define valores padrão para `{topic}`; se um valor faltar, `crewai run` perguntará no terminal.
|
|
|
|
## Etapa 4: Variáveis de ambiente
|
|
|
|
Edite `.env`:
|
|
|
|
```sh
|
|
SERPER_API_KEY=your_serper_api_key
|
|
# Adicione também a chave do seu provedor de modelo.
|
|
```
|
|
|
|
## Etapa 5: Instalar e executar
|
|
|
|
```bash
|
|
crewai install
|
|
crewai run
|
|
```
|
|
|
|
Quando a execução terminar, abra `output/report.md`.
|
|
|
|
<Warning>
|
|
Execute projetos JSON crew apenas de fontes confiáveis. Ferramentas `custom:<name>` e referências `{"python": "module.attribute"}` executam Python local ao carregar a crew.
|
|
</Warning>
|
|
|
|
<Check>
|
|
Você criou uma crew JSON-first funcional que pesquisa um tópico e escreve um relatório.
|
|
</Check>
|