The unified `hanzo` tool imports HanzoCloud from hanzo_tools.core, which hanzo-tools first shipped in 0.3.3 — but nothing in the dependency graph required it. hanzo-tools-api asked for `hanzo-tools-core>=0.1.0`, an empty shim whose own floor is hanzo-tools>=0.3.2, and 0.3.2 has no cloud.py at all. A resolver was therefore free to satisfy every constraint and still produce an install where `from hanzo_tools.core import HanzoCloud` raises ImportError. That is exactly what happened: the legacy-tool gate logged "unified hanzo tool not importable" and fell back, and the dev venv had to install hanzo-tools editable to get a working `hanzo`. Name the real dependency at the real floor: - hanzo-tools-api: hanzo-tools-core>=0.1.0 -> hanzo-tools>=0.3.4. It imports hanzo_tools.core directly, so it must depend on the package that owns it; the >=0.1.0 shim floor also still admitted the shadowing duplicate. - hanzo-tools-vector: hanzo-tools>=0.3.0 -> >=0.3.4 (cloud_vector.py). - hanzo-mcp: hanzo-tools>=0.3.2 -> >=0.3.4, hanzo-tools-api>=0.3.1 -> >=0.3.2. Metadata only, on versions not yet published. No version bumps. Co-authored-by: Hanzo Dev <dev@hanzo.ai>
hanzo-tools-vector
Vector search and embedding tools for Hanzo AI MCP.
Tools
index- Project indexing for semantic searchvector_index- Create and manage vector embeddingsvector_search- Semantic search across indexed content
Installation
pip install hanzo-tools-vector
# With embedding models
pip install hanzo-tools-vector[full]
Features
- Semantic code search
- Document embedding and retrieval
- Project-aware indexing
- Multiple embedding model support
Usage
from hanzo_tools.vector import TOOLS, VECTOR_AVAILABLE, register_tools
if VECTOR_AVAILABLE:
register_tools(mcp_server, permission_manager)
Part of hanzo-tools
This package is part of the modular hanzo-tools ecosystem.