Skip to main content
Learning modes control when and how a Learning Machine captures information. Each store can use a different mode.

Always Mode

Extraction happens automatically in the background. No agent tools involved.
Extraction starts concurrently with the model call, not after it. It sees the conversation up to the current user message, not the assistant’s response or tool calls from that same turn.
Best for: User Profile, User Memory, Session Context, Entity Memory

Agentic Mode

The agent receives tools and decides when to save.
Best for: Learned Knowledge, Decision Log

Tools by Store

Propose Mode

The agent proposes learnings. The user must confirm before saving.
Propose mode is enforced through system prompt instructions, not application code. The save_learning tool stays available throughout the run, so confirmation depends on the agent following its instructions rather than a code-level approval gate. Note: Propose mode is currently intended for Learned Knowledge.
Do not use Propose mode as the sole approval control for high-stakes, regulated, or compliance-sensitive workflows. Enforce required approval in application code before persisting a learning.
Best for: Low-risk learned knowledge that benefits from prompt-guided review

Combining Modes

Use different modes for different stores:

Defaults by Store

Choosing a Mode