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>
170 lines
5.9 KiB
Plaintext
170 lines
5.9 KiB
Plaintext
---
|
|
title: Weaviate Vector Search
|
|
description: The `WeaviateVectorSearchTool` is designed to search a Weaviate vector database for semantically similar documents using hybrid search.
|
|
icon: network-wired
|
|
mode: "wide"
|
|
---
|
|
|
|
## Overview
|
|
|
|
|
|
The `WeaviateVectorSearchTool` is specifically crafted for conducting semantic searches within documents stored in a Weaviate vector database. This tool allows you to find semantically similar documents to a given query, leveraging the power of vector and keyword search for more accurate and contextually relevant search results.
|
|
|
|
[Weaviate](https://weaviate.io/) is a vector database that stores and queries vector embeddings, enabling semantic search capabilities.
|
|
|
|
## Installation
|
|
|
|
To incorporate this tool into your project, you need to install the Weaviate client:
|
|
|
|
```shell
|
|
uv add weaviate-client
|
|
```
|
|
|
|
## Steps to Get Started
|
|
|
|
To effectively use the `WeaviateVectorSearchTool`, follow these steps:
|
|
|
|
1. **Package Installation**: Confirm that the `crewai[tools]` and `weaviate-client` packages are installed in your Python environment.
|
|
2. **Weaviate Setup**: Set up a Weaviate cluster. You can follow the [Weaviate documentation](https://weaviate.io/developers/wcs/manage-clusters/connect) for instructions.
|
|
3. **API Keys**: Obtain your Weaviate cluster URL and API key.
|
|
4. **OpenAI API Key**: Ensure you have an OpenAI API key set in your environment variables as `OPENAI_API_KEY`.
|
|
|
|
## Example
|
|
|
|
The following example demonstrates how to initialize the tool and execute a search:
|
|
|
|
```python Code
|
|
from crewai_tools import WeaviateVectorSearchTool
|
|
|
|
# Initialize the tool
|
|
tool = WeaviateVectorSearchTool(
|
|
collection_name='example_collections',
|
|
limit=3,
|
|
alpha=0.75,
|
|
weaviate_cluster_url="https://your-weaviate-cluster-url.com",
|
|
weaviate_api_key="your-weaviate-api-key",
|
|
)
|
|
|
|
@agent
|
|
def search_agent(self) -> Agent:
|
|
'''
|
|
This agent uses the WeaviateVectorSearchTool to search for
|
|
semantically similar documents in a Weaviate vector database.
|
|
'''
|
|
return Agent(
|
|
config=self.agents_config["search_agent"],
|
|
tools=[tool]
|
|
)
|
|
```
|
|
|
|
## Parameters
|
|
|
|
The `WeaviateVectorSearchTool` accepts the following parameters:
|
|
|
|
- **collection_name**: Required. The name of the collection to search within.
|
|
- **weaviate_cluster_url**: Required. The URL of the Weaviate cluster.
|
|
- **weaviate_api_key**: Required. The API key for the Weaviate cluster.
|
|
- **limit**: Optional. The number of results to return. Default is `3`.
|
|
- **alpha**: Optional. Controls the weighting between vector and keyword (BM25) search. alpha = 0 -> BM25 only, alpha = 1 -> vector search only. Default is `0.75`.
|
|
- **vectorizer**: Optional. The vectorizer to use. If not provided, it will use `text2vec_openai` with the `nomic-embed-text` model.
|
|
- **generative_model**: Optional. The generative model to use. If not provided, it will use OpenAI's `gpt-4o`.
|
|
|
|
## Advanced Configuration
|
|
|
|
You can customize the vectorizer and generative model used by the tool:
|
|
|
|
```python Code
|
|
from crewai_tools import WeaviateVectorSearchTool
|
|
from weaviate.classes.config import Configure
|
|
|
|
# Setup custom model for vectorizer and generative model
|
|
tool = WeaviateVectorSearchTool(
|
|
collection_name='example_collections',
|
|
limit=3,
|
|
alpha=0.75,
|
|
vectorizer=Configure.Vectorizer.text2vec_openai(model="nomic-embed-text"),
|
|
generative_model=Configure.Generative.openai(model="gpt-4o-mini"),
|
|
weaviate_cluster_url="https://your-weaviate-cluster-url.com",
|
|
weaviate_api_key="your-weaviate-api-key",
|
|
)
|
|
```
|
|
|
|
## Preloading Documents
|
|
|
|
You can preload your Weaviate database with documents before using the tool:
|
|
|
|
```python Code
|
|
import os
|
|
from crewai_tools import WeaviateVectorSearchTool
|
|
import weaviate
|
|
from weaviate.classes.init import Auth
|
|
|
|
# Connect to Weaviate
|
|
client = weaviate.connect_to_weaviate_cloud(
|
|
cluster_url="https://your-weaviate-cluster-url.com",
|
|
auth_credentials=Auth.api_key("your-weaviate-api-key"),
|
|
headers={"X-OpenAI-Api-Key": "your-openai-api-key"}
|
|
)
|
|
|
|
# Get or create collection
|
|
test_docs = client.collections.get("example_collections")
|
|
if not test_docs:
|
|
test_docs = client.collections.create(
|
|
name="example_collections",
|
|
vectorizer_config=Configure.Vectorizer.text2vec_openai(model="nomic-embed-text"),
|
|
generative_config=Configure.Generative.openai(model="gpt-4o"),
|
|
)
|
|
|
|
# Load documents
|
|
docs_to_load = os.listdir("knowledge")
|
|
with test_docs.batch.dynamic() as batch:
|
|
for d in docs_to_load:
|
|
with open(os.path.join("knowledge", d), "r") as f:
|
|
content = f.read()
|
|
batch.add_object(
|
|
{
|
|
"content": content,
|
|
"year": d.split("_")[0],
|
|
}
|
|
)
|
|
|
|
# Initialize the tool
|
|
tool = WeaviateVectorSearchTool(
|
|
collection_name='example_collections',
|
|
limit=3,
|
|
alpha=0.75,
|
|
weaviate_cluster_url="https://your-weaviate-cluster-url.com",
|
|
weaviate_api_key="your-weaviate-api-key",
|
|
)
|
|
```
|
|
|
|
## Agent Integration Example
|
|
|
|
Here's how to integrate the `WeaviateVectorSearchTool` with a CrewAI agent:
|
|
|
|
```python Code
|
|
from crewai import Agent
|
|
from crewai_tools import WeaviateVectorSearchTool
|
|
|
|
# Initialize the tool
|
|
weaviate_tool = WeaviateVectorSearchTool(
|
|
collection_name='example_collections',
|
|
limit=3,
|
|
alpha=0.75,
|
|
weaviate_cluster_url="https://your-weaviate-cluster-url.com",
|
|
weaviate_api_key="your-weaviate-api-key",
|
|
)
|
|
|
|
# Create an agent with the tool
|
|
rag_agent = Agent(
|
|
name="rag_agent",
|
|
role="You are a helpful assistant that can answer questions with the help of the WeaviateVectorSearchTool.",
|
|
llm="gpt-4o-mini",
|
|
tools=[weaviate_tool],
|
|
)
|
|
```
|
|
|
|
## Conclusion
|
|
|
|
The `WeaviateVectorSearchTool` provides a powerful way to search for semantically similar documents in a Weaviate vector database. By leveraging vector embeddings, it enables more accurate and contextually relevant search results compared to traditional keyword-based searches. This tool is particularly useful for applications that require finding information based on meaning rather than exact matches.
|