One client, many collections
A Chroma client points at a directory on disk. Inside the client you create collections — independent indexes that share the same on-disk store. A typical app has one collection per content type (docs, conversations, code) so each can have its own embedding model and metadata schema.
Pin your distance metric at creation
Chroma defaults to cosine, but you can opt into L2 or inner product. Choose at creation time — changing the metric on an existing collection means rebuilding it. For most text use cases, leave it on cosine.