Save and recall Memory from C# and tools

Overview

IAgentMemoryProvider supplies a scope-bound IAgentMemoryService. Direct calls are useful when the application knows a fact is confirmed; model tools are useful when the agent needs retrieval. Using both is fine if each concern has one owner.

A provider binds the service to its scope

Resolve IAgentMemoryService through the trusted IAgentMemoryProvider for the agent's principal/scope. Code can save a confirmed fact directly, while exposed memory tools let the model request retrieval. The service should not accept an arbitrary principal supplied by the prompt as its authority. One clear owner should decide when inferred information becomes durable.

A correction is a lifecycle operation

If a user changes a preference, update or supersede the old fact through the supported lifecycle rather than accumulating contradictory statements indefinitely. Recall should provide the applicable active fact and its context. Memory is useful because it outlives a single chat thread, but its actual process durability still depends on the configured SQL-backed feature and storage.

Save and recall a scoped fact

1. Enable SQL mode and configure the required models. Resolve Memory through trusted scope selection.
2. Save a verified preference with source/time metadata and keep its returned ID. Choose Fact, Rule, Instruction, Observation or Procedural intentionally.
3. Recall before answering; use explicit ID updates for corrections and ForgetMemory for deletion. Select agent-memory tools without registering the same functions twice.

using FabrCore.Services.Memory.Abstractions;
using FabrCore.Services.Memory.Models;

// Call these methods from OnMessage or other application-controlled agent methods.
public static class MemoryLifecycle
{
    public static async Task<Guid> RememberPreferenceAsync(IAgentMemoryService memory, CancellationToken ct = default)
    {
        var entry = await memory.SaveMemoryAsync("Response preference", MemoryType.Instruction,
            "The user prefers concise responses.", metadata: new() { ["source"] = "explicit-user-preference" }, ct: ct);
        return entry.Id; // Persist this ID in application state if later updates need it.
    }

    public static Task<MemoryEntry> ArchiveAsync(IAgentMemoryService memory, Guid id, CancellationToken ct = default)
        => memory.UpdateMemoryAsync(id, temperature: MemoryTemperature.Cold, ct: ct);

    public static Task<MemoryEntry> RestoreAsync(IAgentMemoryService memory, Guid id, CancellationToken ct = default)
        => memory.UpdateMemoryAsync(id, temperature: MemoryTemperature.Warm, ct: ct);

    public static async Task<string> RecallAsync(IAgentMemoryService memory, string query, CancellationToken ct = default)
        => memory.FormatRecallContext(await memory.RecallAsync(query, ct: ct));
}

Go deeper

Explore the related documentation.

• FabrCore Knowledge
• FabrCore Database Modes
• Memory Lifecycle