What the agent remembers.
Kautuka keeps two different things. Session history preserves a conversation. Memory facts are small, reusable items an agent can carry into later conversations.
Sessions and facts are separate
A session is the conversation you see. Facts are extracted after a completed turn, when the agent has fact extraction turned on, and they are stored against that agent rather than against the session.
Because they are separate, you can delete a session and keep the facts it produced, or remove a fact without disturbing the conversation. A fact that outlives its session shows that its source session was deleted.
Turn it on
- Open the agent in Settings → Agents → Main.
- Enable Extract and persist memory facts after each run.
- Complete a run that states something lasting, then check the agent on the Memories page.
Extraction is selective. A completed run does not guarantee a fact, so if continuity matters, state what should be remembered explicitly rather than assuming it was captured.
Reviewing and correcting
Choose an agent on the Memories page to see its facts and sessions. Each fact shows its source, category, optional confidence, update time, and source session. You can edit a fact’s title, content, or category, delete it, or open the source session while it still exists.
Advanced memory settings control embeddings and the token budget for injected memory.
Memory and shared agents
Facts are stored against the agent, but each one carries the user it came from. When several people use a shared agent, only the acting user’s facts are recalled into their run, so one person’s remembered context does not surface in another’s conversation. Workspace files work the same way: a shared agent keeps a folder per user. Give people separate agents when they need different tools or settings, rather than to keep memory apart.
Technical details
Agent memories: GET /api/memories/agents/{agentId}. Edit or delete a fact: PATCH /api/memories/{factId}, DELETE /api/memories/{factId}. Delete a session: DELETE /api/sessions/{sessionId}. Memory policy: GET/PUT /api/settings/memory.
Verify by completing a run with an explicit lasting fact, checking the Memories page, then starting a later session and confirming the fact is injected when it is relevant.