Private agent memory
Private, encrypted memory that carries your preferences, instructions, and facts across agent conversations.
Private agent memory lets Confluye remember useful context between conversations without turning it into workspace-wide knowledge. Memories belong to you inside one workspace and are retrieved only when they are relevant to your current request.
What the agent remembers
The agent stores small, curated memories rather than complete chat transcripts:
How you prefer answers, reports, and recurring work to be shaped.
Standing directions the agent should follow in later conversations.
Stable details that help the agent answer or act with the right context.
Writing durable memory requires confirmation. Confluye rejects secret-like content instead of saving it, and every memory has an expiry. Standard memories are retained for at most one year; memories marked sensitive are retained for at most 30 days.
Private by user and workspace
Confluye scopes memory to the signed-in user and the current workspace before decrypting it. Another member cannot retrieve, export, or delete your memories, even when you share a workspace. Your memory in one workspace is not available in another.
Encrypted at rest
Memory content is stored in an authenticated AES-256-GCM envelope, so plaintext is not written to storage. Each envelope records its format version and key version. During key rotation, Confluye can read records protected by the previous key and re-encrypt them with the active key; an old key cannot be retired while active memories still depend on it.
Member memory and end user memory
Private agent memory belongs to workspace members: the people who sign in to Confluye. It is a different system from the memory a workflow keeps for the external customers of a product you build on Confluye (End users and memory):
| Private agent memory | End user memory | |
|---|---|---|
| Belongs to | One signed-in member in one workspace | One external customer (end user) in one memory resource |
| Enabled by | FLUXUS_AGENT_MEMORY=true | FLUXUS_END_USERS=true |
| Written by | The agent with your confirmation | Automatically: each turn, plus facts extracted in the background |
| Scope | The member, across chats and workflow runs | The workflows connected to the memory resource |
| Who can read it | Only its owner; administrators see metadata only | Workspace Admins and Owners, with every read audited |
| Deletion | The owner deletes or exports memories | The owner edits or deletes; your product or the owner erases the customer |
The two never mix. A workflow run made for an end user does not receive the memory.* tools, so it cannot read or
write the private memory of the member who built or owns the workflow, and member memory never reaches an end
user's run.
Retrieval in chat
When a request could benefit from earlier context, the agent retrieves active, unexpired memories owned by you in the current workspace. It ranks matches by relevance, confidence, and recency, then uses the most relevant results as chat context. This works across Command Center threads, Workflow Copilot conversations, and agent workflow runs, except runs made for an end user.
Export and delete
You can export your active memories as JSON. The export contains only memories owned by you in the selected workspace.
Deleting a memory creates a tombstone: Confluye removes the encrypted content and its source reference, marks the memory deleted, and excludes it from future retrieval. The minimal deletion record remains for audit purposes, but the remembered content is no longer available.