ChromaDB
On this page
Purpose
ChromaDB stores embedded Data and searches it by semantic similarity. It can return matches to a flow or expose a search tool to Agent Core.
When to use it
- Build retrieval-augmented responses from prepared Data.
- Search a document collection by meaning.
- Give an agent access to a bounded collection of indexed content.
Required setup
Connect an Embedding Model to Embedding Model. Connect Data or DataFrame values to Ingest Data only when the node should add records.
How to use it
Tool Mode
- Index the collection with a Normal mode ChromaDB node.
- Add a second ChromaDB node with the same collection and embedding settings.
- Enable Tool Mode and connect Toolset to Agent Core.
- Test a specific retrieval question before publishing.
Normal mode
- Prepare source content as Data and connect it to Ingest Data.
- Connect an Embedding Model.
- Use a separate query node with the same collection and embedding settings.
- Enter Search Query and use Search Results or the DataFrame output.
Configuration
| Setting | What it controls | Recommended starting point |
|---|---|---|
| Collection Name | Base name for the isolated collection. | Use a short descriptive name. The default is arkus. |
| Search Query | Text used for semantic search. In Tool Mode, this is the agent argument. | Start with a specific question. |
| Cache Vector Store | Reuses the vector store during one component execution. | Leave on. It does not persist across runs. |
| Allow Duplicates | Checks an existing-record window before ingestion. | Leave off, but do not rely on it to remove duplicates within one incoming batch. |
| Search Type | Selects Similarity or MMR retrieval. | Start with Similarity. |
| Number of Results | Limits returned matches. | Start with 10. |
| Limit | Limits records checked for duplicate comparison. | Leave at 0 unless a bounded comparison is needed. |
Expected result
Search Results returns a list of Data records. The DataFrame output wraps the same matches. Results do not include similarity scores, and complex metadata can be removed before ingestion.
Reference details
Managed Chroma configuration is supplied by Arkus. Use separate ingestion and query nodes when the flow needs predictable retrieval behavior. Publishing creates a frozen collection for that deployment version. Runtime ingestion is rejected, and later Builder writes do not change the deployed collection.
If the embedding connection is missing, reconnect Embedding Model and rebuild. Run the node in a saved flow so Arkus can isolate its collection. If publishing cannot freeze the collection, restore managed Chroma or embedding access and publish again.
Related components
- Embedding Model supplies the required embeddings client.
- Agent Core can use ChromaDB in Tool Mode.
- Data Operations can shape Data before ingestion.