Memory

Memory is what Fluso carries forward between chats. Your preferences, durable facts about your work, and the context of whichever project you are in. It loads quietly at the start of every conversation so you do not have to explain yourself twice. The rule it follows is stricter than you might expect. Memory saves stable things, not everything. A preference you have stated, a fact about your team, a decision you made inside a project. Not the message you sent five minutes ago, not the one-off question, not whatever you happened to ask about today.

​

Three scopes

Memory lives in three layers, each with its own reach. Global preferences. User-level things that should apply everywhere. Your timezone, the response style you have asked for, workflow choices, standing instructions like “always show me drafts in plain text”. Global long-term memory. Durable facts and patterns about you that are useful across every project. The shape of your role, the kind of work you do, the people and companies that recur. Project context. Facts, decisions, conventions, and preferences that belong only to the project you are in. The Q3 roadmap decision. The naming convention you agreed with the team. The pricing approach for this client. The split matters because Fluso is careful about scope. If something looks project-specific, it stays in project context and does not leak into global memory. One client’s notes do not surface inside another client’s project.

​

How it loads

At the start of every new chat, Fluso pulls in three things as background context:

• Your global preferences
• Your global long-term memory
• The current project’s context, if you are in a project

Memory is context for the conversation, not a script. Your current message still drives the response.

​

How it updates

Two paths. Both are conservative on purpose. You ask explicitly. Say “remember this”, “forget this”, “add this to memory”, or “update my preference” and Fluso changes memory directly. Clear intent only. A passing line like “I like detailed answers” is not treated as a memory write. That kind of inference goes through the other path. Background learning. After replies, a background process reviews the conversation and decides whether anything durable came up. Preferences get checked often, because they tend to be short and useful. Long-term observation is more cautious: it activates after roughly 30,000 tokens of eligible conversation, then may write to global memory, global preferences, or project context depending on what it finds. If nothing durable is there, it writes nothing. The guardrail on explicit updates exists for a reason. Vague or accidental wording should not mutate the layer that follows you across every chat.

​

What gets saved

• Stable preferences you have stated.
• Durable facts about your work, your team, the projects you run.
• Decisions, conventions, and patterns inside a project.

​

What does not get saved

• One-time task details.
• Greetings and small talk.
• Temporary instructions for a single chat.
• Guesses Fluso is not confident about.

This line is what keeps memory useful instead of noisy. The longer Fluso runs alongside your work, the more visible the difference becomes.

​

What memory is not

Memory is not a full transcript archive. Fluso does not keep every message you have ever sent. It keeps the curated layer of things worth carrying forward. Preferences, durable facts, project context. If you need the exact text of an old conversation, that is a different question for a different system. Memory is what helps the next chat start in the right place.

​

Next

For the patterns that build a useful memory layer over time, see Going deeper.