How do you teach AI agents company-specific jargon? Four glossary approaches, none great
ladybawss · reddit · 2026-11-05
A Reddit discussion on a real enterprise problem: company-specific acronyms (e.g. "CPR" meaning something different internally) make LLMs fall back on training data and answer confidently wrong—they don't know what they don't know.
Four candidate approaches and their flaws:
- Glossary in the knowledge base, hoping retrieval catches it
- Glossary as a tool, hoping the model calls it
- Injecting the full glossary via system prompt with caching—fine when small, unwieldy at scale
- Knowledge graph with acronyms/aliases per node—graphs bring their own maintenance burden
The author asks how production systems like Glean and Harvey actually handle downstream leverage of bespoke terminology, and what alternatives exist.
More from coding & agent
- LMArena opens Agent Arena for agent evaluation — arena · 2026-11-05
- Running Qwen 27B Q4 at 0.7 tok/s on a 4GB-VRAM laptop as a main coding model — Felix_455-788 · 2026-11-05
- His agent now auto-labels his Google Calendar in the background — steren · 2026-11-05
- The security startups racing to rein in AI agents — pstAsiatech · 2026-11-05
- OpenAI October dev roundup: Decisions API, 12-hour caching, 8x faster Codex tokens — OpenAIDevs · 2026-11-05
- Datadog previews Canvas, a new way to collaborate with AI agents on observability — farooqib · 2026-11-05