Multi-turn session memory (CSESSION): how it works and when to use it
Multi-turn session memory (CSESSION), keeps a bounded conversation buffer with both recent-window reads and semantic search across the whole chat. Here's how Crowkis does it and why it matters for cost and safety.
Your users ask the same things all day, phrased a hundred different ways. Multi-turn session memory (CSESSION) is how Crowkis keeps a bounded conversation buffer with both recent-window reads and semantic search across the whole chat.
How it works
Crowkis keeps a bounded conversation buffer with both recent-window reads and semantic search across the whole chat. It runs inside one Redis-compatible engine, so it composes with semantic caching, agent memory, and the other intelligence layers instead of being a separate service you wire together.
CSESSION ADD s1 user "my budget is 5k" CSESSION SEARCH s1 "what did they say about money?"
Why it matters
Repetitive LLM workloads are where the money is, and semantic caching can cut costs up to 60-70% on repetitive workloads. Multi-turn session memory (CSESSION) is part of what makes that reuse safe rather than reckless, the difference between a cache you trust in production and one you audit after every incident. It's one self-hosted binary, Redis-compatible, free to run.
Infrastructure earns the critical path one boring, verifiable feature at a time.