Setup & Usage

Memory is Fluent's local long-term knowledge layer. In other words – a fully local, private Knowledge Base.

Use it for information that should stay available across many tasks: writing style, product documentation, project notes, profiles, reference material, and similar reusable context.

How It Works

Fluent's Memory is powered by a native hybrid RAG engine that retreives semantically relevant data based on request.

When you add notes or files, Fluent indexes them locally so it can search them later and pull out the relevant parts during a request. You do not have to manage the retrieval details manually.

Groups

Memory is organized into groups.

A group should represent one domain, such as:

• A writing style
• One project
• Product documentation
• Support material
• Personal profile information

Fluent starts with a few practical examples such as My Profile, My Writing Style, and My Projects.

Start

Open Settings → Memory and create a group.

Good first groups:

• My Writing Style
• Current Project
• Product Docs
• Support Answers

Choose a group name that already tells you what belongs there.

Add Content

Memory can contain both notes and files.

You can add:

• Notes
• Individual files
• Entire folders

Use files for stable reference material. Use notes for information that changes over time and should be easy to edit.

This split is important because not all useful memory belongs in a document.

Drag and drop works, and you can also use the file picker. Folder imports are capped, so use them for focused collections rather than large archives.

Use Notes

Use notes for information that changes often.

Good examples:

• Personal profile details
• Writing style rules
• Project priorities
• Product facts that change over time
• Client or team preferences

Notes are usually easier to maintain than trying to keep the same information inside a document.

Use Memory In Requests

There are two common ways to use Memory: either directly in the Smart Panel by typing a @ notation, or written in the actions like:

My action prompt... Use {{ @"My Writing Style" }} to generate a response that sounds 100% like myself. Use {{ @"Product Docs" }} for reference about my product.

The syntax is similar to Variables. If your memory group has whitespaces in name, you have to wrap the whole name in double quotes: {{ @"My Style"}}.

Memory is not only storage. Fluent can search it. You can:

• Reference a specific group directly in prompts and actions
• Enable the Memory integration and let Fluent use Memory tools during MCP workflows

Direct group references are good when you already know which group should be used. Tool-based retrieval is useful when Fluent needs to search more flexibly.

Enable the Memory integration in Settings → Integrations if you want Fluent to use Memory tools.

Why Use It

Memory improves tasks that depend on continuity or internal reference material.

Examples:

• Replies that should follow your usual tone
• Answers grounded in product documentation
• Project work that depends on current priorities
• Actions that would otherwise need a long repeated prompt

Reindex

Reindex the group after file changes.

This step matters for file-based memory. If the source material changed and the group was not reindexed, retrieval may still use older content.

Disable Items

If an item is temporarily irrelevant, disable it instead of deleting it.

This keeps the group cleaner without removing the source completely.