andre/crewAI
1
0
Fork 0
mirror of https://github.com/crewAIInc/crewAI.git synced 2026-07-01 05:08:12 +00:00
Code Issues Actions 6 Packages Projects Releases Wiki Activity
Files
05ab1ece8ed952e54c9775ccbfdda79f84cb8271
crewAI/docs/edge/ko/tools/overview.mdx
Lucas Gomide a237ebabba feat: adopt directory-based docs versioning with Edge channel (#6202) 
* 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>
2026-06-17 11:56:59 -04:00

130 lines
4.2 KiB
Plaintext
Raw Blame History

---
title: "도구 개요"
description: "CrewAI의 AI 에이전트를 강화하는 40개 이상의 방대한 도구 라이브러리를 확인해보세요"
icon: "toolbox"
mode: "wide"
---
CrewAI는 에이전트의 기능을 향상시키기 위한 다양한 사전 구축 도구 라이브러리를 제공합니다. 파일 처리부터 웹 스크래핑, 데이터베이스 쿼리, AI 서비스에 이르기까지 모두 지원합니다.
## **도구 카테고리**
<CardGroup cols={2}>
<Card
title="파일 & 문서"
icon="folder-open"
href="/ko/tools/file-document/overview"
color="#3B82F6"
>
PDF, DOCX, JSON, CSV 등 다양한 파일 형식을 읽고, 작성하고, 검색할 수 있습니다. 문서 처리 워크플로우에 적합합니다.
</Card>
<Card
title="웹 스크래핑 & 브라우징"
icon="globe"
href="/ko/tools/web-scraping/overview"
color="#10B981"
>
웹사이트에서 데이터를 추출하고, 브라우저 상호작용을 자동화하며, Firecrawl, Selenium 등과 같은 도구로 대규모로 콘텐츠를 스크래핑할 수 있습니다.
</Card>
<Card
title="검색 & 리서치"
icon="magnifying-glass"
href="/ko/tools/search-research/overview"
color="#F59E0B"
>
웹 검색을 수행하고, 코드 저장소를 찾으며, YouTube 콘텐츠를 리서치하고, 인터넷 전반에 걸쳐 정보를 탐색할 수 있습니다.
</Card>
<Card
title="데이터베이스 & 데이터"
icon="database"
href="/ko/tools/database-data/overview"
color="#8B5CF6"
>
SQL 데이터베이스, 벡터 스토어, 데이터 웨어하우스에 연결합니다. MySQL, PostgreSQL, Snowflake, Qdrant, Weaviate를 쿼리할 수 있습니다.
</Card>
<Card
title="AI & 머신러닝"
icon="brain"
href="/ko/tools/ai-ml/overview"
color="#EF4444"
>
DALL-E로 이미지 생성, 비전 태스크 처리, LangChain과의 통합, RAG 시스템 구축, 코드 인터프리터 활용 등이 가능합니다.
</Card>
<Card
title="클라우드 & 스토리지"
icon="cloud"
href="/ko/tools/cloud-storage/overview"
color="#06B6D4"
>
AWS S3, Amazon Bedrock 및 기타 클라우드 스토리지 및 AI 서비스 등 클라우드 서비스와 상호작용할 수 있습니다.
</Card>
<Card
title="자동화"
icon="bolt"
href="/ko/tools/automation/overview"
color="#84CC16"
>
Apify, Composio 등과 함께 워크플로우를 자동화하고 에이전트를 외부 서비스와 연결하세요.
</Card>
<Card
title="통합"
icon="plug"
href="/ko/tools/tool-integrations/overview"
color="#0891B2"
>
Amazon Bedrock 및 CrewAI Automation 툴킷 등 외부 시스템과 CrewAI를 통합합니다.
</Card>
</CardGroup>
## **빠른 접근**
특정 도구가 필요하신가요? 인기 있는 옵션들을 소개합니다:
<CardGroup cols={3}>
<Card title="RAG Tool" icon="image" href="/ko/tools/ai-ml/ragtool">
검색 기반 생성(Retrieval-Augmented Generation) 구현
</Card>
<Card title="Serper Dev" icon="book-atlas" href="/ko/tools/search-research/serperdevtool">
구글 검색 API
</Card>
<Card title="File Read" icon="file" href="/ko/tools/file-document/filereadtool">
모든 파일 유형 읽기
</Card>
<Card title="Scrape Website" icon="globe" href="/ko/tools/web-scraping/scrapewebsitetool">
웹 콘텐츠 추출
</Card>
<Card title="Code Interpreter" icon="code" href="/ko/tools/ai-ml/codeinterpretertool">
Python 코드 실행
</Card>
<Card title="S3 Reader" icon="cloud" href="/ko/tools/cloud-storage/s3readertool">
AWS S3 파일 액세스
</Card>
</CardGroup>
## **시작하기**
CrewAI 프로젝트에서 어떤 도구를 사용하려면:
1. **도구를 임포트**하여 crew 설정에 추가합니다.
2. **에이전트의 tool 목록**에 추가합니다.
3. 필요한 **API 키 또는 설정을 구성**합니다.
```python
from crewai_tools import FileReadTool, SerperDevTool
# Add tools to your agent
agent = Agent(
role="Research Analyst",
tools=[FileReadTool(), SerperDevTool()],
# ... other configuration
)
```
탐험을 시작할 준비가 되셨나요? 위에서 카테고리를 선택하여 사용 사례에 맞는 도구를 찾아보세요!
Reference in New Issue View Git Blame Copy Permalink