jyapayne/langflow
1
0
Fork 0
Code Issues Pull requests Projects Releases 1 Packages Wiki Activity Actions

docs: user feedback items (#9122)

Browse source 
* db-location-and-agent-memory

* cleanup

* postgresql-for-agent-memory

* postgresql-in-message-history

* remove-mcp-tutorial-note
This commit is contained in:
Mendon Kissling 2025-07-22 12:22:30 -04:00 • committed by GitHub
commit 8f84d9100d
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
7 changed files with 44 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

19
docs/docs/Agents/agents.mdx
View file

@ -122,6 +122,25 @@ In the **Agent Instructions** (`system_prompt`) field, you can provide custom in
These instructions are applied in addition to the **Input** (`input_value`), which can be entered directly or provided through another component, such as a **Chat Input** component.
### Agent memory
Langflow Agents have built-in memory enabled by default that allows them to remember previous messages in a conversation.
This memory acts as a rolling chat history window, ensuring the Agent can reference earlier exchanges and maintain context without requiring a separate [Message History](/components-helpers#message-history) component.
The Agent’s internal chat history is stored in the Langflow database, just like the [Message History](/components-helpers#message-history) helper component.
The default storage option in Langflow is a [SQLite](https://www.sqlite.org/) database stored in your system's cache directory:
- **macOS Desktop**: `/Users/<username>/.langflow/data/database.db`
- **Windows Desktop**: `C:\Users\<name>\AppData\Roaming\com.Langflow\data\langflow.db`
- **OSS macOS/Windows/Linux/WSL (uv pip install)**: `<path_to_venv>/lib/python3.12/site-packages/langflow/langflow.db` (Python version may vary)
- **OSS macOS/Windows/Linux/WSL (git clone)**: `<path_to_clone>/src/backend/base/langflow/langflow.db`
If your Langflow deployment has `LANGFLOW_DATABASE_URL` set to PostgreSQL, the Agent memory will use the PostgreSQL database.
Each conversation is associated with a session ID, so messages are grouped and retrieved per session.
This means your chat history is saved and can be accessed or retrieved later, even if you refresh or revisit the flow.
The number of stored messages can be configured in the **Number of Chat History Messages** field in the Agent component.
### Tools
Agents are most useful when they have the appropriate tools available to complete requests.