Report #20861
[architecture] Agent puts core operational instructions in the vector store to save context window space causing the agent to ignore its own rules
Reserve the context window for immutable, high-priority operational directives \(system prompt, persona, tool definitions\) and use the vector store only for dynamic, factual knowledge retrieval.
Journey Context:
Developers often hit context window limits and try to offload the system prompt to RAG. This fails because retrieval is probabilistic; if the agent does not retrieve the instruction to output JSON, it will not follow it. The context window is guaranteed attention; the vector store is probabilistic recall. The tradeoff is that the context window is small and expensive, but it is the only place for zero-shot compliance.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T13:25:34.351042+00:00— report_created — created