mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-03 22:19:27 +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>
94 lines
3.9 KiB
Plaintext
94 lines
3.9 KiB
Plaintext
---
|
|
title: "개요"
|
|
description: "웹 검색을 수행하고, 저장소를 찾으며, 인터넷 전반에 걸쳐 정보를 조사합니다"
|
|
icon: "face-smile"
|
|
mode: "wide"
|
|
---
|
|
|
|
이러한 도구들은 에이전트가 웹을 검색하고, 다양한 주제를 조사하며, 검색 엔진, GitHub, YouTube 등 다양한 플랫폼에서 정보를 찾을 수 있도록 지원합니다.
|
|
|
|
## **사용 가능한 도구**
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="Serper Dev Tool" icon="google" href="/ko/tools/search-research/serperdevtool">
|
|
종합적인 웹 검색 기능을 위한 Google 검색 API 통합.
|
|
</Card>
|
|
|
|
<Card title="Brave Search Tool" icon="shield" href="/ko/tools/search-research/bravesearchtool">
|
|
Brave의 독립적인 검색 인덱스를 활용한 프라이버시 중심의 검색.
|
|
</Card>
|
|
|
|
<Card title="Exa Search Tool" icon="magnifying-glass" href="/ko/tools/search-research/exasearchtool">
|
|
특정하고 관련성 높은 콘텐츠를 찾기 위한 AI 기반 검색.
|
|
</Card>
|
|
|
|
<Card title="LinkUp Search Tool" icon="link" href="/ko/tools/search-research/linkupsearchtool">
|
|
최신 콘텐츠 인덱싱을 통한 실시간 웹 검색.
|
|
</Card>
|
|
|
|
<Card title="GitHub Search Tool" icon="github" href="/ko/tools/search-research/githubsearchtool">
|
|
GitHub 저장소, 코드, 이슈, 문서를 검색합니다.
|
|
</Card>
|
|
|
|
<Card title="Website Search Tool" icon="globe" href="/ko/tools/search-research/websitesearchtool">
|
|
특정 웹사이트 및 도메인 내에서 검색합니다.
|
|
</Card>
|
|
|
|
<Card title="Code Docs Search Tool" icon="code" href="/ko/tools/search-research/codedocssearchtool">
|
|
코드 문서와 기술 자료를 검색합니다.
|
|
</Card>
|
|
|
|
<Card title="YouTube Channel Search" icon="youtube" href="/ko/tools/search-research/youtubechannelsearchtool">
|
|
특정 콘텐츠 및 크리에이터를 찾기 위한 YouTube 채널 검색.
|
|
</Card>
|
|
|
|
<Card title="YouTube Video Search" icon="play" href="/ko/tools/search-research/youtubevideosearchtool">
|
|
주제, 키워드 또는 조건별로 YouTube 동영상을 찾고 분석합니다.
|
|
</Card>
|
|
|
|
<Card title="Tavily Search Tool" icon="magnifying-glass" href="/ko/tools/search-research/tavilysearchtool">
|
|
Tavily의 AI 기반 검색 API를 활용한 종합 웹 검색.
|
|
</Card>
|
|
|
|
<Card title="Tavily Extractor Tool" icon="file-text" href="/ko/tools/search-research/tavilyextractortool">
|
|
Tavily API를 사용하여 웹 페이지에서 구조화된 콘텐츠를 추출합니다.
|
|
</Card>
|
|
|
|
<Card title="Arxiv Paper Tool" icon="box-archive" href="/ko/tools/search-research/arxivpapertool">
|
|
arXiv에서 논문을 검색하고 선택적으로 PDF를 다운로드합니다.
|
|
</Card>
|
|
|
|
<Card title="SerpApi Google Search" icon="search" href="/ko/tools/search-research/serpapi-googlesearchtool">
|
|
구조화된 결과를 제공하는 SerpApi를 통한 Google 검색.
|
|
</Card>
|
|
|
|
<Card title="SerpApi Google Shopping" icon="cart-shopping" href="/ko/tools/search-research/serpapi-googleshoppingtool">
|
|
SerpApi를 통한 Google 쇼핑 쿼리.
|
|
</Card>
|
|
</CardGroup>
|
|
|
|
## **일반적인 사용 사례**
|
|
|
|
- **시장 조사**: 산업 트렌드와 경쟁사 분석 검색
|
|
- **콘텐츠 발견**: 관련 기사, 영상 및 자료 찾기
|
|
- **코드 연구**: 저장소 및 문서에서 솔루션 검색
|
|
- **리드 생성**: 기업 및 개인 조사
|
|
- **학술 연구**: 학술 기사 및 기술 논문 찾기
|
|
|
|
```python
|
|
from crewai_tools import SerperDevTool, GitHubSearchTool, YoutubeVideoSearchTool, TavilySearchTool, TavilyExtractorTool
|
|
|
|
# Create research tools
|
|
web_search = SerperDevTool()
|
|
code_search = GitHubSearchTool()
|
|
video_research = YoutubeVideoSearchTool()
|
|
tavily_search = TavilySearchTool()
|
|
content_extractor = TavilyExtractorTool()
|
|
|
|
# Add to your agent
|
|
agent = Agent(
|
|
role="Research Analyst",
|
|
tools=[web_search, code_search, video_research, tavily_search, content_extractor],
|
|
goal="Gather comprehensive information on any topic"
|
|
)
|
|
``` |