Agent sessions & memory

When you chat with an agent, Selu starts a session — a running instance of that agent with access to its tools and context. Understanding sessions helps explain when agents share state and when they don’t.

What is a session?

A session is the live environment your agent works in. It holds things like open files, active connections, and any in-memory state for the current conversation.

By default, Selu reuses an active session for the same agent across your conversations. This keeps things fast — the agent doesn’t need to restart for every message.

Session isolation

Some agents — especially ones that do hands-on work like writing code or managing files — benefit from keeping each conversation completely separate. If you switch between two conversations with a coding agent, you probably don’t want work from one thread leaking into the other.

Agents that need this behavior can be configured to use per-thread session isolation. When this is enabled, each conversation thread gets its own dedicated session. There’s no cross-thread state at all.

Note

This is a setting controlled by the agent developer, not something you configure yourself. If you’re seeing unexpected shared state between conversations on a stateful agent, contact the agent’s author about enabling per-thread isolation.

Memory across sessions

Sessions are temporary — they can restart, time out, or be recreated. Memory is how agents carry useful information forward across sessions and conversations.

Selu has three separate kinds of memory. See Personality & Memory for a full explanation of each.

Memory type	Scope	Survives session restart?
About you (profile)	All agents	Yes — always
Shared notes	All agents	Yes — stored in the database
Agent lessons	One agent	Yes — stored in the database

Persistent storage

Separate from memory, agents can also use persistent storage — a key-value store for exact data like sync checkpoints, user preferences, or structured state. Unlike shared notes (which are written in natural language for the LLM to read), persistent storage holds precise values.

You can view and delete an agent’s stored data from the agent’s detail page under Storage.