mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-03 22:19:27 +00:00
a237ebabba
* 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>
127 lines
5.2 KiB
Plaintext
127 lines
5.2 KiB
Plaintext
---
|
|
title: MultiOn Tool
|
|
description: O `MultiOnTool` permite que agentes CrewAI naveguem e interajam com a web por meio de instruções em linguagem natural.
|
|
icon: globe
|
|
mode: "wide"
|
|
---
|
|
|
|
## Visão Geral
|
|
|
|
O `MultiOnTool` foi projetado para envolver as capacidades de navegação web do [MultiOn](https://docs.multion.ai/welcome), permitindo que agentes CrewAI controlem navegadores web usando instruções em linguagem natural. Esta ferramenta facilita a navegação fluida, tornando-se um recurso essencial para projetos que requerem interação dinâmica com dados web e automação de tarefas baseadas na web.
|
|
|
|
## Instalação
|
|
|
|
Para utilizar esta ferramenta, é necessário instalar o pacote MultiOn:
|
|
|
|
```shell
|
|
uv add multion
|
|
```
|
|
|
|
Você também precisará instalar a extensão de navegador do MultiOn e habilitar o uso da API.
|
|
|
|
## Passos para Começar
|
|
|
|
Para usar o `MultiOnTool` de forma eficaz, siga estes passos:
|
|
|
|
1. **Instale o CrewAI**: Certifique-se de que o pacote `crewai[tools]` esteja instalado em seu ambiente Python.
|
|
2. **Instale e utilize o MultiOn**: Siga a [documentação do MultiOn](https://docs.multion.ai/learn/browser-extension) para instalar a extensão de navegador do MultiOn.
|
|
3. **Habilite o Uso da API**: Clique na extensão do MultiOn na pasta de extensões do seu navegador (não no ícone flutuante do MultiOn na página web) para abrir as configurações da extensão. Clique na opção para habilitar a API (API Enabled).
|
|
|
|
## Exemplo
|
|
|
|
O exemplo a seguir demonstra como inicializar a ferramenta e executar uma tarefa de navegação web:
|
|
|
|
```python Code
|
|
from crewai import Agent, Task, Crew
|
|
from crewai_tools import MultiOnTool
|
|
|
|
# Initialize the tool
|
|
multion_tool = MultiOnTool(api_key="YOUR_MULTION_API_KEY", local=False)
|
|
|
|
# Define an agent that uses the tool
|
|
browser_agent = Agent(
|
|
role="Browser Agent",
|
|
goal="Control web browsers using natural language",
|
|
backstory="An expert browsing agent.",
|
|
tools=[multion_tool],
|
|
verbose=True,
|
|
)
|
|
|
|
# Example task to search and summarize news
|
|
browse_task = Task(
|
|
description="Summarize the top 3 trending AI News headlines",
|
|
expected_output="A summary of the top 3 trending AI News headlines",
|
|
agent=browser_agent,
|
|
)
|
|
|
|
# Create and run the crew
|
|
crew = Crew(agents=[browser_agent], tasks=[browse_task])
|
|
result = crew.kickoff()
|
|
```
|
|
|
|
## Parâmetros
|
|
|
|
O `MultiOnTool` aceita os seguintes parâmetros durante a inicialização:
|
|
|
|
- **api_key**: Opcional. Especifica a chave da API do MultiOn. Se não for fornecida, a ferramenta procurará pela variável de ambiente `MULTION_API_KEY`.
|
|
- **local**: Opcional. Defina como `True` para executar o agente localmente em seu navegador. Certifique-se de que a extensão do MultiOn está instalada e a opção API Enabled está marcada. O padrão é `False`.
|
|
- **max_steps**: Opcional. Define o número máximo de etapas que o agente MultiOn pode executar para um comando. O padrão é `3`.
|
|
|
|
## Uso
|
|
|
|
Ao utilizar o `MultiOnTool`, o agente fornecerá instruções em linguagem natural que a ferramenta traduzirá em ações de navegação web. A ferramenta retorna os resultados da sessão de navegação juntamente com um status.
|
|
|
|
```python Code
|
|
# Example of using the tool with an agent
|
|
browser_agent = Agent(
|
|
role="Web Browser Agent",
|
|
goal="Search for and summarize information from the web",
|
|
backstory="An expert at finding and extracting information from websites.",
|
|
tools=[multion_tool],
|
|
verbose=True,
|
|
)
|
|
|
|
# Create a task for the agent
|
|
search_task = Task(
|
|
description="Search for the latest AI news on TechCrunch and summarize the top 3 headlines",
|
|
expected_output="A summary of the top 3 AI news headlines from TechCrunch",
|
|
agent=browser_agent,
|
|
)
|
|
|
|
# Run the task
|
|
crew = Crew(agents=[browser_agent], tasks=[search_task])
|
|
result = crew.kickoff()
|
|
```
|
|
|
|
Se o status retornado for `CONTINUE`, o agente deve ser instruído a reenviar a mesma instrução para continuar a execução.
|
|
|
|
## Detalhes de Implementação
|
|
|
|
O `MultiOnTool` é implementado como uma subclasse de `BaseTool` do CrewAI. Ele envolve o cliente MultiOn para fornecer capacidades de navegação web:
|
|
|
|
```python Code
|
|
class MultiOnTool(BaseTool):
|
|
"""Tool to wrap MultiOn Browse Capabilities."""
|
|
|
|
name: str = "Multion Browse Tool"
|
|
description: str = """Multion gives the ability for LLMs to control web browsers using natural language instructions.
|
|
If the status is 'CONTINUE', reissue the same instruction to continue execution
|
|
"""
|
|
|
|
# Implementation details...
|
|
|
|
def _run(self, cmd: str, *args: Any, **kwargs: Any) -> str:
|
|
"""
|
|
Run the Multion client with the given command.
|
|
|
|
Args:
|
|
cmd (str): The detailed and specific natural language instruction for web browsing
|
|
*args (Any): Additional arguments to pass to the Multion client
|
|
**kwargs (Any): Additional keyword arguments to pass to the Multion client
|
|
"""
|
|
# Implementation details...
|
|
```
|
|
|
|
## Conclusão
|
|
|
|
O `MultiOnTool` oferece uma maneira poderosa de integrar capacidades de navegação web em agentes CrewAI. Ao permitir que agentes interajam com sites por meio de instruções em linguagem natural, amplia significativamente as possibilidades para tarefas baseadas na web, desde coleta de dados e pesquisa até interações automatizadas com serviços online. |