Why should you care?

ERP assistants referencing prior invoices need persisted thread state, not stateless POST bodies.

See it live — copy this example

Paste into an ASP.NET Core 8+ / AgentNest project, then run with dotnet run (set your API keys in user-secrets).

// AgentNest.Agents/Memory/ThreadMemoryStore.cs
public sealed class ThreadMemoryStore(IDistributedCache cache)
{
    public async Task<ChatHistory> LoadAsync(string threadId, CancellationToken ct)
    {
        var json = await cache.GetStringAsync($"thread:{threadId}", ct);
        return json is null ? new ChatHistory() : JsonSerializer.Deserialize<ChatHistory>(json)!;
    }
    public Task SaveAsync(string threadId, ChatHistory history, CancellationToken ct) =>
        cache.SetStringAsync($"thread:{threadId}", JsonSerializer.Serialize(history),
            new DistributedCacheEntryOptions { SlidingExpiration = TimeSpan.FromHours(8) }, ct);
}

What happened?

• ThreadMemoryStore persists SK ChatHistory in Redis with sliding expiration for active deal conversations.
• Follow the steps below — typing the code yourself is the fastest way to learn.

Practice next

1. Add StackExchangeRedis cache in Program.cs.
2. Generate threadId per user conversation in API.
3. Load history before agent call, append assistant reply, save.
4. Encrypt serialized history with IDataProtector per tenant.
5. Add memory summary job when messages exceed 40.

Remember

Persist ChatHistory externally for multi-turn AgentNest chat. Use sliding expiration aligned with session policy. Summarize or truncate old turns proactively.

Long CRM deal threads

AEs chat about the same enterprise deal for two weeks.

Outcome: ThreadMemoryStore restores context; summarization keeps tokens under budget.