docs: Language model component doesn't include built-in chat memory. If-Else component no longer has a Message parameter.#9676
Conversation
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the WalkthroughDocumentation updates clarify that only the Agent component has built-in chat memory, refine memory vs. chat history distinctions, and refocus external memory guidance around a Redis-centric workflow. Minor UI terminology and parameter table adjustments are included. No code or public API changes. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
actor User
participant CI as Chat Input
participant MH as Message History
participant RCM as Redis Chat Memory
participant PT as Prompt Template ({memory})
participant LM as Language Model
participant CO as Chat Output
User->>CI: Enter message
CI->>MH: Retrieve recent messages (by session_id)
MH-->>CI: Messages
CI->>RCM: Retrieve external memory (by session_id)
RCM-->>CI: Memory snippets
CI->>PT: Populate template with {memory} + user input
PT->>LM: Prompt with context
LM-->>CO: Response
CO-->>User: Show response
CO->>MH: Append messages (history)
CO->>RCM: Store/update memory (if enabled)
note over MH,RCM: Storage can be Langflow default (history) and Redis (memory)
sequenceDiagram
autonumber
actor User
participant Agent as Agent (built-in memory)
participant LS as Langflow Storage
User->>Agent: Message
Agent->>LS: Retrieve prior messages (configured count)
Agent-->>User: Response
Agent->>LS: Append new messages
note over Agent,LS: Built-in chat memory applies to Agent only
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested labels
Suggested reviewers
✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
Status, Documentation and Community
|
github-actions
Bot
added
the
documentation
This comment has been minimized.
This comment has been minimized.
github-actions
Bot
added
documentation
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (6)
docs/docs/Components/components-prompts.mdx (1)
1-4: Add required frontmatter descriptionDocs must include a description field in frontmatter.
Apply this diff:
--- title: Prompt Template slug: /components-prompts +description: "Create prompt templates with variables and connect chat memory via Message History or Agent memory." ---docs/docs/Components/bundles-datastax.mdx (1)
1-4: Add required frontmatter descriptionMissing description in frontmatter.
Use:
--- title: DataStax slug: /bundles-datastax +description: "DataStax bundle components, including chat memory options and database tools." ---docs/docs/Develop/memory.mdx (2)
1-4: Add required frontmatter descriptionFrontmatter lacks a description; required by docs guidelines.
Apply:
--- title: Memory management options slug: /memory +description: "Configure storage, caching, and chat memory in Langflow, including Agent built-in memory and Message History." ---
15-15: Fix typo: “operation system” → “operating system”User-facing typo.
-The default storage path depends on your operation system and installation method: +The default storage path depends on your operating system and installation method:docs/docs/Components/components-helpers.mdx (2)
1-4: Add required frontmatter descriptionPlease include a description.
--- title: Helpers slug: /components-helpers +description: "Helper components such as Message History, Calculator, and utilities for managing data in flows." ---
153-153: Fix UI label typo: “Input input” → “Input field”User-facing text issue.
-5. Add a **Chat Input** component, and then connect it to the **Language Model** component's **Input** input. +5. Add a **Chat Input** component, and then connect it to the **Language Model** component's **Input** field.
🧹 Nitpick comments (2)
docs/docs/Components/components-helpers.mdx (2)
83-83: Capitalize Markdown and URLsFollow style guide for acronyms and proper nouns.
-Use markdown to format your answer, properly embedding images and urls. +Use Markdown to format your answer, properly embedding images and URLs.Also applies to: 138-138
48-50: Tighten repetitive bullet phrasingMinor style polish; avoids repeated “You need…”.
-* You need to store and retrieve chat memory for a language model component (not an agent). -* You need to retrieve chat memories outside the chat context, such as sentiment analysis flow that retrieves and analyzes recently stored memories. -* You want to store memories in a specific database that is separate from Langflow storage. +* Store and retrieve chat memory for a language model component (not an agent). +* Retrieve memories outside the chat context, such as a sentiment analysis flow that analyzes recent memories. +* Store memories in a specific database separate from Langflow storage.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (5)
docs/docs/Components/bundles-datastax.mdx(1 hunks)docs/docs/Components/components-helpers.mdx(3 hunks)docs/docs/Components/components-logic.mdx(0 hunks)docs/docs/Components/components-prompts.mdx(1 hunks)docs/docs/Develop/memory.mdx(2 hunks)
💤 Files with no reviewable changes (1)
- docs/docs/Components/components-logic.mdx
🧰 Additional context used
📓 Path-based instructions (1)
docs/docs/**/*.{md,mdx}
📄 CodeRabbit inference engine (.cursor/rules/docs_development.mdc)
docs/docs/**/*.{md,mdx}: All documentation content must be written in Markdown or MDX files located under docs/docs/, following the prescribed directory structure for guides, reference, how-to, concepts, and API documentation.
All documentation Markdown and MDX files must begin with a frontmatter block including at least title and description fields.
Use admonitions (:::tip, :::warning, :::danger) in Markdown/MDX files to highlight important information, warnings, or critical issues.
All images referenced in documentation must include descriptive alt text for accessibility.
All code examples included in documentation must be tested and verified to work as shown.
Internal links in documentation must be functional and not broken.
Content must follow the style guide: professional but approachable tone, second person voice, present tense, short paragraphs, sentence case headers, inline code with backticks, bold for UI elements, italic for emphasis, and parallel structure in lists.
Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
Files:
docs/docs/Components/components-prompts.mdxdocs/docs/Components/bundles-datastax.mdxdocs/docs/Components/components-helpers.mdxdocs/docs/Develop/memory.mdx
🪛 LanguageTool
docs/docs/Components/components-helpers.mdx
[style] ~50-~50: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...nd analyzes recently stored memories. * You want to store memories in a specific da...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: build-and-deploy
🔇 Additional comments (5)
docs/docs/Components/components-prompts.mdx (1)
29-31: Approve: internal links verified and clarification is accurateLinks to
/components-helpers#message-historyand/memoryresolve correctly; the Agent component’s built-in chat memory clarification stands.docs/docs/Components/bundles-datastax.mdx (1)
22-24: LGTM: Narrowed scope to Agent built-in chat memoryThe admonition correctly reflects Agent-only built-in memory and clarifies no external DB needed for agentic flows.
docs/docs/Develop/memory.mdx (1)
89-106: LGTM: Clear separation of chat history vs. chat memory and Agent built-in memoryThe revisions improve conceptual clarity and accurately scope built-in memory to the Agent; session ID guidance is precise.
Also applies to: 110-134
docs/docs/Components/components-helpers.mdx (2)
43-53: LGTM: Agent built-in memory + when to use Message HistoryAccurate and helpful scoping.
96-99: LGTM: “Language Model core component” wording and “Input field” UI labelMatches UI terminology.
github-actions
Bot
added
documentation
This comment has been minimized.
This comment has been minimized.
Co-authored-by: Mendon Kissling <59585235+mendonk@users.noreply.github.com>
github-actions
Bot
added
documentation
|
|
Build successful! ✅ |
2 participants
Corrections for 2 items
Summary by CodeRabbit