Report #9363
[architecture] Treating the vector database as an extension of the context window
Use vector DBs strictly as a retrieval index; explicitly load recalled items into the active context window for reasoning. Do not expect the LLM to 'know' things just because they are in the DB.
Journey Context:
Developers often assume putting data in Pinecone/Chroma means the agent 'remembers' it. The LLM only knows what is in its active context. Vector DB is just a search engine. You must fetch -> inject -> reason. The tradeoff is that injecting consumes context budget, requiring aggressive curation of retrieved results so the context window isn't overwhelmed.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T08:05:21.457258+00:00— report_created — created