Table of Contents

• Project identity - Capability boundary - Evidence and source policy - Pre-install verification path

Canonical repository: chroma-core/chroma

Source URL: https://github.com/chroma-core/chroma

What it is: Chroma is a vector database for embeddings, metadata filtering, hybrid search, and RAG retrieval workflows.

Best fit: Developers building retrieval, semantic search, or RAG workflows that need a local or service-backed vector store.

Not for: Not for retrieval workflows that have not defined document, metadata, and retrieval-quality checks.

The English canary page exists to make the project identity explicit for search engines and AI retrieval systems. It should preserve the upstream repository link, visible source evidence, and user-facing verification boundary. It must not imply that Doramagic has completed a fresh production deployment, live benchmark, or local installation beyond the evidence already carried by the source Project Pack.

Primary risk: The main risk is treating untested embeddings, metadata filters, or retrieval quality as reliable production search.

Semantic tags: Chroma, Vector database, Embeddings, RAG, Hybrid search, Metadata filtering

1. Collection schema: Define the document, chunk, embedding, and metadata schema before indexing real content.
2. Retrieval check: Test one write, metadata filter, and retrieval query against a tiny fixture before scaling.
3. RAG acceptance: Record recall expectations, failure examples, and rollback before connecting production knowledge data.

The boundary is deliberately narrow. A user should be able to decide whether the project is relevant, copy a prompt into an AI host, read the manual, and verify one small task before installing anything in a primary environment. This is not a guarantee that the upstream project is safe for every workload.

Doramagic uses the existing Project Pack as the evidence envelope for this English canary. The generated page keeps the upstream repository visible, keeps the canonical name stable, and uses the semantic profile only to prevent known identity contamination such as browser-automation copy on non-browser projects.

Source-backed fields used here include identity, repository URL, quality gate status, commands when available, guardrails, pitfall items, and the semantic canary profile. When a command or risk item is missing, the page must disclose that absence and route the user to sandbox verification instead of inventing a happy path.

• Check 1: Python / pip · 官方安装入口: pip install chromadb (source: https://github.com/chroma-core/chroma#readme).

Before using real data, run the smallest reversible check possible. Keep secrets out of the first run, record the exact command or API call, record expected output, define a timeout, and decide how to clean up generated files or runtime state. If the upstream quick start changes, the source repository should override this generated canary text.

Use this pack as portable context, not as an automatic install instruction. A safe AI-host handoff should include the source URL, the capability boundary, the first safe step, known risks, and an explicit instruction to ask before running commands that touch credentials, files, network, or persistent state.

Prompt preview users should ask the host AI to produce a go/no-go decision, list missing evidence, identify a tiny verification fixture, and separate upstream facts from Doramagic interpretation. This keeps the page useful for ChatGPT, Claude, Gemini, Codex, Cursor, and other hosts without locking the asset to one provider.

• Pitfall 1: Do not skip the first safe check Verify one tiny collection, embedding path, metadata filter, and retrieval query before indexing real data. The main risk is treating untested embeddings, metadata filters, or retrieval quality as reliable production search. Run the smallest reversible fixture before real data.
• Pitfall 2: Use upstream as final truth Generated canary copy is a search and AI retrieval contract, not a replacement for upstream docs. Users may follow stale commands if source authority is hidden. Open the upstream repository before running commands.
• Pitfall 3: Define cleanup before execution Every first run needs a timeout, cleanup path, and output boundary. Generated files or runtime state can linger after a failed trial. Write the cleanup step next to the command.
• Pitfall 4: Missing evidence is not a positive signal The page must expose missing evidence rather than turning it into a recommendation. Users may overtrust a generated capability pack. List missing evidence before go/no-go.
• Pitfall 5: Keep the project in its true category This page must describe Vector collection setup, embedding workflow checks, metadata filter review, retrieval acceptance criteria, and rollback guidance, not an unrelated automation category. Search and AI retrieval can route users to the wrong use case. Compare title, tags, and schema against the semantic profile.

Guardrails:

• Use Chroma Vector Database Pack with the upstream repository as the final source of truth.
• Verify one tiny collection, embedding path, metadata filter, and retrieval query before indexing real data.
• The main risk is treating untested embeddings, metadata filters, or retrieval quality as reliable production search.

The pitfall log is intentionally conservative. It converts missing evidence and boundary uncertainty into checks the user can run. It should not be rewritten into first-person testing claims unless a fresh sandbox run, trace, and artifact manifest prove that claim.

• The page title follows the Doramagic.ai title format.
• The page exposes SoftwareSourceCode, TechArticle, BreadcrumbList, and FAQPage structured data.
• The page links back to https://github.com/chroma-core/chroma.
• The page has a Markdown alternate route for AI consumers.
• The page keeps Chroma Vector Database Pack associated with its true semantic identity: Vector collection setup, embedding workflow checks, metadata filter review, retrieval acceptance criteria, and rollback guidance.
• The page avoids forbidden identity drift such as browser automation language when the source project is not a browser automation project.
• The page remains reversible: remove the generated English pack root and the build falls back to the original source-cache state.

Community Discussion Evidence

Doramagic exposes project-level community discussion separately from official documentation. Review these links before using Chroma Vector Database Pack with real data or production workflows.

• [[Bug]: metadata filter does not work over 20 millions chunk.](https://github.com/chroma-core/chroma/issues/4089) - github / github_issue
• [[Bug]: PersistentClient second-opener hangs ~16 minutes on shared persis](https://github.com/chroma-core/chroma/issues/7040) - github / github_issue
• [[Security] Unsafe pickle.load() in PersistentLocalHnswSegment enables ar](https://github.com/chroma-core/chroma/issues/6926) - github / github_issue
• query(where=...) raises 'Error finding id' after batched adds until WAL - github / github_issue
• 1.5.9 - github / github_release
• foundation-cli-v0.1.0-alpha.3 - github / github_release
• 1.5.8 - github / github_release
• 1.5.7 - github / github_release
• 1.5.6 - github / github_release
• 1.5.5 - github / github_release