Chatbot injects 252k-token prompt every turn instead of RAG, dev asks to be talked out of it

louay_Sallakho · reddit · 2026-09-15

A developer running a WhatsApp support bot (27,000 customers) shares a deliberately extreme architecture: every message gets a 252,000-token prompt with no retrieval at all.

Prompt structure

Why not RAG: they also run a retrieval version (55k tokens, 4.6x cheaper) but distrust it because retrieval fails silently — a classifier grabbing the wrong policy section yields confident wrong answers nobody notices. Sending everything removes the failure point.

Open questions posed: attention degradation at 250k tokens (are rules buried 80% down actually followed?), whether 'deciding branches at prompt-build time' has a proper name, and how others handle prompt versioning and rollback. Stack: Notion + n8n.

Original post →

More from coding & agent

coding & agent channel →