Please add ChromaDB support to KiloCode

[CrazyAce25]

KiloCode currently supports LanceDB and Milvus Lite as memory/vector‑store backends. However, many local‑AI developers rely on LocalAI’s LocalRecall, which uses ChromaDB as its storage engine. Because KiloCode does not yet support ChromaDB, it cannot interoperate with LocalRecall, which blocks a large class of local‑first workflows.

Why ChromaDB matters
ChromaDB has become the de‑facto standard for lightweight, local vector storage in the open‑source AI ecosystem. It is:

simple to embed

easy to run locally

stable and mature

widely adopted

fully open‑source

extremely easy to integrate (Python API + HTTP server mode)

LocalAI, LM Studio integrations, and many local‑first RAG tools already use ChromaDB as their default memory engine.

Why this matters for KiloCode users
KiloCode + BMAD is an ideal workflow for building local AI apps. But without ChromaDB support, users cannot:

use LocalRecall as the memory layer

share memory between KiloCode and LocalRecall

build persistent local‑first apps that rely on ChromaDB

integrate with the broader local‑AI ecosystem

This creates a single point of friction in an otherwise seamless toolchain.

Why ChromaDB is a good fit for KiloCode
ChromaDB aligns perfectly with KiloCode’s philosophy:

local‑first

lightweight

developer‑friendly

no external cloud dependencies

easy to embed in desktop apps

ideal for offline AI workflows

Adding ChromaDB would immediately unlock interoperability with LocalAI and other local‑AI tools.

What’s needed -
A new memory backend option:

ChromaDB

With basic operations:

create collection

add embeddings

query by vector

delete/update entries

This is fully aligned with KiloCode’s existing memory backend architecture.

Impact -
Adding ChromaDB would:

enable KiloCode + BMAD + LocalRecall workflows

allow developers to build fully local AI apps with persistent memory

expand KiloCode’s compatibility with the broader local‑AI ecosystem

remove the current blocker for users who rely on LocalAI

make KiloCode more attractive to local‑first developers

Conclusion -
ChromaDB support is a small addition with a huge payoff. It would immediately unlock full compatibility between KiloCode and LocalAI’s LocalRecall, enabling powerful local‑first AI applications without cloud dependencies.

Thank you for considering this — it would be a major quality‑of‑life improvement, imo.