docs: Redesigned docs welcome page#8919
Closed
kurtenj wants to merge 7 commits into
Closed
Conversation
dosubot
Bot
added
the
size:XL
Contributor
|
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 WalkthroughThis update standardizes all internal documentation links to use the Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Browser
participant Docusaurus
participant CustomNavbar
participant CustomIcon
User->>Browser: Navigate to docs site
Browser->>Docusaurus: Load root or /docs path
Docusaurus->>CustomNavbar: Render Navbar (checks window width)
alt Desktop
CustomNavbar->>CustomIcon: Render social and theme icons
CustomNavbar->>Docusaurus: Render Algolia search, links, theme toggle
else Mobile
CustomNavbar->>Docusaurus: Render original mobile Navbar
end
Docusaurus->>Browser: Render homepage (index.tsx) with hero, quick links, cards
CustomIcon-->>Browser: Render requested SVG icon
Browser->>User: Display updated docs site with new navigation and homepage
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. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
github-actions
Bot
added
the
documentation
- Create custom React homepage with modern layout and responsive design - Add lightweight custom icon system and internal navigation links - Remove routing conflicts and maintain backward compatibility - Clean up project structure by consolidating components
github-actions
Bot
added
documentation
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 10
🔭 Outside diff range comments (12)
docs/docs/API-Reference/api-monitor.md (1)
1-4: Add adescriptionto the front-matter block.All docs files must include at least
titleanddescription.
Suggest:--- title: Monitor endpoints slug: /api-monitor +description: Reference for the /monitor API endpoints used to inspect and mutate builds, messages and transactions. ---docs/docs/Templates/travel-planning-agent.md (1)
1-4: Missingdescriptionin front-matter.--- title: Travel planning agent slug: /travel-planning-agent +description: Build a multi-agent Langflow template that plans a seven-day trip using tool-calling agents. ---docs/docs/Integrations/Arize/integrations-arize.md (1)
1-4: Adddescriptionto front-matter.--- title: Integrate Arize with Langflow slug: /integrations-arize +description: Configure Arize (Platform or Phoenix) to trace and monitor your Langflow applications. ---docs/docs/Integrations/Notion/notion-agent-meeting-notes.md (1)
1-4: Missingdescriptionfield.--- title: Notion Meeting Notes Agent slug: /integrations/notion/notion-agent-meeting-notes +description: Automate extraction of meeting action items and update Notion pages using Langflow. ---docs/docs/Templates/vector-store-rag.md (1)
1-4: Front-matter lacksdescription.--- title: Vector store RAG slug: /vector-store-rag +description: Starter project that demonstrates Retrieval-Augmented Generation with a vector store using Langflow. ---docs/docs/Components/components-io.md (1)
1-4: Directory casing breaks docs structure conventionThe file lives under
Components/, but the style guide specifies lowercase category folders (e.g.components/).
Please move the file (and update imports / sidebar) todocs/docs/components/components-io.mdto avoid accidental duplication and routing issues.docs/docs/Agents/agents.md (1)
42-43: Broken internal linkThe placeholder
/link does not resolve.
It should point to the dedicated “Configure tools for agents” page.-For more information, see [Configure tools for agents](/) +For more information, see [Configure tools for agents](/docs/agents-tools)docs/docs/Concepts/concepts-overview.md (1)
1-4: Add the mandatorydescriptionfield to front-matter
Docs guidelines requiretitle+description. Missing it will break SEO metadata and the sidebar generator.--- title: Langflow overview +description: High-level overview of Flows, Components, and the workspace layout in Langflow. slug: /concepts-overview ---docs/docs/Concepts/concepts-file-management.md (1)
1-4: Front-matter missingdescription
Same issue as above – please add a short description.docs/docs/Integrations/Nvidia/integrations-nvidia-ingest.md (1)
1-4:descriptionfield missing in front-matterAdd it for consistency with the docs template.
docs/docs/API-Reference/api-flows.md (1)
1-4: Adddescriptionto front-matterEvery API reference page should include a short description for search/SEO.
docs/docs/Components/components-helpers.md (1)
1-4: Missingdescriptionfront-matterAdd a concise description to comply with docs requirements.
🧹 Nitpick comments (71)
docs/src/theme/Footer.js (1)
25-31: Inline pixel tweak is fine, but consider extracting to CSS classHard-coding
right: '21px'/bottom: '21px'keeps magic numbers in JS. Moving the button positioning to the existingcustom.css(or a CSS module) makes future visual tweaks easier and keeps the React component lean.- style={{ - position: 'fixed', - right: '21px', - bottom: '21px', - zIndex: 100, + className="lf-search-btn", + style={{ + position: 'fixed', /* fallback if CSS fails */ + zIndex: 100,Then add in
docs/css/custom.css:.lf-search-btn{ right: 21px; bottom: 21px; }docs/docs/Templates/travel-planning-agent.md (1)
10-11: Use the official term “OpenAI”.
Open AIshould beOpenAIto stay consistent with Langflow docs terminology.-In this flow, multiple **Tool-calling agents** reason using an **Open AI** LLM +In this flow, multiple **Tool-calling agents** reason using an **OpenAI** LLMdocs/docs/Configuration/configuration-global-variables.md (1)
1-4: Missingdescriptionin front-matter headerGuidelines require every docs page to include at least
titleanddescriptionin the front-matter block.
Add a short, present-tense sentence that summarizes the page.docs/docs/Concepts/concepts-playground.md (2)
10-11: Link prefix looks good, but component name should be capitalized.
Per the docs style-guide, always refer to Langflow primitives with an initial capital letter, e.g. Input Component or Output Component.
Consider rewriting for consistency:-As long as you have an [Input or Output](/docs/components-io) component working +As long as you have an [**Input** or **Output** Component](/docs/components-io) working
32-33: Terminology consistency.
Same capitalization issue here – use Memory Components to stay aligned with the glossary.-To learn more about chat memories in Langflow, see [Memory components](/docs/components-memories). +To learn more about chat memories in Langflow, see [**Memory Components**](/docs/components-memories).docs/docs/Deployment/deployment-kubernetes-prod.md (1)
34-37: 👍 Corrected link, but minor grammar slip nearby.
The link prefix is now correct. Right after it we still have “If you have a created a …” (extra “a”). Consider trimming the duplicated article while you’re touching this sentence.-If you have a created a +If you have created adocs/docs/Templates/financial-report-parser.md (3)
8-9: Link updates OK, but capitalization.
Use “Structured Output” (capital “O”) to match component name.-[Structured output](/docs/components-helpers#structured-output) +[Structured Output](/docs/components-helpers#structured-output)
14-16: Plural noun – keep brand spelling consistent.
“Langflow instance” is fine, but the preceding bullet should start with an article for parallel structure:-[A running Langflow instance] +[A running **Langflow** instance]
40-41: Nice link correction.
Minor style: the component name is DataFrame Object per concepts page; consider mirroring the exact heading.docs/docs/Concepts/embedded-chat-widget.md (2)
10-11: Corrected link, but maintain sentence-case header reference.
“Publish pane” is a UI element → bold it for emphasis:-On the [Publish pane](/docs/concepts-publish), +On the [**Publish** pane](/docs/concepts-publish),
62-64: Consistent capitalisation for Session ID.
The term is capitalised elsewhere; update link text to match.-To add a custom [session ID](/docs/session-id) value +To add a custom [Session ID](/docs/session-id) valuedocs/docs/Components/components-prompts.md (2)
16-16: Capitalize the Doc Title and Concept Term
Vector RAG starter flowshould follow the project’s naming convention: capitalize each key word and the concept term Flow.-An example of modifying a prompt can be found in [Vector RAG starter flow](/docs/vector-store-rag), where a basic chatbot flow is extended to include a full vector RAG pipeline. +An example of modifying a prompt appears in the [Vector RAG Starter Flow](/docs/vector-store-rag), where a basic chatbot Flow is extended to include a full vector-RAG pipeline.
33-33: Grammar & Naming: possessive and capitalization
- Use the possessive form agent’s.
- Capitalize the starter-template name and concept term Flow.
-When variables are added to a prompt template, new fields are automatically created in the component. These fields can be connected to receive text input from other components to automate prompting, or to output instructions to other components. An example of prompts controlling agents behavior is available in the [sequential tasks agent starter flow](/docs/sequential-agent). +When variables are added to a prompt template, new fields are automatically created in the component. These fields can receive input from other components or output instructions downstream. An example of prompts controlling an agent’s behavior is available in the [Sequential Tasks Agent Starter Flow](/docs/sequential-agent).docs/docs/Develop/session-id.md (1)
36-36: Component name capitalizationThe component name in visible text should be capitalized: Message History.
-To retrieve messages from local Langflow memory, add a [Message history](/docs/components-helpers#message-history) component to your flow. +To retrieve messages from local Langflow memory, add a [Message History](/docs/components-helpers#message-history) Component to your Flow.docs/docs/Components/components-memories.md (2)
12-12: Capitalize ‘Agent’ when referring to the Langflow concept-Memory components provide access to their respective external databases **as memory**. This allows Large Language Models (LLMs) or [agents](/docs/components-agents) to access external memory for persistence and context retention. +Memory components provide access to their respective external databases **as memory**. This allows Large Language Models (LLMs) or [Agents](/docs/components-agents) to access external memory for persistence and context retention.
18-18: Commas with ‘because’LanguageTool flagged the comma before because as unnecessary.
-They are distinct from vector store components, because they are built specifically for storing and retrieving chat messages from external databases. +They are distinct from vector-store Components because they are built specifically for storing and retrieving chat messages from external databases.docs/docs/Templates/sequential-agent.md (1)
54-54: Hyphenate ‘problem-solving’ and capitalize ‘Agent’-To create your own multi-agent flow, see [Create a problem solving agent](/docs/agents). +To create your own multi-agent Flow, see [Create a Problem-Solving Agent](/docs/agents).docs/docs/Concepts/concepts-publish.md (2)
67-67: Visibility wordingOptionally capitalize Endpoint to match section titles elsewhere.
-For information on sending files to the Langflow API, see [Files endpoint](/docs/api-files). +For information on sending files to the Langflow API, see [Files Endpoint](/docs/api-files).
81-81: Capitalize widget title-For more information, see [Embedded chat widget](/docs/embedded-chat-widget). +For more information, see [Embedded Chat Widget](/docs/embedded-chat-widget).docs/docs/Templates/document-qa.md (1)
19-19: Add descriptive alt-text to the image.Empty alt-text violates the docs style guide and impacts accessibility.
- +docs/docs/Contributing/contributing-community.md (1)
35-35: Rephrase sentence for smoother grammar.The current wording is slightly awkward; this keeps second-person voice while clarifying purpose.
-For more information, see [Get help and request enhancements](/docs/contributing-github-issues). +For more information, see [Getting help and requesting enhancements](/docs/contributing-github-issues).docs/docs/Configuration/configuration-authentication.md (1)
31-33: Variable name inconsistency.The paragraph refers to
AUTO_LOGIN, but the env variable isLANGFLOW_AUTO_LOGIN. Recommend aligning with the actual variable.-If `AUTO_LOGIN` is enabled +If `LANGFLOW_AUTO_LOGIN` is enableddocs/docs/Integrations/Nvidia/integrations-nvidia-g-assist.md (1)
35-37: Fix unordered-list style and keep markdown-lint quiet.MD004 flags the dash style here. Switch to asterisks (used elsewhere) for consistency.
- - `text`: The response from NVIDIA G-Assist containing the completed operation result. -- The NVIDIA G-Assist message response is wrapped in a Langflow [Message](/docs/concepts-objects#message-object) object. +* `text`: The response from NVIDIA G-Assist containing the completed operation result. +* The NVIDIA G-Assist message response is wrapped in a Langflow [Message](/docs/concepts-objects#message-object) object.docs/docs/Integrations/Google/integrations-setup-google-cloud-vertex-ai-langflow.md (1)
6-6: Path correction acknowledged; minor phrasing tweak optional.Link targets are correct. Consider replacing “for authenticating” with “to authenticate” for smoother reading.
-Langflow integrates with the [Google Vertex AI API](https://console.cloud.google.com/marketplace/product/google/aiplatform.googleapis.com) for authenticating the [Vertex AI embeddings model](/docs/components-embedding-models#vertexai-embeddings) and [Vertex AI](/docs/components-models#vertexai) components. +Langflow integrates with the [Google Vertex AI API](https://console.cloud.google.com/marketplace/product/google/aiplatform.googleapis.com) to authenticate the [Vertex AI Embeddings](/docs/components-embedding-models#vertexai-embeddings) and [Vertex AI](/docs/components-models#vertexai) components.docs/docs/Components/components-agents.md (1)
24-24: Missing comma after introductory clause
Add a comma after “example” for correct punctuation.-For a multi-agent example see [Create a flow with an agent](/docs/agents). +For a multi-agent example, see [Create a flow with an agent](/docs/agents).docs/docs/Develop/memory.md (1)
26-40: Bulleted list uses “•” characters
Consider replacing UTF-8 bullets with standard markdown-so Docusaurus renders lists consistently across themes.Also applies to: 46-50
docs/docs/API-Reference/api-reference-api-examples.md (1)
160-162: Repetitive bullet phrasing
All three bullets start with “Use the Langflow API to …”. Vary wording or condense to avoid redundancy (LanguageTool flag).docs/docs/Integrations/mcp-component-astra.md (1)
38-39: Capitalize “Global variables” for terminology consistency-For more information, see [global variables](/docs/configuration-global-variables). +For more information, see [Global variables](/docs/configuration-global-variables).docs/docs/Templates/simple-agent.md (2)
10-12: Spell the vendor consistently
Open AI→OpenAI(no space) to match branding used elsewhere.-In this flow, the **Tool-calling agent** reasons using an **Open AI** LLM. +In this flow, the **Tool-calling agent** reasons using an **OpenAI** LLM.
15-16: Lower-case folder nameLike the previous file, this lives under
Templates/. Consider renaming the folder totemplates/(and adjusting sidebars) for consistency with the docs hierarchy list.docs/docs/Deployment/deployment-overview.md (2)
13-25: Minor readability & repetitionThree consecutive bullet items start with “The Langflow …”. Rephrase one or merge into preceding sentence to avoid monotony flagged by LanguageTool.
-* The **Langflow IDE** … -* The **Langflow runtime** … +The two modes are: +* **Langflow IDE** … +* **Langflow runtime** …
1-4: Folder casingCurrent path
Deployment/should bedeployment/per docs directory naming rules.docs/docs/Agents/agents-tools.md (2)
32-33: Starter-flow link OK but watch folder caseThe slug
/docs/simple-agentis fine, but this file sits inAgents/instead of lowercaseagents/. Align with folder-casing convention when convenient.
175-178: Typo in image alt text
agnet→agent.- +docs/docs/Develop/develop-overview.md (1)
1-4: Folder casing
Develop/should bedevelop/per docs folder guidelines.docs/docs/Get-Started/get-started-installation.md (2)
26-26: Duplicate “Quickstart” call-out – keep one, drop oneThe exact same “After confirming … [Quickstart]” sentence appears twice.
Repeating it adds noise without extra value.-After confirming that Langflow is running, create your first flow with the [Quickstart](/docs/get-started-quickstart).Delete either line 26 or line 130.
Also applies to: 130-130
160-162: Inconsistent capitalisation in link text“quickstart” in the last paragraph is lowercase, while the concept is capitalised elsewhere (“Quickstart”). Align for consistency.
-After installing Langflow, build and run a flow with the [quickstart](/docs/get-started-quickstart). +After installing Langflow, build and run a flow with the [Quickstart](/docs/get-started-quickstart).docs/docs/API-Reference/api-projects.md (1)
77-78: Missing punctuation & readabilityConsider ending the sentence with a colon before listing endpoints and wrapping each path in back-ticks for clarity.
-To add flows and components at project creation, retrieve the `components_list` and `flows_list` values from the [`/all`](/docs/api-reference-api-examples#get-all-components) and [/flows/read](/docs/api-flows#read-flows) endpoints and add them to the request body. +To add flows and components at project creation, retrieve the `components_list` and `flows_list` values from: +* [`/all`](/docs/api-reference-api-examples#get-all-components) +* [`/flows/read`](/docs/api-flows#read-flows) +and add them to the request body.docs/docs/Support/troubleshooting.md (1)
140-142: Grammar – plural noun agreement“components and integrations issues” reads awkwardly. Prefer singular “integration” or add an article.
-## Custom components and integrations issues +## Custom component and integration issuesdocs/docs/Develop/Clients/typescript-client.md (1)
56-56: Broken style: un-capitalized concept reference“API keys” is a Langflow concept and should follow the project’s terminology guide: capitalize API and use sentence-case for the rest, e.g. API keys → API Keys.
docs/docs/Concepts/concepts-voice-mode.md (2)
12-13: Term “Flow” should be capitalizedAccording to the style guide, Langflow concepts are capitalized.
Your flow must have…→Your Flow must have…
22-23: Agent is a component, capitalize for consistencySame guideline: “Simple agent” → “Simple Agent” to match other occurrences.
docs/docs/API-Reference/api-flows-run.md (1)
9-10: Typo: “amd” → “and”
/runand/webhookendpoints.docs/docs/Concepts/concepts-components.md (2)
19-20: Capitalize Flow when referring to the concept
add a component to a flow→add a component to a Flow
126-127: Anchor works, but wording repeats “component”Optional:
represented in the Workspace as component ports→represented in the Workspace as ports.docs/docs/Develop/webhook.md (2)
12-22: Capitalize “Component” in updated sentencesPer the terminology rules, “Component” should be capitalized when referring to Langflow components.
-2. Add a [Parser](/docs/components-processing#parser) component to your flow. - Create variables for values in the `template` the same way you would in a [Prompt](/docs/components-prompts) component. +2. Add a [Parser](/docs/components-processing#parser) Component to your Flow. + Create variables for values in the `template` the same way you would in a [Prompt](/docs/components-prompts) Component.
61-63: Minor: capitalize “Flow”-- [Flow trigger endpoints](/docs/api-flows-run) +- [Flow Trigger Endpoints](/docs/api-flows-run)docs/docs/Components/components-embedding-models.md (2)
280-286: Capitalize “Flow” to comply with style guide-1. Create a [Vector store RAG flow](/docs/vector-store-rag). +1. Create a [Vector Store RAG Flow](/docs/vector-store-rag).
424-429: Capitalize “Flow” for consistency-For example, this flow connects a local Ollama server running a `all-minilm:latest` embeddings model to a [Chroma DB](/docs/components-vector-stores#chroma-db) vector store to generate embeddings for split text. +For example, this Flow connects a local Ollama server running an `all-minilm:latest` embeddings model to a [Chroma DB](/docs/components-vector-stores#chroma-db) Vector Store to generate embeddings for split text.docs/docs/Contributing/contributing-components.md (3)
46-50: Clarify bullet & fix punctuationThere’s an unmatched parentheses and the bullet starts with a capitalized clause but lacks a terminating period.
- For more information, see [Contributing bundles](/docs/contributing-bundles#add-the-bundle-to-the-frontend-folder). + For more information, see [Contributing Bundles](/docs/contributing-bundles#add-the-bundle-to-the-frontend-folder).
52-56: Capitalize “Component” in reference link-For more information on creating your custom component, see [Create custom Python components](/docs/components-custom-components). +For more information on creating your custom Component, see [Create Custom Python Components](/docs/components-custom-components).
125-129: Update link text to match title casing-Include tests for your changes using `ComponentTestBase` classes. For more information, see [Contribute component tests](/docs/contributing-component-tests). +Include tests for your changes using `ComponentTestBase` classes. For more information, see [Contribute Component Tests](/docs/contributing-component-tests).docs/docs/Concepts/concepts-overview.md (1)
14-18: Capitalize the concept names to stay consistent with the style-guide
ComponentandFlowshould be capitalised when referring to Langflow concepts.-Flows consist of [components](/docs/concepts-components) that you configure ... +A Flow consists of [Components](/docs/concepts-components) that you configure ... -A flow can be as simple as the [basic prompting flow](/docs/get-started-quickstart) ... +A Flow can be as simple as the [Basic Prompting Flow](/docs/get-started-quickstart) ...Also applies to: 55-57
docs/docs/Concepts/concepts-file-management.md (1)
37-45: Verify anchors and follow naming conventions
- Anchor
#filemight actually be#file-componenton the Components page – please double-check.- Use the full concept name “File Component” when linking.
-1. Include the [File](/docs/components-data#file) component in a flow. +1. Include the [File Component](/docs/components-data#file-component) in a flow.Same for lines 41 and 44.
docs/docs/Integrations/Nvidia/integrations-nvidia-ingest.md (2)
14-15: Nit: break up the long sentence for readabilityCurrent sentence is >200 chars. Splitting also removes the comma complaint flagged by LanguageTool.
-...objects. `Ingestor` accepts additional configuration options for data extraction from other text formats. To configure these options, see the [component parameters](/docs/integrations-nvidia-ingest#parameters). +...objects. +`Ingestor` accepts additional configuration options for other text formats. See the [component parameters](/docs/integrations-nvidia-ingest#parameters) for details.
88-90: Insert the missing comma after the introductory phrase-The **NVIDIA Retriever Extraction** component outputs a list of [Data](/docs/concepts-objects#data-object) objects where each object contains: +The **NVIDIA Retriever Extraction** component outputs a list of [Data](/docs/concepts-objects#data-object) objects, where each object contains:docs/docs/API-Reference/api-flows.md (1)
11-12: Capitalize “Flow”-If you want to use the Langflow API to run a flow, see ... +If you want to use the Langflow API to run a Flow, see ...docs/docs/Components/components-helpers.md (1)
16-25: Use specific anchors and capitalised concept namesConsider linking directly to the Data Object anchor and capitalise properly:
-...as [Data](/docs/concepts-objects) objects... +...as [Data](/docs/concepts-objects#data-object) Objects...Likewise for the DataFrame Object link.
docs/docs/Components/components-custom-components.md (1)
350-356: Spelling error: “Mensage” → “Message”
The example input label reads “Mensage”, which is likely a typo.- MessageTextInput( - name="message", - display_name="Mensage", + MessageTextInput( + name="message", + display_name="Message",docs/docs/Templates/memory-chatbot.md (2)
12-13: Link prefix change correct, but image alt text still missing
The new/docs/...link works; however, the nearby image on line 25 still has an empty alt tag ().
Consider adding descriptive alt text per docs style guide.- +
75-78: Second batch of links OK; same alt-text issue applies to image on line 63
Please add an alt description to/img/messages-logs.pngfor accessibility.docs/docs/Components/components-data.md (2)
104-110: Link corrected; MD036 still raised
The heading right below (“Parameters”) is rendered via**Inputs**emphasis instead of a proper###heading, triggering markdown-lint rule MD036. Converting it to a real heading will silence the linter.-**Inputs** +### Inputs
280-283: Parser / Chat Output links correct; watch long lines
Links are fine. Very long markdown table lines ( >120 chars) may hurt readability but are not blocking.Also applies to: 300-304
docs/docs/Components/components-models.md (2)
226-233: Groq section link OK, but consider shortening sentence
The sentence starting “1. To use this component in a flow…” is long and a bit hard to scan. Splitting after the parenthetical would improve readability, but optional.
275-281: Comma missing after introductory clause
Static analysis flagged this.-…authenticate. In this example based on the [Basic prompting flow](/docs/basic-prompting), the **Hugging Face API** model component… +…authenticate. In this example, based on the [Basic prompting flow](/docs/basic-prompting), the **Hugging Face API** model component…docs/docs/API-Reference/api-build.md (1)
106-109: Table cell ends with a period – minor consistency nit
The row forstop_component_idends with “contents).” whereas the one above doesn’t. Recommend dropping the period for consistency across rows.docs/docs/Concepts/mcp-server.md (1)
355-356: Fix inconsistent list style in "See also" section.The static analysis correctly identifies inconsistent unordered list styling. The documentation should use consistent bullet points throughout.
Apply this diff to fix the list style consistency:
-- [Use Langflow as an MCP client](/docs/mcp-client) -- [Use a DataStax Astra DB MCP server](/docs/mcp-component-astra) +* [Use Langflow as an MCP client](/docs/mcp-client) +* [Use a DataStax Astra DB MCP server](/docs/mcp-component-astra)docs/docs/Get-Started/get-started-quickstart.md (1)
520-521: Fix inconsistent list style in "Next steps" section.The static analysis correctly identifies inconsistent list styling. The documentation should use consistent bullet points (preferably dashes based on the existing pattern in the file).
Apply this diff to fix the list style consistency:
-* [Model Context Protocol (MCP) servers](/docs/mcp-server) -* [Langflow deployment overview](/docs/deployment-overview) +- [Model Context Protocol (MCP) servers](/docs/mcp-server) +- [Langflow deployment overview](/docs/deployment-overview)docs/src/theme/Navbar.js (3)
30-38: Consider externalizing social links configuration.The hardcoded social links work for now but could be moved to a configuration file for better maintainability.
Consider moving to a separate config file:
+// config/socialLinks.js +export const socialLinks = [ + { + href: "https://github.com/langflow-ai/langflow", + icon: "github", + label: "GitHub", + }, + { href: "https://x.com/langflow_ai", icon: "x", label: "X" }, + { href: "https://discord.gg/langflow", icon: "discord", label: "Discord" }, +];
88-95: Move inline styles to CSS for better maintainability.The separator styling could be moved to CSS classes for consistency with the rest of the navbar styling.
Consider moving to CSS:
- <div - style={{ - width: '1px', - height: '20px', - background: 'var(--ifm-color-emphasis-300)', - margin: '0 0.25rem' - }} - ></div> + <div className="lf-navbar-separator"></div>And add the corresponding CSS class.
70-70: Consider consistent icon usage pattern.The component mixes direct lucide-react imports (
MonitorDown,Moon,Sun) with the customIconcomponent. Consider using a consistent approach.Also applies to: 104-104, 106-106
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (3)
docs/package-lock.jsonis excluded by!**/package-lock.jsondocs/static/img/lf-agent.pngis excluded by!**/*.pngdocs/yarn.lockis excluded by!**/yarn.lock,!**/*.lock
📒 Files selected for processing (80)
docs/css/custom.css(6 hunks)docs/docs/API-Reference/api-build.md(3 hunks)docs/docs/API-Reference/api-files.md(5 hunks)docs/docs/API-Reference/api-flows-run.md(4 hunks)docs/docs/API-Reference/api-flows.md(3 hunks)docs/docs/API-Reference/api-monitor.md(1 hunks)docs/docs/API-Reference/api-projects.md(1 hunks)docs/docs/API-Reference/api-reference-api-examples.md(4 hunks)docs/docs/Agents/agents-tools.md(3 hunks)docs/docs/Agents/agents.md(4 hunks)docs/docs/Components/components-agents.md(1 hunks)docs/docs/Components/components-custom-components.md(4 hunks)docs/docs/Components/components-data.md(5 hunks)docs/docs/Components/components-embedding-models.md(3 hunks)docs/docs/Components/components-helpers.md(4 hunks)docs/docs/Components/components-io.md(5 hunks)docs/docs/Components/components-logic.md(5 hunks)docs/docs/Components/components-memories.md(1 hunks)docs/docs/Components/components-models.md(4 hunks)docs/docs/Components/components-processing.md(28 hunks)docs/docs/Components/components-prompts.md(2 hunks)docs/docs/Components/components-tools.md(4 hunks)docs/docs/Components/components-vector-stores.md(24 hunks)docs/docs/Components/mcp-client.md(5 hunks)docs/docs/Concepts/concepts-components.md(2 hunks)docs/docs/Concepts/concepts-file-management.md(1 hunks)docs/docs/Concepts/concepts-objects.md(1 hunks)docs/docs/Concepts/concepts-overview.md(5 hunks)docs/docs/Concepts/concepts-playground.md(3 hunks)docs/docs/Concepts/concepts-publish.md(2 hunks)docs/docs/Concepts/concepts-voice-mode.md(3 hunks)docs/docs/Concepts/embedded-chat-widget.md(3 hunks)docs/docs/Concepts/mcp-server.md(6 hunks)docs/docs/Configuration/configuration-api-keys.md(2 hunks)docs/docs/Configuration/configuration-authentication.md(1 hunks)docs/docs/Configuration/configuration-global-variables.md(1 hunks)docs/docs/Contributing/contributing-community.md(2 hunks)docs/docs/Contributing/contributing-components.md(3 hunks)docs/docs/Contributing/contributing-github-issues.md(2 hunks)docs/docs/Deployment/deployment-docker.md(1 hunks)docs/docs/Deployment/deployment-kubernetes-prod.md(1 hunks)docs/docs/Deployment/deployment-overview.md(2 hunks)docs/docs/Develop/Clients/typescript-client.md(4 hunks)docs/docs/Develop/develop-application.md(9 hunks)docs/docs/Develop/develop-overview.md(1 hunks)docs/docs/Develop/memory.md(2 hunks)docs/docs/Develop/session-id.md(1 hunks)docs/docs/Develop/webhook.md(3 hunks)docs/docs/Get-Started/get-started-installation.md(4 hunks)docs/docs/Get-Started/get-started-quickstart.md(4 hunks)docs/docs/Get-Started/welcome-to-langflow.md(0 hunks)docs/docs/Integrations/Arize/integrations-arize.md(1 hunks)docs/docs/Integrations/Cleanlab/integrations-cleanlab.md(1 hunks)docs/docs/Integrations/Composio/integrations-composio.md(2 hunks)docs/docs/Integrations/Google/integrations-setup-google-cloud-vertex-ai-langflow.md(1 hunks)docs/docs/Integrations/Google/integrations-setup-google-oauth-langflow.md(1 hunks)docs/docs/Integrations/Notion/notion-agent-conversational.md(1 hunks)docs/docs/Integrations/Notion/notion-agent-meeting-notes.md(1 hunks)docs/docs/Integrations/Nvidia/integrations-nvidia-g-assist.md(1 hunks)docs/docs/Integrations/Nvidia/integrations-nvidia-ingest.md(2 hunks)docs/docs/Integrations/Nvidia/integrations-nvidia-nim-wsl2.md(1 hunks)docs/docs/Integrations/mcp-component-astra.md(3 hunks)docs/docs/Support/troubleshooting.md(4 hunks)docs/docs/Templates/basic-prompting.md(1 hunks)docs/docs/Templates/blog-writer.md(1 hunks)docs/docs/Templates/document-qa.md(2 hunks)docs/docs/Templates/financial-report-parser.md(2 hunks)docs/docs/Templates/memory-chatbot.md(2 hunks)docs/docs/Templates/sequential-agent.md(2 hunks)docs/docs/Templates/simple-agent.md(2 hunks)docs/docs/Templates/travel-planning-agent.md(1 hunks)docs/docs/Templates/vector-store-rag.md(1 hunks)docs/docusaurus.config.js(5 hunks)docs/sidebars.js(0 hunks)docs/src/components/CustomIcon/index.tsx(1 hunks)docs/src/components/icon/index.tsx(2 hunks)docs/src/pages/index.module.css(1 hunks)docs/src/pages/index.tsx(1 hunks)docs/src/theme/Footer.js(1 hunks)docs/src/theme/Navbar.js(1 hunks)
💤 Files with no reviewable changes (2)
- docs/sidebars.js
- docs/docs/Get-Started/welcome-to-langflow.md
🧰 Additional context used
📓 Path-based instructions (2)
`docs/docs/**/*.{md,mdx}`: All documentation content must be placed within the '...
docs/docs/**/*.{md,mdx}: All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
All documentation markdown files must start with a frontmatter block containing at least 'title' and 'description' fields.
Use admonitions (:::tip, :::warning, :::danger) in markdown files to highlight important information, warnings, or critical issues.
Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Use code blocks with language identifiers and optional titles for code examples in markdown documentation.
Documentation 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', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
📄 Source: CodeRabbit Inference Engine (.cursor/rules/docs_development.mdc)
List of files the instruction was applied to:
docs/docs/API-Reference/api-monitor.mddocs/docs/Templates/blog-writer.mddocs/docs/Deployment/deployment-docker.mddocs/docs/Templates/travel-planning-agent.mddocs/docs/Templates/financial-report-parser.mddocs/docs/Integrations/Cleanlab/integrations-cleanlab.mddocs/docs/Configuration/configuration-global-variables.mddocs/docs/Integrations/Arize/integrations-arize.mddocs/docs/Develop/session-id.mddocs/docs/Templates/basic-prompting.mddocs/docs/Concepts/concepts-playground.mddocs/docs/Templates/vector-store-rag.mddocs/docs/Components/components-prompts.mddocs/docs/Integrations/Composio/integrations-composio.mddocs/docs/Components/components-memories.mddocs/docs/Develop/develop-overview.mddocs/docs/Deployment/deployment-kubernetes-prod.mddocs/docs/Configuration/configuration-authentication.mddocs/docs/Deployment/deployment-overview.mddocs/docs/Integrations/Google/integrations-setup-google-cloud-vertex-ai-langflow.mddocs/docs/Concepts/concepts-objects.mddocs/docs/Concepts/embedded-chat-widget.mddocs/docs/Templates/document-qa.mddocs/docs/Integrations/Nvidia/integrations-nvidia-g-assist.mddocs/docs/API-Reference/api-files.mddocs/docs/Contributing/contributing-community.mddocs/docs/Agents/agents-tools.mddocs/docs/API-Reference/api-reference-api-examples.mddocs/docs/Components/components-agents.mddocs/docs/Support/troubleshooting.mddocs/docs/Integrations/Notion/notion-agent-conversational.mddocs/docs/API-Reference/api-projects.mddocs/docs/Integrations/mcp-component-astra.mddocs/docs/Components/mcp-client.mddocs/docs/API-Reference/api-flows-run.mddocs/docs/Concepts/concepts-overview.mddocs/docs/Integrations/Notion/notion-agent-meeting-notes.mddocs/docs/Contributing/contributing-components.mddocs/docs/Components/components-logic.mddocs/docs/Contributing/contributing-github-issues.mddocs/docs/Concepts/concepts-file-management.mddocs/docs/Integrations/Google/integrations-setup-google-oauth-langflow.mddocs/docs/Components/components-io.mddocs/docs/Concepts/concepts-components.mddocs/docs/Components/components-data.mddocs/docs/Integrations/Nvidia/integrations-nvidia-nim-wsl2.mddocs/docs/Templates/memory-chatbot.mddocs/docs/Components/components-models.mddocs/docs/Concepts/mcp-server.mddocs/docs/Agents/agents.mddocs/docs/API-Reference/api-flows.mddocs/docs/Integrations/Nvidia/integrations-nvidia-ingest.mddocs/docs/Components/components-custom-components.mddocs/docs/Concepts/concepts-publish.mddocs/docs/Components/components-tools.mddocs/docs/Components/components-embedding-models.mddocs/docs/Components/components-processing.mddocs/docs/Configuration/configuration-api-keys.mddocs/docs/Develop/memory.mddocs/docs/Templates/simple-agent.mddocs/docs/Get-Started/get-started-installation.mddocs/docs/Concepts/concepts-voice-mode.mddocs/docs/Develop/develop-application.mddocs/docs/Templates/sequential-agent.mddocs/docs/API-Reference/api-build.mddocs/docs/Develop/webhook.mddocs/docs/Components/components-helpers.mddocs/docs/Develop/Clients/typescript-client.mddocs/docs/Get-Started/get-started-quickstart.mddocs/docs/Components/components-vector-stores.md
`docs/docusaurus.config.js`: Site configuration, including navbar, title, and theme settings, must be managed in 'docs/docusaurus.config.js'.
docs/docusaurus.config.js: Site configuration, including navbar, title, and theme settings, must be managed in 'docs/docusaurus.config.js'.
📄 Source: CodeRabbit Inference Engine (.cursor/rules/docs_development.mdc)
List of files the instruction was applied to:
docs/docusaurus.config.js
🧠 Learnings (71)
📓 Common learnings
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/sidebars.js : Sidebar navigation must be configured and updated in 'docs/sidebars.js' to reflect the current documentation structure.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Sidebar and navigation should be kept current to ensure users can easily find all documentation sections and cross-references.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docusaurus.config.js : Site configuration, including navbar, title, and theme settings, must be managed in 'docs/docusaurus.config.js'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: The documentation site is built and served locally using 'yarn build' and 'yarn serve', and is automatically deployed on commit to the main branch.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Before deployment, documentation must be reviewed for accuracy, completeness, clarity, and navigation, including checking for broken links and up-to-date screenshots.
docs/docs/Templates/blog-writer.md (6)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
docs/docs/Deployment/deployment-docker.md (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Before deployment, documentation must be reviewed for accuracy, completeness, clarity, and navigation, including checking for broken links and up-to-date screenshots.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
docs/docs/Templates/travel-planning-agent.md (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
docs/docs/Templates/financial-report-parser.md (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
docs/docs/Configuration/configuration-global-variables.md (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
docs/docs/Develop/session-id.md (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
docs/docs/Templates/basic-prompting.md (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
docs/docs/Concepts/concepts-playground.md (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.464Z
Learning: Edit and test components in the UI first for fast iteration, then save to source
docs/docs/Templates/vector-store-rag.md (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
docs/docs/Components/components-prompts.md (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: 2getsandesh
PR: langflow-ai/langflow#8209
File: src/backend/base/langflow/services/tracing/traceloop.py:184-188
Timestamp: 2025-06-03T08:26:39.319Z
Learning: In LangFlow's tracing integrations (TraceLoop and Arize Phoenix), there is an established pattern of special-casing the "prompt" trace type with different span kind mappings compared to other trace types.
docs/docs/Integrations/Composio/integrations-composio.md (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
docs/docs/Components/components-memories.md (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test Langflow's 'Message' objects and chat functionality by asserting correct properties and structure.
docs/docs/Develop/develop-overview.md (11)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Before deployment, documentation must be reviewed for accuracy, completeness, clarity, and navigation, including checking for broken links and up-to-date screenshots.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/package.json : All dependencies and scripts for the documentation site must be managed in 'docs/package.json'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
docs/docs/Deployment/deployment-kubernetes-prod.md (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Before deployment, documentation must be reviewed for accuracy, completeness, clarity, and navigation, including checking for broken links and up-to-date screenshots.
docs/docs/Configuration/configuration-authentication.md (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
docs/docs/Deployment/deployment-overview.md (12)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Before deployment, documentation must be reviewed for accuracy, completeness, clarity, and navigation, including checking for broken links and up-to-date screenshots.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Documentation must build successfully with 'yarn build' before deployment.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/package.json : All dependencies and scripts for the documentation site must be managed in 'docs/package.json'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Documentation is automatically deployed on commit to the main branch; build artifacts are output to the 'build/' directory.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/static/img/**/* : Place images and static assets in the 'docs/static/img/' directory and use descriptive alt text for all images.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
docs/docs/Integrations/Google/integrations-setup-google-cloud-vertex-ai-langflow.md (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
docs/docs/Concepts/concepts-objects.md (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
docs/docs/Concepts/embedded-chat-widget.md (9)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/sidebars.js : Sidebar navigation must be configured and updated in 'docs/sidebars.js' to reflect the current documentation structure.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Headers in documentation should use sentence case, and formatting should include inline code with backticks, bold for UI elements, and italic for emphasis.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-23T12:46:42.048Z
Learning: React Flow should be used for flow graph visualization, with nodes and edges passed as props, and changes handled via onNodesChange and onEdgesChange callbacks.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-23T12:46:42.048Z
Learning: Custom React Flow node types should be implemented as memoized components, using Handle components for connection points and supporting optional icons and labels.
docs/docs/Templates/document-qa.md (11)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/package.json : All dependencies and scripts for the documentation site must be managed in 'docs/package.json'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Before deployment, documentation must be reviewed for accuracy, completeness, clarity, and navigation, including checking for broken links and up-to-date screenshots.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
docs/docs/API-Reference/api-files.md (10)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/package.json : All dependencies and scripts for the documentation site must be managed in 'docs/package.json'.
docs/docs/Contributing/contributing-community.md (8)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use admonitions (:::tip, :::warning, :::danger) in markdown files to highlight important information, warnings, or critical issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
docs/docs/Agents/agents-tools.md (9)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Before deployment, documentation must be reviewed for accuracy, completeness, clarity, and navigation, including checking for broken links and up-to-date screenshots.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.510Z
Learning: Applies to src/frontend/src/components/**/*FlowGraph.tsx : Use React Flow for flow graph visualization components.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Use predefined JSON flows and utility functions for flow testing (e.g., 'create_flow', 'build_flow', 'get_build_events', 'consume_and_assert_stream').
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-23T12:46:42.048Z
Learning: Custom React Flow node types should be implemented as memoized components, using Handle components for connection points and supporting optional icons and labels.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.464Z
Learning: Applies to src/backend/tests/unit/**/*.py : Test component integration within flows using create_flow, build_flow, and get_build_events utilities
docs/docs/API-Reference/api-reference-api-examples.md (9)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test Langflow's REST API endpoints using the async 'client' fixture and assert correct status codes and response structure.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Use predefined JSON flows and utility functions for flow testing (e.g., 'create_flow', 'build_flow', 'get_build_events', 'consume_and_assert_stream').
docs/docs/Components/components-agents.md (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
docs/docs/Support/troubleshooting.md (12)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Before deployment, documentation must be reviewed for accuracy, completeness, clarity, and navigation, including checking for broken links and up-to-date screenshots.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.464Z
Learning: Applies to {uv.lock,pyproject.toml} : Use uv (>=0.4) as the Python package manager for dependency management
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test backward compatibility across Langflow versions by mapping component files to supported versions using 'VersionComponentMapping'.
docs/docs/API-Reference/api-projects.md (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
docs/docs/Integrations/mcp-component-astra.md (8)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-23T12:46:42.048Z
Learning: Custom React Flow node types should be implemented as memoized components, using Handle components for connection points and supporting optional icons and labels.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.510Z
Learning: Applies to src/frontend/src/icons/**/*.{ts,tsx,js,jsx} : Use Lucide React for icons in frontend components.
docs/docs/Components/mcp-client.md (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
docs/docs/API-Reference/api-flows-run.md (10)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Headers in documentation should use sentence case, and formatting should include inline code with backticks, bold for UI elements, and italic for emphasis.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Use predefined JSON flows and utility functions for flow testing (e.g., 'create_flow', 'build_flow', 'get_build_events', 'consume_and_assert_stream').
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test webhook endpoints by posting payloads and asserting correct processing and status codes.
docs/docs/Concepts/concepts-overview.md (16)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/sidebars.js : Sidebar navigation must be configured and updated in 'docs/sidebars.js' to reflect the current documentation structure.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Before deployment, documentation must be reviewed for accuracy, completeness, clarity, and navigation, including checking for broken links and up-to-date screenshots.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/package.json : All dependencies and scripts for the documentation site must be managed in 'docs/package.json'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-23T12:46:42.048Z
Learning: Custom React Flow node types should be implemented as memoized components, using Handle components for connection points and supporting optional icons and labels.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Use predefined JSON flows and utility functions for flow testing (e.g., 'create_flow', 'build_flow', 'get_build_events', 'consume_and_assert_stream').
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.464Z
Learning: Applies to src/backend/tests/unit/**/*.py : Test component integration within flows using create_flow, build_flow, and get_build_events utilities
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.510Z
Learning: Applies to src/frontend/src/components/**/*FlowGraph.tsx : Use React Flow for flow graph visualization components.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
docs/docs/Contributing/contributing-components.md (22)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/package.json : All dependencies and scripts for the documentation site must be managed in 'docs/package.json'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: Applies to src/backend/**/components/**/*.py : In your Python component class, set the `icon` attribute to a string matching the frontend icon mapping exactly (case-sensitive).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: Applies to src/backend/**/*component*.py : In your Python component class, set the `icon` attribute to a string matching the frontend icon mapping exactly (case-sensitive).
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to src/backend/tests/**/*.py : Inherit from the appropriate ComponentTestBase class ('ComponentTestBase', 'ComponentTestBaseWithClient', or 'ComponentTestBaseWithoutClient') and provide the required fixtures: 'component_class', 'default_kwargs', and 'file_names_mapping' when adding a new component test.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,src/frontend/**/*.test.{ts,tsx,js,jsx},src/frontend/**/*.spec.{ts,tsx,js,jsx},tests/**/*.py} : Create comprehensive unit tests for all new components.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.464Z
Learning: Applies to src/backend/tests/unit/components/**/*.py : Create comprehensive unit tests for all new components
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.464Z
Learning: Applies to src/backend/tests/unit/components/**/*.py : Use ComponentTestBaseWithClient or ComponentTestBaseWithoutClient as base classes for component unit tests
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.464Z
Learning: Applies to src/backend/tests/unit/components/**/*.py : Mirror the component directory structure in unit tests under src/backend/tests/unit/components/
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.md,tests/**/*.md} : If unit tests are incomplete, create a Markdown file with manual testing steps in the same directory as the unit tests, using the same filename as the component but with a '.md' extension.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,src/frontend/**/*.test.{ts,tsx,js,jsx},src/frontend/**/*.spec.{ts,tsx,js,jsx},tests/**/*.py} : Test component initialization and configuration.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,src/frontend/**/*.test.{ts,tsx,js,jsx},src/frontend/**/*.spec.{ts,tsx,js,jsx},tests/**/*.py} : Complex test setups should be commented, and mock usage should be documented within the test code.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to src/backend/tests/**/*.py : Test files should use the same filename as the component with an appropriate test prefix or suffix (e.g., 'my_component.py' → 'test_my_component.py').
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.510Z
Learning: All changes must be tested in both light and dark mode before committing.
docs/docs/Components/components-logic.md (11)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Before deployment, documentation must be reviewed for accuracy, completeness, clarity, and navigation, including checking for broken links and up-to-date screenshots.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.510Z
Learning: Applies to src/frontend/src/components/**/*FlowGraph.tsx : Use React Flow for flow graph visualization components.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-23T12:46:42.048Z
Learning: Custom React Flow node types should be implemented as memoized components, using Handle components for connection points and supporting optional icons and labels.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
docs/docs/Contributing/contributing-github-issues.md (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
docs/docs/Concepts/concepts-file-management.md (10)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/static/img/**/* : Screenshots included in documentation must be up-to-date, use a consistent browser/OS, highlight relevant UI elements, and have descriptive file names.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Before deployment, documentation must be reviewed for accuracy, completeness, clarity, and navigation, including checking for broken links and up-to-date screenshots.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/package.json : All dependencies and scripts for the documentation site must be managed in 'docs/package.json'.
docs/docs/Integrations/Google/integrations-setup-google-oauth-langflow.md (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
docs/docs/Components/components-io.md (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test Langflow's 'Message' objects and chat functionality by asserting correct properties and structure.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-23T12:46:42.048Z
Learning: Custom React Flow node types should be implemented as memoized components, using Handle components for connection points and supporting optional icons and labels.
docs/docs/Concepts/concepts-components.md (11)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-23T12:46:42.048Z
Learning: Custom React Flow node types should be implemented as memoized components, using Handle components for connection points and supporting optional icons and labels.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.464Z
Learning: Applies to src/backend/base/langflow/components/**/*.py : Add new backend components to the appropriate subdirectory under src/backend/base/langflow/components/
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to src/backend/tests/**/*.py : Inherit from the appropriate ComponentTestBase class ('ComponentTestBase', 'ComponentTestBaseWithClient', or 'ComponentTestBaseWithoutClient') and provide the required fixtures: 'component_class', 'default_kwargs', and 'file_names_mapping' when adding a new component test.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.464Z
Learning: Applies to src/backend/base/langflow/components/**/__init__.py : Update __init__.py with alphabetical imports when adding new components
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: Applies to src/backend/**/components/**/*.py : In your Python component class, set the `icon` attribute to a string matching the frontend icon mapping exactly (case-sensitive).
docs/docs/Components/components-data.md (11)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/sidebars.js : Sidebar navigation must be configured and updated in 'docs/sidebars.js' to reflect the current documentation structure.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/package.json : All dependencies and scripts for the documentation site must be managed in 'docs/package.json'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Before deployment, documentation must be reviewed for accuracy, completeness, clarity, and navigation, including checking for broken links and up-to-date screenshots.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test webhook endpoints by posting payloads and asserting correct processing and status codes.
docs/docs/Templates/memory-chatbot.md (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test Langflow's 'Message' objects and chat functionality by asserting correct properties and structure.
docs/docs/Components/components-models.md (6)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
docs/docs/Concepts/mcp-server.md (10)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Before deployment, documentation must be reviewed for accuracy, completeness, clarity, and navigation, including checking for broken links and up-to-date screenshots.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test Langflow's REST API endpoints using the async 'client' fixture and assert correct status codes and response structure.
docs/docs/Agents/agents.md (6)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
docs/docs/API-Reference/api-flows.md (7)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Use predefined JSON flows and utility functions for flow testing (e.g., 'create_flow', 'build_flow', 'get_build_events', 'consume_and_assert_stream').
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test Langflow's REST API endpoints using the async 'client' fixture and assert correct status codes and response structure.
docs/docs/Integrations/Nvidia/integrations-nvidia-ingest.md (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
docs/docs/Components/components-custom-components.md (18)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/sidebars.js : Sidebar navigation must be configured and updated in 'docs/sidebars.js' to reflect the current documentation structure.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Before deployment, documentation must be reviewed for accuracy, completeness, clarity, and navigation, including checking for broken links and up-to-date screenshots.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/package.json : All dependencies and scripts for the documentation site must be managed in 'docs/package.json'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.464Z
Learning: Applies to src/backend/base/langflow/components/**/*.py : Add new backend components to the appropriate subdirectory under src/backend/base/langflow/components/
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.464Z
Learning: Applies to src/backend/base/langflow/components/**/__init__.py : Update __init__.py with alphabetical imports when adding new components
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.510Z
Learning: Frontend source code must reside in the 'src/frontend/src/' directory, organized into components, pages, icons, stores, types, utils, hooks, services, and assets subdirectories.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.464Z
Learning: Applies to src/backend/base/langflow/services/database/models/**/*.py : Place database models in src/backend/base/langflow/services/database/models/ and its subdirectories
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
docs/docusaurus.config.js (13)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docusaurus.config.js : Site configuration, including navbar, title, and theme settings, must be managed in 'docs/docusaurus.config.js'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/sidebars.js : Sidebar navigation must be configured and updated in 'docs/sidebars.js' to reflect the current documentation structure.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/package.json : All dependencies and scripts for the documentation site must be managed in 'docs/package.json'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use admonitions (:::tip, :::warning, :::danger) in markdown files to highlight important information, warnings, or critical issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: The documentation site is built and served locally using 'yarn build' and 'yarn serve', and is automatically deployed on commit to the main branch.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation markdown files must start with a frontmatter block containing at least 'title' and 'description' fields.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
docs/docs/Concepts/concepts-publish.md (8)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test Langflow's REST API endpoints using the async 'client' fixture and assert correct status codes and response structure.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Use predefined JSON flows and utility functions for flow testing (e.g., 'create_flow', 'build_flow', 'get_build_events', 'consume_and_assert_stream').
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
docs/docs/Components/components-tools.md (10)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-23T12:46:42.048Z
Learning: Custom React Flow node types should be implemented as memoized components, using Handle components for connection points and supporting optional icons and labels.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
docs/docs/Components/components-embedding-models.md (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
docs/src/components/CustomIcon/index.tsx (11)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: Applies to src/frontend/src/icons/*/* : Create a new directory for your icon in `src/frontend/src/icons/YourIconName/` and add your SVG as a React component (e.g., `YourIconName.jsx`) that uses the `isdark` prop to support both light and dark mode.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: Applies to src/frontend/src/icons/*/index.tsx : Create an `index.tsx` in your icon directory that exports your icon using `forwardRef` and passes the `isdark` prop.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: Export custom icon components in React using React.forwardRef to ensure proper ref forwarding and compatibility with parent components.
Learnt from: dolfim-ibm
PR: langflow-ai/langflow#8394
File: src/frontend/src/icons/Docling/index.tsx:4-6
Timestamp: 2025-06-16T11:14:04.200Z
Learning: The Langflow codebase consistently uses `React.PropsWithChildren<{}>` as the prop type for all icon components using forwardRef, rather than `React.SVGProps<SVGSVGElement>`. This is an established pattern across hundreds of icon files in src/frontend/src/icons/.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: Applies to src/frontend/src/icons/*/*.jsx : Always support both light and dark mode for custom icons by using the `isdark` prop in your SVG component.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.510Z
Learning: Applies to src/frontend/src/icons/**/*.{ts,tsx,js,jsx} : Use Lucide React for icons in frontend components.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: Custom SVG icon components in React should always support both light and dark mode by accepting an 'isdark' prop and adjusting colors accordingly.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: Applies to src/frontend/src/icons/lazyIconImports.ts : Add your icon to the `lazyIconsMapping` object in `src/frontend/src/icons/lazyIconImports.ts` with a key that matches the backend icon string exactly.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: If a custom icon does not exist for a component, use a generic lucide icon as a fallback and request a new custom icon if needed.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: If no suitable custom icon exists, use a lucide icon from https://lucide.dev/icons.
docs/docs/Components/components-processing.md (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
docs/docs/Configuration/configuration-api-keys.md (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
docs/src/components/icon/index.tsx (11)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.510Z
Learning: Applies to src/frontend/src/icons/**/*.{ts,tsx,js,jsx} : Use Lucide React for icons in frontend components.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: Applies to src/frontend/src/icons/*/index.tsx : Create an `index.tsx` in your icon directory that exports your icon using `forwardRef` and passes the `isdark` prop.
Learnt from: dolfim-ibm
PR: langflow-ai/langflow#8394
File: src/frontend/src/icons/Docling/index.tsx:4-6
Timestamp: 2025-06-16T11:14:04.200Z
Learning: The Langflow codebase consistently uses `React.PropsWithChildren<{}>` as the prop type for all icon components using forwardRef, rather than `React.SVGProps<SVGSVGElement>`. This is an established pattern across hundreds of icon files in src/frontend/src/icons/.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: Applies to src/frontend/src/icons/*/*.jsx : Always support both light and dark mode for custom icons by using the `isdark` prop in your SVG component.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: Export custom icon components in React using React.forwardRef to ensure proper ref forwarding and compatibility with parent components.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: Applies to src/frontend/src/icons/lazyIconImports.ts : Add your icon to the `lazyIconsMapping` object in `src/frontend/src/icons/lazyIconImports.ts` with a key that matches the backend icon string exactly.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: If a custom icon does not exist for a component, use a generic lucide icon as a fallback and request a new custom icon if needed.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: Applies to src/frontend/src/icons/*/* : Create a new directory for your icon in `src/frontend/src/icons/YourIconName/` and add your SVG as a React component (e.g., `YourIconName.jsx`) that uses the `isdark` prop to support both light and dark mode.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: If no suitable custom icon exists, use a lucide icon from https://lucide.dev/icons.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: Custom SVG icon components in React should always support both light and dark mode by accepting an 'isdark' prop and adjusting colors accordingly.
docs/docs/Develop/memory.md (6)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test Langflow's 'Message' objects and chat functionality by asserting correct properties and structure.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.464Z
Learning: Use SQLite for development and PostgreSQL for production as the database backend
docs/docs/Templates/simple-agent.md (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
docs/docs/Get-Started/get-started-installation.md (11)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/package.json : All dependencies and scripts for the documentation site must be managed in 'docs/package.json'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Before deployment, documentation must be reviewed for accuracy, completeness, clarity, and navigation, including checking for broken links and up-to-date screenshots.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
docs/docs/Concepts/concepts-voice-mode.md (6)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
docs/docs/Develop/develop-application.md (16)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Before deployment, documentation must be reviewed for accuracy, completeness, clarity, and navigation, including checking for broken links and up-to-date screenshots.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/package.json : All dependencies and scripts for the documentation site must be managed in 'docs/package.json'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Documentation must build successfully with 'yarn build' before deployment.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.464Z
Learning: Starter project files are auto-formatted after langflow run; these changes can be committed or ignored
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.464Z
Learning: Applies to src/backend/base/langflow/components/**/*.py : Add new backend components to the appropriate subdirectory under src/backend/base/langflow/components/
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Use predefined JSON flows and utility functions for flow testing (e.g., 'create_flow', 'build_flow', 'get_build_events', 'consume_and_assert_stream').
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: The documentation site is built and served locally using 'yarn build' and 'yarn serve', and is automatically deployed on commit to the main branch.
docs/docs/Templates/sequential-agent.md (6)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
docs/docs/API-Reference/api-build.md (13)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Documentation must build successfully with 'yarn build' before deployment.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Documentation is automatically deployed on commit to the main branch; build artifacts are output to the 'build/' directory.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: The documentation site is built and served locally using 'yarn build' and 'yarn serve', and is automatically deployed on commit to the main branch.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Use predefined JSON flows and utility functions for flow testing (e.g., 'create_flow', 'build_flow', 'get_build_events', 'consume_and_assert_stream').
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.464Z
Learning: Applies to src/backend/tests/unit/**/*.py : Test component integration within flows using create_flow, build_flow, and get_build_events utilities
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test Langflow's REST API endpoints using the async 'client' fixture and assert correct status codes and response structure.
docs/docs/Develop/webhook.md (9)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Headers in documentation should use sentence case, and formatting should include inline code with backticks, bold for UI elements, and italic for emphasis.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Use predefined JSON flows and utility functions for flow testing (e.g., 'create_flow', 'build_flow', 'get_build_events', 'consume_and_assert_stream').
docs/docs/Components/components-helpers.md (8)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Sidebar and navigation should be kept current to ensure users can easily find all documentation sections and cross-references.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/sidebars.js : Sidebar navigation must be configured and updated in 'docs/sidebars.js' to reflect the current documentation structure.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test Langflow's 'Message' objects and chat functionality by asserting correct properties and structure.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
docs/docs/Develop/Clients/typescript-client.md (5)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
docs/docs/Get-Started/get-started-quickstart.md (11)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Before deployment, documentation must be reviewed for accuracy, completeness, clarity, and navigation, including checking for broken links and up-to-date screenshots.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test Langflow's REST API endpoints using the async 'client' fixture and assert correct status codes and response structure.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
docs/docs/Components/components-vector-stores.md (5)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
docs/src/pages/index.module.css (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.510Z
Learning: Applies to src/frontend/**/*.{ts,tsx,js,jsx,css,scss} : Use Tailwind CSS for styling all frontend components.
docs/src/theme/Navbar.js (8)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docusaurus.config.js : Site configuration, including navbar, title, and theme settings, must be managed in 'docs/docusaurus.config.js'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/sidebars.js : Sidebar navigation must be configured and updated in 'docs/sidebars.js' to reflect the current documentation structure.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.510Z
Learning: Applies to src/frontend/src/{components,hooks}/**/*.{ts,tsx} : Implement dark mode support in components and hooks where needed.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: Applies to src/frontend/src/icons/*/* : Create a new directory for your icon in `src/frontend/src/icons/YourIconName/` and add your SVG as a React component (e.g., `YourIconName.jsx`) that uses the `isdark` prop to support both light and dark mode.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: Applies to src/frontend/src/icons/*/*.jsx : Always support both light and dark mode for custom icons by using the `isdark` prop in your SVG component.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: Custom SVG icon components in React should always support both light and dark mode by accepting an 'isdark' prop and adjusting colors accordingly.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-23T12:46:42.048Z
Learning: Dark mode support should be implemented using a dedicated Zustand store (e.g., useDarkStore), and toggled via a custom hook (e.g., useDarkMode) that exposes isDark and toggle.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: Export custom icon components in React using React.forwardRef to ensure proper ref forwarding and compatibility with parent components.
docs/src/pages/index.tsx (11)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.510Z
Learning: Applies to src/frontend/src/components/**/*FlowGraph.tsx : Use React Flow for flow graph visualization components.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: dolfim-ibm
PR: langflow-ai/langflow#8394
File: src/frontend/src/icons/Docling/index.tsx:4-6
Timestamp: 2025-06-16T11:14:04.200Z
Learning: The Langflow codebase consistently uses `React.PropsWithChildren<{}>` as the prop type for all icon components using forwardRef, rather than `React.SVGProps<SVGSVGElement>`. This is an established pattern across hundreds of icon files in src/frontend/src/icons/.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.510Z
Learning: Applies to src/frontend/**/*.{ts,tsx} : Use React 18 with TypeScript for all UI components and frontend logic.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.510Z
Learning: Applies to src/frontend/src/icons/**/*.{ts,tsx,js,jsx} : Use Lucide React for icons in frontend components.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docusaurus.config.js : Site configuration, including navbar, title, and theme settings, must be managed in 'docs/docusaurus.config.js'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-23T12:46:42.048Z
Learning: Custom React Flow node types should be implemented as memoized components, using Handle components for connection points and supporting optional icons and labels.
docs/css/custom.css (7)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docusaurus.config.js : Site configuration, including navbar, title, and theme settings, must be managed in 'docs/docusaurus.config.js'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/sidebars.js : Sidebar navigation must be configured and updated in 'docs/sidebars.js' to reflect the current documentation structure.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.510Z
Learning: Applies to src/frontend/src/{components,hooks}/**/*.{ts,tsx} : Implement dark mode support in components and hooks where needed.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.510Z
Learning: All changes must be tested in both light and dark mode before committing.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: Applies to src/frontend/src/icons/*/*.jsx : Always support both light and dark mode for custom icons by using the `isdark` prop in your SVG component.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-23T12:46:42.048Z
Learning: All changes must be tested in both light and dark mode to ensure consistent appearance and functionality.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: Custom SVG icon components in React should always support both light and dark mode by accepting an 'isdark' prop and adjusting colors accordingly.
🪛 LanguageTool
docs/docs/Templates/financial-report-parser.md
[misspelling] ~10-~10: This word is normally spelled as one.
Context: ...xample, the Chat Input component is pre-loaded with a sample financial report to demon...
(EN_COMPOUNDS_PRE_LOADED)
docs/docs/Components/components-memories.md
[formatting] ~10-~10: If the ‘because’ clause is essential to the meaning, do not use a comma before the clause.
Context: ...re distinct from vector store components, because they are built specifically for storing...
(COMMA_BEFORE_BECAUSE)
docs/docs/Deployment/deployment-overview.md
[style] ~20-~20: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ment for creating and testing flows. * [Langflow runtime](/docs/deployment-kubernetes-pr...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
docs/docs/API-Reference/api-files.md
[style] ~275-~275: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...low, send it to the File component. To retrieve the File component's full ...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
docs/docs/Contributing/contributing-community.md
[grammar] ~35-~35: The word ‘help’ is a conjunction. In formal texts, use “to”.
Context: ...ry. For more information, see [Get help and request enhancements](/docs/contributin...
(HELP_AND_VB)
docs/docs/API-Reference/api-reference-api-examples.md
[style] ~162-~162: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...I to upload files. - Use the Langflow API to [get flow logs](/do...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
docs/docs/Components/components-agents.md
[uncategorized] ~24-~24: Possible missing comma found.
Context: ...ow-simple-agent.png) For a multi-agent example see [Create a flow with an agent](/docs...
(AI_HYDRA_LEO_MISSING_COMMA)
docs/docs/Support/troubleshooting.md
[uncategorized] ~143-~143: The grammatical number of this noun doesn’t look right. Consider replacing it.
Context: ...g-mcp-server) ## Custom components and integrations issues For troubleshooting advice for ...
(AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER)
docs/docs/API-Reference/api-projects.md
[uncategorized] ~77-~77: A punctuation mark might be missing here.
Context: ..._listandflows_list values from the [/all`](/docs/api-reference-api-examples#...
(AI_EN_LECTOR_MISSING_PUNCTUATION)
docs/docs/Components/mcp-client.md
[style] ~75-~75: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...e from the targeted Langflow server. 2. In the [component's header menu](/docs/con...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
docs/docs/Contributing/contributing-components.md
[uncategorized] ~49-~49: Loose punctuation mark.
Context: ...to-the-frontend-folder). * priority: An optional integer to control display ...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~50-~50: Loose punctuation mark.
Context: ... Lower numbers appear first. * name: An optional internal identifier that de...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~50-~50: You might be missing the article “the” here.
Context: ...al internal identifier that defaults to class name. 4. Define the component's interf...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
docs/docs/Components/components-models.md
[uncategorized] ~277-~277: Possible missing comma found.
Context: ...urity-tokens) to authenticate. In this example based on the [Basic prompting flow](/do...
(AI_HYDRA_LEO_MISSING_COMMA)
docs/docs/Integrations/Nvidia/integrations-nvidia-ingest.md
[uncategorized] ~88-~88: Possible missing comma found.
Context: ...ta](/docs/concepts-objects#data-object) objects where each object contains: - text: T...
(AI_HYDRA_LEO_MISSING_COMMA)
docs/docs/Templates/sequential-agent.md
[grammar] ~54-~54: This noun or verb “problem-solving” is spelled with a hyphen.
Context: ...our own multi-agent flow, see Create a problem solving agent.
(PROBLEM_SOLVE_HYPHEN)
🪛 markdownlint-cli2 (0.17.2)
docs/docs/Integrations/Nvidia/integrations-nvidia-g-assist.md
36-36: Unordered list style
Expected: asterisk; Actual: dash
(MD004, ul-style)
37-37: Unordered list style
Expected: asterisk; Actual: dash
(MD004, ul-style)
docs/docs/Support/troubleshooting.md
23-23: Images should have alternate text (alt text)
(MD045, no-alt-text)
docs/docs/Contributing/contributing-components.md
54-54: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
docs/docs/Components/components-data.md
111-111: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
docs/docs/Concepts/mcp-server.md
355-355: Unordered list style
Expected: asterisk; Actual: dash
(MD004, ul-style)
356-356: Unordered list style
Expected: asterisk; Actual: dash
(MD004, ul-style)
docs/docs/Get-Started/get-started-quickstart.md
520-520: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
521-521: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
🔇 Additional comments (55)
docs/docs/Concepts/concepts-objects.md (1)
208-210: Internal link update looks correctThe new
/docs/session-idpath matches the site-wide convention introduced in this PR, so no further action needed.docs/docs/Integrations/Notion/notion-agent-conversational.md (1)
10-14: Updated link path matches new routing
/docs/integrations/notion/setupfollows the updated docs base path and resolves correctly.docs/docs/Templates/basic-prompting.md (1)
15-19: Link prefix adjustment approvedThe prerequisite link now points to
/docs/get-started-installation, aligning with the new structure.docs/docs/Deployment/deployment-docker.md (1)
144-147: Kubernetes deployment link fixedThe Helm-deployment reference correctly gains the
/docsprefix—no issues spotted.docs/docs/API-Reference/api-monitor.md (1)
675-677: Double-check the new target/docs/session-id.If the “Session ID” page lives under a different folder (e.g. API-Reference), this link will 404 after the migration. Please run the link checker or verify manually before merging.
Otherwise LGTM.docs/docs/Templates/travel-planning-agent.md (1)
18-19: Validate the updated install link.Good catch adding the
/docs/prefix, but ensure the referenced slug really is/docs/get-started-installation(note the folder uses “Get-Started” with capital G/S in many files).
Run the link checker before shipping.docs/docs/Integrations/Arize/integrations-arize.md (1)
70-71: Confirm simple-agent link path.
/docs/simple-agentis correct only if the slug is exactly that. Older files used/simple-agent. Please verify.docs/docs/Integrations/Notion/notion-agent-meeting-notes.md (1)
11-12: Verify new Notion setup link.Ensure
/docs/integrations/notion/setupexists; otherwise keep the original relative path.docs/docs/Templates/vector-store-rag.md (1)
22-23: Confirm installation link accuracy.The
get-started-installationpage recently moved; please run the link checker to avoid broken links.docs/docs/Configuration/configuration-global-variables.md (1)
212-212: No changes required: link slug is correct
The frontmatter slug in docs/docs/Configuration/environment-variables.md is/environment-variables, so linking to/docs/environment-variableswill resolve properly.docs/docs/Integrations/Composio/integrations-composio.md (1)
22-23: Link path switched to/docs/*— confirm slug existsThe new links to
[global variable](/docs/configuration-global-variables)assume that page’s slug now includes the/docsprefix.
Double-check thatconfiguration-global-variables.mdexposes that exact slug (or add an alias) to avoid 404s.Also applies to: 38-39
docs/docs/Integrations/Cleanlab/integrations-cleanlab.md (1)
138-139: Potential broken link to Vector Store RAG templateEnsure the template file’s slug is actually
/docs/vector-store-rag.
If the original slug was/vector-store-rag, the added prefix could break navigation.docs/docs/Templates/blog-writer.md (1)
14-15: Confirm/docs/get-started-installationslugThe install guide may still live at
/get-started-installation.
Please verify the target slug after the docs restructure.docs/docs/Contributing/contributing-github-issues.md (1)
6-7: Slug validation for community page linksBoth occurrences now point to
/docs/contributing-community.
Run a quick grep to ensure that slug exists or add it as an alias.Also applies to: 24-25
docs/docs/Concepts/concepts-playground.md (1)
94-95: Good fix – link works.
No further action required.docs/docs/Integrations/Nvidia/integrations-nvidia-nim-wsl2.md (1)
25-27: URL prefix fix looks good.
No additional issues spotted in this hunk.docs/docs/Concepts/embedded-chat-widget.md (1)
19-21: Good path update.
The example now resolves properly.docs/docs/Components/components-memories.md (1)
8-8: Minor wording: clarityConsider adding chat for consistency with the paragraph below.
-Memory components store and retrieve chat messages by [`session_id`](/docs/session-id). +Memory components store and retrieve chat messages by [`session_id`](/docs/session-id).docs/docs/Templates/sequential-agent.md (1)
14-14: No action – link prefix LGTM
The updated/docs/get-started-installationpath aligns with the new routing scheme.docs/docs/Templates/document-qa.md (2)
10-10: Internal link prefix looks good.
/docs/get-started-installationmatches the new routing scheme and resolves correctly.
29-29: Consistent path prefix acknowledged.The link to the File Management concept now follows the
/docs/convention—no issues.docs/docs/Contributing/contributing-community.md (1)
21-21: Link prefix update verified.
/docs/contributing-how-to-contributeis correct under the new scheme.docs/docs/Configuration/configuration-authentication.md (1)
109-109: Link prefix change confirmed.
/docs/configuration-authentication#authentication-configuration-valuesmatches the doc slug—no action needed.docs/docs/Components/components-agents.md (2)
20-20: Link update looks good.
The new/docs/simple-agentprefix aligns with the global permalink change.
32-32: Confirm/docs/agentsexists
Double-check that the new slug actually resolves; the previous file name looked plural but the page may live under/components-agentsor/components-agents#agent-component.docs/docs/Configuration/configuration-api-keys.md (1)
77-77: Links updated correctly
Both links now point to the canonical/docs/paths.Also applies to: 116-116
docs/docs/Components/components-io.md (1)
22-23: 👍 Link prefix update looks correctThe
/docs/concepts-objects#message-objectpath matches the new base-path routing. No further action.docs/docs/Templates/simple-agent.md (1)
6-6: Internal link fixed – good catch
[Agent](/docs/agents)now resolves correctly after the route change.docs/docs/Agents/agents-tools.md (1)
15-16: Correct component link – looks good
/docs/components-data#urlresolves under the new routing. ✅docs/docs/Develop/develop-overview.md (1)
8-19: All link prefixes updated – niceEach bullet now correctly uses
/docs/…ensuring client-side routing works after the base-path change.docs/docs/Components/mcp-client.md (1)
48-50: Verify slug for components-agentsLink points to
/docs/components-agents; the rest of the docs use “components-io”, “components-data”, etc. Please ensure a page with that slug exists; otherwise this introduces a broken link.docs/docs/API-Reference/api-files.md (2)
243-248: Capitalize “Component” for consistency with the docs style guide
Componentis a Langflow concept and should always be capitalized.
[ suggest_essential_refactor ]-Send a file to your flow for analysis using the [File](/docs/components-data#file) component and the API. -Your flow must contain a [File](/docs/components-data#file) component to receive the file. +Send a file to your Flow for analysis using the [File](/docs/components-data#file) Component and the API. +Your Flow must contain a [File](/docs/components-data#file) Component to receive the file.
66-68: LGTM – link path now matches the new/docsconventionNo issues spotted.
docs/docs/Develop/develop-application.md (1)
9-10: Link update looks goodThe new
/docs/deployment-dockerlink matches the repo-wide change.docs/docs/API-Reference/api-flows.md (1)
264-299: Confirm target anchors existPlease ensure:
/docs/concepts-flows#langflow-json-file-contents/docs/api-projects#read-projectsactually resolve; otherwise update the anchors.
docs/docs/Components/components-helpers.md (2)
131-168: Memory page link may be obsoleteThe page was recently moved to
/docs/Concepts/memory– verify and update if necessary.
304-304: Session-ID link looks top-levelDouble-check that
/docs/session-idexists; many config docs moved under/docs/Administration/. Update path if needed.docs/docs/Components/components-custom-components.md (1)
108-110: Internal link update looks good
/docs/components-custom-components#custom-component-inputs-and-outputsresolves correctly after the router update.docs/docs/Components/components-data.md (2)
107-113: Good link fix; alt-text unchanged
The updated/docs/concepts-objectslink is correct. No further issues found in this hunk.
255-258: DataFrame link fine – no action needed
The new/docs/concepts-objects#dataframe-objecttarget exists.docs/docs/Components/components-models.md (2)
16-21: Internal links fixed
Both/docs/concepts-objectsand/docs/basic-promptingresolve.
547-550: Agent link update correct
/docs/components-agentsexists. No further action required.docs/docs/API-Reference/api-build.md (2)
12-15: Good: “Flow trigger endpoints” link now accurate
Confirming/docs/api-flows-runresolves.
161-165: ‘See also’ links verified
All three/docs/…targets exist. Looks good.docs/docs/Concepts/mcp-server.md (1)
14-14: LGTM: Link standardization is correct and consistent.The systematic addition of
/docs/prefix to internal documentation links aligns perfectly with the documentation restructuring effort described in the PR objectives.Also applies to: 26-26, 94-94, 108-108, 158-158, 163-163, 355-356
docs/docusaurus.config.js (2)
18-18: LGTM: Appropriate configuration change during restructuring.Changing broken link handling from error to warning is a sensible approach during large-scale documentation restructuring to prevent build failures while links are being updated.
137-278: LGTM: Redirect updates support backward compatibility.The systematic update of all redirect targets to include the
/docs/prefix ensures backward compatibility while supporting the new documentation structure. This maintains user experience for existing bookmarks and external links.docs/docs/Get-Started/get-started-quickstart.md (1)
14-14: LGTM: Link standardization is correct and comprehensive.All internal documentation links have been properly updated with the
/docs/prefix, maintaining consistency with the documentation restructuring effort.Also applies to: 23-23, 25-25, 30-30, 61-61
docs/docs/Components/components-tools.md (1)
22-22: LGTM: Link standardization is correct and maintains component documentation integrity.All internal documentation links have been systematically updated with the
/docs/prefix, ensuring proper navigation within the restructured documentation. The changes maintain the context and accuracy of component documentation references.Also applies to: 28-28, 126-126, 158-158, 314-314, 319-319
docs/docs/Components/components-logic.md (1)
12-12: LGTM! Internal link corrections are consistent and necessary.The addition of
/docsprefix to all internal documentation links aligns with the broader documentation restructuring effort and ensures proper navigation throughout the site.Also applies to: 14-14, 150-150, 235-235, 240-240, 326-326, 350-350
docs/docs/Components/components-processing.md (1)
12-12: LGTM! Comprehensive link corrections maintain documentation consistency.All internal documentation links have been correctly updated with the
/docsprefix, ensuring consistent navigation across the documentation site.Also applies to: 22-22, 107-107, 109-109, 111-111, 157-157, 176-176, 196-196, 198-198, 293-293, 316-316, 334-334, 366-366, 393-393, 395-395, 478-478, 494-494, 503-503, 504-504, 516-516, 566-566, 576-576, 577-577, 616-616, 626-626, 645-645, 662-662, 675-675, 719-719, 735-735, 747-747, 866-866, 873-873, 883-883, 899-899
docs/src/components/icon/index.tsx (1)
2-2: LGTM! Refactor simplifies icon rendering through centralized CustomIcon.The delegation to
CustomIconcentralizes icon management effectively. The flexible props typing allows for forward compatibility.Note: This depends on the
CustomIconcomponent implementing properforwardRefand theme support as suggested in the previous review.Also applies to: 14-14, 18-19
docs/src/theme/Navbar.js (1)
14-23: LGTM! Mobile detection logic is clean and handles responsive behavior well.The viewport detection and event cleanup is properly implemented with useEffect.
docs/docs/Components/components-vector-stores.md (1)
417-418: Markdown table cell renders incorrectlyThe cell mixes type markup with a link:
List[Data](/docs/concepts-objects#data-object).Markdown will treat
List[Data]as the link text; the word “List” is lost and the bracket syntax is confusing in the rendered table. Use back-ticks or split the text:| search_results | `List[Data]` | The results … |or
| search_results | List of [Data](/docs/concepts-objects#data-object) objects | … |docs/src/pages/index.tsx (1)
54-84: Verify quick-link targets
/docs/get-started-quickstart,/docs/agents, and/docs/mcp-servermust match actual slugs in the sidebar. A mismatch will drop users on a 404 from the very first click.
Comment on lines
52
to
53
| To store or retrieve chat messages from external memory, connect the **External memory** port of the **Message store** or **Message history** component to a **Memory** component, like the [Astra DB chat memory](components-memories#astradbchatmemory-component) component. An example flow looks like this: | ||
|
|
Contributor
There was a problem hiding this comment.
Internal link missed the new /docs/ prefix
The link to the Astra DB chat memory component still omits the /docs prefix, breaking consistency.
-...component, like the [Astra DB chat memory](components-memories#astradbchatmemory-component) component.
+...component, like the [Astra DB chat memory](/docs/components-memories#astradbchatmemory-component) component.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| To store or retrieve chat messages from external memory, connect the **External memory** port of the **Message store** or **Message history** component to a **Memory** component, like the [Astra DB chat memory](components-memories#astradbchatmemory-component) component. An example flow looks like this: | |
| To store or retrieve chat messages from external memory, connect the **External memory** port of the **Message store** or **Message history** component to a **Memory** component, like the [Astra DB chat memory](/docs/components-memories#astradbchatmemory-component) component. An example flow looks like this: |
🤖 Prompt for AI Agents
In docs/docs/Develop/memory.md around lines 52 to 53, the internal link to the
Astra DB chat memory component is missing the required /docs/ prefix. Update the
link URL to include the /docs/ prefix before
components-memories#astradbchatmemory-component to maintain consistency and
ensure the link works correctly.
Comment on lines
22
to
23
| The quickstart demonstrates how to get automatically generated code snippets for your flows, use a script to run a flow, and extract data from the Langfow API response. | ||
| ::: |
Contributor
There was a problem hiding this comment.
Typo: “Langfow” → “Langflow”
-The quickstart demonstrates ... extract data from the Langfow API response.
+The quickstart demonstrates ... extract data from the Langflow API response.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| The quickstart demonstrates how to get automatically generated code snippets for your flows, use a script to run a flow, and extract data from the Langfow API response. | |
| ::: | |
| The quickstart demonstrates how to get automatically generated code snippets for your flows, use a script to run a flow, and extract data from the Langflow API response. | |
| ::: |
🤖 Prompt for AI Agents
In docs/docs/API-Reference/api-reference-api-examples.md around lines 22 to 23,
correct the typo by changing "Langfow" to "Langflow" to ensure the product name
is spelled correctly.
Comment on lines
91
to
93
| - You can find flow IDs on the [Publish pane](/docs/concepts-publish), in a flow's URL, and with [`GET /flows`](/docs/api-flows#read-flows). | ||
| - You can retrieve project IDs with `GET /projects`(/api-projects#read-projects). | ||
| ::: |
Contributor
There was a problem hiding this comment.
Malformed markdown link and missing /docs prefix
The second sentence mixes back-ticks and parentheses, so it renders as plain text, not a link:
-You can retrieve project IDs with `GET /projects`(/api-projects#read-projects).
+You can retrieve project IDs with [`GET /projects`](/docs/api-projects#read-projects).📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| - You can find flow IDs on the [Publish pane](/docs/concepts-publish), in a flow's URL, and with [`GET /flows`](/docs/api-flows#read-flows). | |
| - You can retrieve project IDs with `GET /projects`(/api-projects#read-projects). | |
| ::: | |
| - You can find flow IDs on the [Publish pane](/docs/concepts-publish), in a flow's URL, and with [`GET /flows`](/docs/api-flows#read-flows). | |
| - You can retrieve project IDs with [`GET /projects`](/docs/api-projects#read-projects). | |
| ::: |
🤖 Prompt for AI Agents
In docs/docs/API-Reference/api-reference-api-examples.md around lines 91 to 93,
the markdown link for the GET /projects endpoint is malformed because it mixes
back-ticks and parentheses incorrectly and is missing the /docs prefix in the
URL. Fix this by properly formatting the link using square brackets for the link
text with back-ticks inside, followed immediately by the URL in parentheses, and
add the missing /docs prefix to the URL path.
| import TOCInline from '@theme/TOCInline'; | ||
|
|
||
| Langflow integrates with [Google OAuth](https://developers.google.com/identity/protocols/oauth2) for authenticating the [Gmail loader](/components-data#gmail-loader), [Google Drive loader](components-data#google-drive-loader), and [Google Drive Search](/components-data#google-drive-search) components. | ||
| Langflow integrates with [Google OAuth](https://developers.google.com/identity/protocols/oauth2) for authenticating the [Gmail loader](/docs/components-data#gmail-loader), [Google Drive loader](components-data#google-drive-loader), and [Google Drive Search](/docs/components-data#google-drive-search) components. |
Contributor
There was a problem hiding this comment.
Inconsistent link prefix – leads outside docs router
[Google Drive loader](components-data#google-drive-loader) is still a relative path and will break once the site is served under /docs. Prefix it like the other two links.
-[Google Drive loader](components-data#google-drive-loader)
+[Google Drive loader](/docs/components-data#google-drive-loader)📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| Langflow integrates with [Google OAuth](https://developers.google.com/identity/protocols/oauth2) for authenticating the [Gmail loader](/docs/components-data#gmail-loader), [Google Drive loader](components-data#google-drive-loader), and [Google Drive Search](/docs/components-data#google-drive-search) components. | |
| Langflow integrates with [Google OAuth](https://developers.google.com/identity/protocols/oauth2) for authenticating the [Gmail loader](/docs/components-data#gmail-loader), [Google Drive loader](/docs/components-data#google-drive-loader), and [Google Drive Search](/docs/components-data#google-drive-search) components. |
🤖 Prompt for AI Agents
In docs/docs/Integrations/Google/integrations-setup-google-oauth-langflow.md at
line 8, the link for "Google Drive loader" uses a relative path without the
"/docs" prefix, causing it to break when served under the /docs base path.
Update the link to include the "/docs" prefix like the other two links, changing
it to "/docs/components-data#google-drive-loader" to ensure consistent routing
within the documentation site.
Comment on lines
101
to
103
| This confirms your client is connecting to Langflow. | ||
| * The `sessionID` value is a unique identifier for the client-server session. For more information, see [Session ID](/session-id). | ||
| * The `sessionID` value is a unique identifier for the client-server session. For more information, see [Session ID](/docs/session-id). | ||
| * The `outputs` array contains the results of your flow execution. |
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion
Inconsistent session-ID naming across docs and code
This bullet uses the back-ticked identifier sessionID, but:
- The API parameter is
session_id. - The advanced example in the same file uses
session_id. - JavaScript conventions would favour
sessionId.
Pick one spelling and use it everywhere; otherwise users copy/paste the wrong field name and the call fails.
🤖 Prompt for AI Agents
In docs/docs/Develop/Clients/typescript-client.md around lines 101 to 103, the
term `sessionID` is inconsistently used compared to the API parameter
`session_id` and the advanced example in the same file. Choose one consistent
naming convention for the session identifier—preferably `session_id` to match
the API—and update all occurrences in the document to use this exact spelling to
avoid confusion and errors when users copy and paste code.
Comment on lines
+66
to
+69
| export default function CustomIcon({ name, size = 24, className }: IconProps) { | ||
| const icon = customIcons[name as keyof typeof customIcons]; | ||
| return icon ? icon(size, className) : null; | ||
| } No newline at end of file |
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion
Add forwardRef and dark mode support to align with Langflow icon patterns.
Based on the established patterns in the Langflow codebase, icon components should use React.forwardRef and support an isdark prop for theme switching.
Apply this refactor to align with established patterns:
+interface IconProps {
+ name: string;
+ size?: number;
+ className?: string;
+ isdark?: boolean;
+}
-export default function CustomIcon({ name, size = 24, className }: IconProps) {
+const CustomIcon = React.forwardRef<SVGSVGElement, IconProps>(
+ ({ name, size = 24, className, isdark }, ref) => {
const icon = customIcons[name as keyof typeof customIcons];
- return icon ? icon(size, className) : null;
-}
+ return icon ? icon(size, className, ref) : null;
+ });
+
+CustomIcon.displayName = 'CustomIcon';
+export default CustomIcon;Also update the icon functions to accept a ref parameter and apply isdark styling where appropriate.
Committable suggestion skipped: line range outside the PR's diff.
🤖 Prompt for AI Agents
In docs/src/components/CustomIcon/index.tsx around lines 66 to 69, refactor the
CustomIcon component to use React.forwardRef to properly forward refs as per
Langflow icon patterns. Add an isdark prop to support dark mode styling and pass
it to the icon functions. Update the icon functions to accept a ref parameter
and apply conditional styling based on the isdark prop to align with the
established theme switching conventions.
Comment on lines
+62
to
+82
| .quickLinkCard { | ||
| background-color: var(--ifm-background-surface-color); | ||
| border: 1px solid var(--ifm-color-emphasis-200); | ||
| border-radius: var(--ifm-global-radius); | ||
| padding: 1.5rem; | ||
| display: flex; | ||
| flex-direction: column; | ||
| gap: 1rem; | ||
| transition: all 0.3s ease; | ||
| text-decoration: none; | ||
| color: inherit; | ||
| position: relative; | ||
| overflow: hidden; | ||
| } | ||
|
|
||
| .quickLinkCard:hover { | ||
| border-color: var(--ifm-color-emphasis-800); | ||
| transform: translateY(-2px); | ||
| text-decoration: none; | ||
| color: inherit; | ||
| } |
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion
Add keyboard-visible focus style for .quickLinkCard
Interactive cards receive hover feedback only. Users navigating with the keyboard will not get any visual indication of focus, which hurts accessibility (WCAG 2.1 §2.4.7). Add a :focus-visible rule that mirrors (or complements) the hover state.
.quickLinkCard:hover {
border-color: var(--ifm-color-emphasis-800);
transform: translateY(-2px);
text-decoration: none;
color: inherit;
}
+
+.quickLinkCard:focus-visible {
+ outline: 2px solid var(--ifm-color-primary);
+ outline-offset: 2px;
+ border-color: var(--ifm-color-primary);
+ transform: translateY(-2px);
+}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| .quickLinkCard { | |
| background-color: var(--ifm-background-surface-color); | |
| border: 1px solid var(--ifm-color-emphasis-200); | |
| border-radius: var(--ifm-global-radius); | |
| padding: 1.5rem; | |
| display: flex; | |
| flex-direction: column; | |
| gap: 1rem; | |
| transition: all 0.3s ease; | |
| text-decoration: none; | |
| color: inherit; | |
| position: relative; | |
| overflow: hidden; | |
| } | |
| .quickLinkCard:hover { | |
| border-color: var(--ifm-color-emphasis-800); | |
| transform: translateY(-2px); | |
| text-decoration: none; | |
| color: inherit; | |
| } | |
| .quickLinkCard { | |
| background-color: var(--ifm-background-surface-color); | |
| border: 1px solid var(--ifm-color-emphasis-200); | |
| border-radius: var(--ifm-global-radius); | |
| padding: 1.5rem; | |
| display: flex; | |
| flex-direction: column; | |
| gap: 1rem; | |
| transition: all 0.3s ease; | |
| text-decoration: none; | |
| color: inherit; | |
| position: relative; | |
| overflow: hidden; | |
| } | |
| .quickLinkCard:hover { | |
| border-color: var(--ifm-color-emphasis-800); | |
| transform: translateY(-2px); | |
| text-decoration: none; | |
| color: inherit; | |
| } | |
| .quickLinkCard:focus-visible { | |
| outline: 2px solid var(--ifm-color-primary); | |
| outline-offset: 2px; | |
| border-color: var(--ifm-color-primary); | |
| transform: translateY(-2px); | |
| } |
🤖 Prompt for AI Agents
In docs/src/pages/index.module.css between lines 62 and 82, the .quickLinkCard
class has hover styles but lacks a :focus-visible style, which is needed for
keyboard accessibility. Add a .quickLinkCard:focus-visible CSS rule that applies
similar visual feedback as the hover state, such as changing border color and
applying the translateY transform, to ensure keyboard users can see when the
card is focused.
Comment on lines
28
to
29
| Alternatively, connect the vector database component's **Retriever** port to a [retriever tool](components-tools#retriever-tool), and then to an [agent](/docs/components-agents) component. This enables the agent to use your vector database as a tool and make decisions based on the available data. | ||
|
|
Contributor
There was a problem hiding this comment.
Broken internal link: missing /docs/ prefix
components-tools#retriever-tool bypasses the new URL convention introduced in this PR.
Replace with /docs/components-tools#retriever-tool to avoid a 404.
🤖 Prompt for AI Agents
In docs/docs/Components/components-vector-stores.md around lines 28 to 29, the
internal link to the retriever tool is missing the /docs/ prefix, causing a
broken link. Update the link from components-tools#retriever-tool to
/docs/components-tools#retriever-tool to follow the new URL convention and
prevent a 404 error.
Comment on lines
+90
to
+119
| <Link to={useBaseUrl('/')} className={styles.card}> | ||
| <div className={styles.cardIcon}> | ||
| <BookMarked size={16} strokeWidth={1.25} /> | ||
| </div> | ||
| <div className={styles.cardContent}> | ||
| <div className={styles.cardTitle}>About Langflow</div> | ||
| </div> | ||
| <div className={styles.cardArrow}> | ||
| <ArrowRight size={20} strokeWidth={1.25} /> | ||
| </div> | ||
| </Link> | ||
| <Link to={useBaseUrl('/docs/get-started-installation')} className={styles.card}> | ||
| <div className={styles.cardIcon}> | ||
| <MonitorDown size={16} strokeWidth={1.25} /> | ||
| </div> | ||
| <div className={styles.cardContent}> | ||
| <div className={styles.cardTitle}>Install Langflow</div> | ||
| </div> | ||
| <div className={styles.cardArrow}> | ||
| <ArrowRight size={20} strokeWidth={1.25} /> | ||
| </div> | ||
| </Link> | ||
| <Link to={useBaseUrl('/')} className={styles.card}> | ||
| <div className={styles.cardIcon}> | ||
| <GraduationCap size={16} strokeWidth={1.25} /> | ||
| </div> | ||
| <div className={styles.cardContent}> | ||
| <div className={styles.cardTitle}>Tutorial</div> | ||
| </div> | ||
| <div className={styles.cardArrow}> | ||
| <ArrowRight size={20} strokeWidth={1.25} /> | ||
| </div> | ||
| </Link> |
Contributor
There was a problem hiding this comment.
Placeholder links ('/') break navigation
Cards “About Langflow” and “Tutorial” point to the site root ('/'). This reloads the docs home instead of the expected pages. Provide the correct doc URLs or remove the cards until the destinations exist.
🤖 Prompt for AI Agents
In docs/src/pages/index.tsx between lines 90 and 122, the "About Langflow" and
"Tutorial" Link components use placeholder paths ('/') that cause navigation to
the site root instead of the intended pages. Update these Link components to use
the correct documentation URLs for their destinations or remove these cards if
the target pages do not yet exist, ensuring navigation leads to valid content.
Comment on lines
+490
to
+499
| .lf-navbar-search .navbar__search input { | ||
| width: 100% !important; | ||
| min-width: 500px !important; | ||
| } | ||
|
|
||
| .lf-navbar-search .DocSearch-Button { | ||
| width: 100% !important; | ||
| min-width: 300px !important; | ||
| max-width: 500px !important; | ||
| } |
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion
Search input forces 500 px min-width
The rule
.lf-navbar-search .navbar__search input { min-width: 500px; }overflows small laptops and tablets (< 1024 px) and is not cancelled by later media queries. Use min-width:0 and rely on the container’s max-width instead:
-.lf-navbar-search .navbar__search input {
- width: 100% !important;
- min-width: 500px !important;
- max-width: 500px !important;
-}
+.lf-navbar-search .navbar__search input {
+ width: 100% !important;
+ min-width: 0 !important; /* allow shrink */
+ max-width: 500px !important;
+}🤖 Prompt for AI Agents
In docs/css/custom.css around lines 490 to 499, the min-width of 500px on the
search input causes overflow on smaller screens and is not overridden by media
queries. Change the min-width from 500px to 0 on the .lf-navbar-search
.navbar__search input selector to prevent overflow and allow the container's
max-width to control sizing.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 10
🔭 Outside diff range comments (15)
docs/docs/Integrations/Google/integrations-setup-google-cloud-vertex-ai-langflow.md (1)
1-4: Adddescriptionfront-matter fieldThe style guide mandates a
descriptionin every doc’s front-matter.
Add a short, sentence-style summary so search results and meta tags are populated correctly.--- title: Integrate Google Cloud Vertex AI with Langflow slug: /integrations-setup-google-cloud-vertex-ai-langflow +description: Step-by-step guide to authenticate and use Vertex AI components from Langflow. ---docs/docs/Configuration/configuration-api-keys.md (1)
1-4: Front-matter missingdescriptionAdd a concise description per docs guidelines.
--- title: API keys slug: /configuration-api-keys +description: Generate, use, and manage Langflow API and component keys. ---docs/docs/Templates/simple-agent.md (1)
1-4: Adddescriptionto front-matterRequired by the docs style guide for SEO and consistency.
--- title: Simple agent slug: /simple-agent +description: Build and run a starter Tool-calling agent flow in Langflow. ---docs/docs/Develop/webhook.md (1)
1-4: Missingdescriptionfront-matterAdd a short description to comply with docs requirements.
--- title: Trigger flows with webhooks slug: /webhook +description: Use the Webhook component to start Langflow flows from external HTTP requests. ---docs/docs/Support/troubleshooting.md (1)
1-4: Adddescriptionto front-matterEvery doc needs a
descriptionfor consistency and metadata.--- title: Troubleshoot Langflow slug: /troubleshoot +description: Common problems and fixes for installing, running, and upgrading Langflow. ---docs/docs/Components/components-helpers.md (1)
1-4: Add mandatorydescriptionto the front-matterSite-wide guideline requires every doc front-matter to contain both
titleanddescription.
Please add a concise description to avoid build-time warnings and to improve SEO.--- title: Helpers slug: /components-helpers +description: Learn how to use Langflow helper components such as Store Message, Message History, Batch Run, and more. ---docs/docs/API-Reference/api-files.md (1)
1-4: MissingdescriptionfieldAll docs pages need a front-matter
description. Add one to keep the build clean.--- title: Files endpoints slug: /api-files +description: Reference for /v1/files and /v2/files endpoints, including upload, download, list and delete operations. ---docs/docs/Contributing/contributing-components.md (1)
1-4: Add adescriptionto front-matterRequired by the docs style-guide.
--- title: Contribute components slug: /contributing-components +description: Step-by-step guide to adding new or example components to Langflow and best-practice tips. ---docs/docs/Components/components-embedding-models.md (1)
1-4: Front-matter missingdescription--- title: Embeddings slug: /components-embedding-models +description: Catalog of Langflow embedding-model components and how to use them in flows. ---docs/docs/Components/components-processing.md (1)
1-4: Adddescriptionfield--- title: Processing slug: /components-processing +description: Documentation for Langflow processing components such as Split Text, Data Operations and Smart Function. ---docs/docs/Get-Started/get-started-installation.md (1)
1-4: Missingdescriptionin front-matterEvery markdown doc must include a
descriptionin its front-matter.--- title: Install Langflow +description: Step-by-step instructions to install and run Langflow via Desktop, Docker, or Python. slug: /get-started-installation ---docs/docs/Templates/memory-chatbot.md (1)
1-4: Adddescriptionfield to front-matter--- title: Memory chatbot +description: Build a chatbot that uses the Message History component to provide conversational memory. slug: /memory-chatbot ---docs/docs/Components/components-custom-components.md (1)
1-4: Front-matter missingdescription--- title: Create custom Python components +description: Learn how to extend Langflow with your own Python Components. slug: /components-custom-components ---docs/docs/Get-Started/get-started-quickstart.md (1)
1-4: Add missingdescriptionin front-matter--- title: Quickstart +description: A hands-on guide to running your first Langflow template and calling it via the API. slug: /get-started-quickstart ---docs/docs/Concepts/mcp-server.md (1)
1-4: Front-matter lacksdescription--- title: Use Langflow as an MCP server +description: Expose Langflow Flows as Model Context Protocol tools and connect external clients. slug: /mcp-server ---
🧹 Nitpick comments (51)
docs/docs/Templates/basic-prompting.md (1)
29-31: Add descriptive alt text for the image.Images should include meaningful alt text per the docs style-guide.
- +docs/src/theme/Footer.js (1)
25-30: Avoid “magic numbers” in inline styles.Hard-coding
right: '21px'andbottom: '21px'makes later tweaks tedious. Consider a CSS class or custom property so design tokens live in one place.- right: '21px', - bottom: '21px', + /* align with --lf-spacing-l to keep design tokens centralized */ + right: 'var(--lf-spacing-l, 21px)', + bottom: 'var(--lf-spacing-l, 21px)',docs/docs/Templates/travel-planning-agent.md (2)
10-11: Terminology: use “OpenAI”, not “Open AI”.Consistent capitalization keeps docs polished.
-In this flow, multiple **Tool-calling agents** reason using an **Open AI** LLM to plan a travel journey. +In this flow, multiple **Tool-calling agents** reason using an **OpenAI** LLM to plan a travel journey.
30-32: Provide alt text for images.- +docs/docs/Concepts/concepts-playground.md (2)
10-10: Typo in component link description.Consider clarifying to “an [Input or Output component]” for consistency with style (bold UI element names).
No functional issue with the/docs/components-iopath.
94-94: List-style inconsistency flagged by markdownlint.Use
*to match the rest of the document’s unordered lists:- - [Session ID](/docs/session-id) + * [Session ID](/docs/session-id)docs/docs/Configuration/configuration-authentication.md (1)
109-109: Anchor link LGTM — small style tweak suggested.Consider dropping “Authentication configuration values” repetition in the link text for brevity:
[...] variables described in [the configuration table](/docs/configuration-authentication#authentication-configuration-values).docs/docs/Templates/financial-report-parser.md (2)
8-8: Capitalize Langflow concepts (“Structured Output”, “Parser”, “Flow”, “Component”).These are first-class Langflow concepts and should follow docs style-guide capitalization.
-Build a **Financial Report Parser** flow with the [Structured output](/docs/components-helpers#structured-output) and [Parser](/docs/components-processing#parser) components to parse LLM responses into a structured format. +Build a **Financial Report Parser** **Flow** with the [**Structured Output**](/docs/components-helpers#structured-output) and [**Parser**](/docs/components-processing#parser) **Components** to parse LLM responses into a structured format.
10-10: Hyphenate “preloaded” correctly.LanguageTool flags “pre-loaded”. The single-word form is standard.
-In this example, the **Chat Input** component is pre-loaded with a sample financial report to demonstrate extracting `Gross Profit`, `EBITDA`, and `Net Income`. +In this example, the **Chat Input** component is preloaded with a sample financial report to demonstrate extracting `Gross Profit`, `EBITDA`, and `Net Income`.docs/docs/Components/components-prompts.md (2)
16-16: Capitalize starter-flow name.-An example of modifying a prompt can be found in [Vector RAG starter flow](/docs/vector-store-rag), where a basic chatbot flow is extended to include a full vector RAG pipeline. +An example of modifying a prompt can be found in the [Vector RAG Starter Flow](/docs/vector-store-rag), where a basic chatbot flow is extended to include a full vector RAG pipeline.
33-33: Capitalize and clarify flow title.-…behavior is available in the [sequential tasks agent starter flow](/docs/sequential-agent). +…behavior is available in the [Sequential Tasks Agent Starter Flow](/docs/sequential-agent).docs/docs/Agents/agents-tools.md (2)
32-32: Capitalize flow name.-1. Create the [Simple agent starter flow](/docs/simple-agent). +1. Create the [Simple Agent Starter Flow](/docs/simple-agent).
165-165: Capitalize component name.-An agent can use flows that are saved in your workspace as tools with the [Run flow](/docs/components-logic#run-flow) component. +An agent can use flows that are saved in your workspace as tools with the [Run Flow](/docs/components-logic#run-flow) component.docs/docs/Contributing/contributing-community.md (2)
21-21: Minor wording tweak for smoother reading.-Because Langflow is an open-source project, the more visible the repository is, the more likely the project is to attract [contributors](/docs/contributing-how-to-contribute). +Because Langflow is an open-source project, the more visible the repository is, the more likely it is to attract [contributors](/docs/contributing-how-to-contribute).
35-35: Grammar: use “to” for parallel actions.-For more information, see [Get help and request enhancements](/docs/contributing-github-issues). +For more information, see [Get help and request enhancements](/docs/contributing-github-issues).Consider rephrasing to “see How to get help and request enhancements” if you touch this line again.
docs/docs/Integrations/Nvidia/integrations-nvidia-g-assist.md (1)
35-37: Minor redundancy in output description.Both bullets explain that the response is wrapped in a
Messageobject. Consider collapsing into one clearer sentence to avoid repetition.docs/docs/Templates/document-qa.md (1)
19-19: Provide descriptive alt text for accessibility.- +docs/docs/Concepts/concepts-overview.md (1)
14-15: Capitalize “Component” to comply with docs terminologyPer the docs style guide, when referring to Langflow concepts the word must be capitalized.
-Flows consist of [components](/docs/concepts-components) that you configure … +Flows consist of [Components](/docs/concepts-components) that you configure …docs/docs/Deployment/deployment-overview.md (1)
22-25: Stylistic: three successive sentences start with “The”Static analysis flagged repetition. Consider merging or re-wording for smoother reading:
-The **Langflow IDE** includes … -The Langflow IDE can be deployed on … -The **Langflow runtime** is … +The **Langflow IDE** includes … +You can deploy the IDE on … +By contrast, the **Langflow runtime** is …docs/docs/Integrations/mcp-component-astra.md (1)
10-11: Terminology & route validation
- Capitalize Component when naming Langflow components.
-Use the [MCP connection component](/docs/mcp-client) … +Use the [MCP connection Component](/docs/mcp-client) …
- Verify that newly prefixed slugs (
/docs/mcp-client,/docs/simple-agent,/docs/configuration-global-variables) exist post-refactor.Also applies to: 20-23, 38-39
docs/docs/Templates/simple-agent.md (1)
11-11: Fix product naming: use “OpenAI”, not “Open AI”The brand is a single word; update to maintain consistency.
-In this flow, the **Tool-calling agent** reasons using an **Open AI** LLM. +In this flow, the **Tool-calling agent** reasons using an **OpenAI** LLM.docs/docs/Support/troubleshooting.md (1)
14-16: Broken plural phrase“Custom components and integrations issues” sounds awkward.
Recommend singular “integration” or rephrase for clarity.-## Custom components and integrations issues +## Custom components and integration issuesdocs/docs/Components/components-agents.md (1)
24-25: Add the missing comma after the introductory clause"For a multi-agent example see …" should read "For a multi-agent example, see …" to comply with standard punctuation and the docs style guide.
-For a multi-agent example see [Create a flow with an agent](/docs/agents). +For a multi-agent example, see [Create a flow with an agent](/docs/agents).docs/docs/Components/components-io.md (1)
96-102: Consider inline-code formatting for object names in the bullet list
DataandDataFrameare types rather than prose; wrapping them in back-ticks would be more consistent with the rest of the document.-* [Data](/docs/concepts-objects#data-object) -* [DataFrame](/docs/concepts-objects#dataframe-object) +* [`Data`](/docs/concepts-objects#data-object) +* [`DataFrame`](/docs/concepts-objects#dataframe-object)docs/docs/Components/components-memories.md (1)
10-13: Remove superfluous comma before “because”The clause is essential, so the comma breaks the sentence unnecessarily.
-They are distinct from vector store components, because they are built specifically for storing and retrieving chat messages from external databases. +They are distinct from vector store components because they are built specifically for storing and retrieving chat messages from external databases.docs/docs/API-Reference/api-flows-run.md (1)
9-12: Fix typo “amd” → “and”Small spelling error in the first sentence.
-Use the `/run` amd `/webhook` endpoints to run flows. +Use the `/run` and `/webhook` endpoints to run flows.docs/docs/API-Reference/api-projects.md (1)
77-77: Endpoint text should be formatted consistently
/allis styled as inline code but/flows/readis not. For consistency with the docs style-guide, wrap the second endpoint in back-ticks as well (or style both as prose).-... [`/all`](/docs/api-reference-api-examples#get-all-components) and [/flows/read](/docs/api-flows#read-flows) endpoints ... +... [`/all`](/docs/api-reference-api-examples#get-all-components) and [`/flows/read`](/docs/api-flows#read-flows) endpoints ...Minor, but it keeps formatting uniform across the API reference.
docs/docs/Integrations/Nvidia/integrations-nvidia-ingest.md (1)
88-88: Tiny grammar nit – add a commaA comma after “objects” improves readability.
-The **NVIDIA Retriever Extraction** component outputs a list of [Data](/docs/concepts-objects#data-object) objects where each object contains: +The **NVIDIA Retriever Extraction** component outputs a list of [Data](/docs/concepts-objects#data-object) objects, where each object contains:docs/docs/Develop/Clients/typescript-client.md (1)
101-103: Inconsistent casing:sessionIDvssessionIdThe API object returned in the sample response uses the camel-case property
sessionId, yet the explanatory bullet refers tosessionID. This subtle mismatch can confuse readers copying field names.-* The `sessionID` value is a unique identifier … +* The `sessionId` value is a unique identifier …docs/docs/Concepts/concepts-voice-mode.md (1)
28-29: Capitalize Langflow conceptsPer the docs style guide, concept names must be capitalized. Change global variable → Global variable (appears twice).
-This key is saved as a [global variable](/docs/configuration-global-variables) … +This key is saved as a [Global variable](/docs/configuration-global-variables) …Also applies to: 38-39
docs/docs/Components/components-models.md (2)
18-21: Image directly below needs alt-textLine 22 embeds an image with empty alt text (
). The style guide requires descriptive alt text for accessibility.- +
230-233: Same missing alt-text for Groq component image- +docs/docs/API-Reference/api-reference-api-examples.md (1)
160-162: Consistent bullet phrasingThree successive bullets start with “Use the Langflow API to …”; static-analysis flagged this repetition. Consider tightening wording, e.g.:
-- Use the Langflow API to [run a flow](/docs/api-flows-run). -- Use the Langflow API to [upload files](/docs/api-files). -- Use the Langflow API to [get flow logs](/docs/api-logs). +- [Run a flow](/docs/api-flows-run) +- [Upload files](/docs/api-files) +- [Retrieve flow logs](/docs/api-logs)docs/docs/API-Reference/api-files.md (1)
247-248: Minor style: successive sentences start with “For more information”Consider merging or re-phrasing to avoid the repetition flagged by the linter.
-For more information, see ... +See ... for more details.docs/docs/Components/components-processing.md (1)
16-16: Image missing alt textMarkdown-lint flagged this:
.- +docs/docs/Get-Started/get-started-installation.md (1)
26-27: Capitalize the Langflow concept “Flow”Guidelines require capital “Flow” when referring to the concept.
-After confirming that Langflow is running, create your first flow with the [Quickstart](/docs/get-started-quickstart). +After confirming that Langflow is running, create your first **Flow** with the [Quickstart](/docs/get-started-quickstart).Also applies to: 130-131
docs/docs/Templates/memory-chatbot.md (2)
12-13: Capitalize Langflow entities in link text“Basic prompting flow” → “Basic Prompting Flow”.
-This flow extends the [basic prompting flow](/docs/basic-prompting) … +This Flow extends the [Basic Prompting Flow](/docs/basic-prompting) …
77-78: Plural form still needs capital “Components”Style guide: always capitalize Component.
-[Memory components](/docs/components-memories) +[Memory Components](/docs/components-memories)docs/docs/Components/components-custom-components.md (1)
109-110: Link text should match capitalisation rules-For more information, see [Custom component inputs and outputs](/docs/components-custom-components#custom-component-inputs-and-outputs). +For more information, see [Custom Component Inputs and Outputs](/docs/components-custom-components#custom-component-inputs-and-outputs).docs/docs/Get-Started/get-started-quickstart.md (1)
14-15: Multiple style-guide violations (capitalisation)Capitalize “Component”, “Components”, “Flow”, and “Global Variable”.
-[A running Langflow instance] +[A running Langflow Instance] -[Agent component] +[Agent Component] -[Chat I/O components] +[Chat I/O Components] -[Calculator component] +[Calculator Component] -[URL component] +[URL Component] -click <Icon …> **Globe** to store the key in a Langflow [global variable] +click <Icon …> **Globe** to store the key in a Langflow [Global Variable] -* [Model Context Protocol (MCP) servers](/docs/mcp-server) +* [Model Context Protocol (MCP) Servers](/docs/mcp-server)Also applies to: 23-26, 30-31, 520-521
docs/docs/Concepts/mcp-server.md (1)
159-165: Capitalise concept “Document Q&A Flow”-For example, an agent won't know that flow … is a [Document Q&A](/docs/document-qa) flow +For example, an agent won't know that Flow … is a [Document Q&A Flow](/docs/document-qa)docs/docs/Components/components-tools.md (2)
124-128: Add missing anchor for precisionBoth table rows link to
/docs/concepts-objects, but other pages (e.g. components-logic.md) use#data-objectfor the same target. Adding the anchor keeps behaviour consistent and scrolls the reader to the exact section.-| Data | List[Data] | A list of [Data](/docs/concepts-objects) objects … +| Data | List[Data] | A list of [Data](/docs/concepts-objects#data-object) objects …
156-160: Same anchor suggestion applies here-| Data | List[Data] | A list of [Data](/docs/concepts-objects) objects … +| Data | List[Data] | A list of [Data](/docs/concepts-objects#data-object) objects …docs/docs/Components/components-data.md (1)
107-109: Add anchor for consistencyElsewhere you use
#data-object; adding it here keeps linking behaviour predictable:-… converts the content into a [Data](/docs/concepts-objects) object. +… converts the content into a [Data](/docs/concepts-objects#data-object) object.docs/src/theme/Navbar.js (2)
6-7: Inconsistent icon usage: mixing lucide-react and custom icons.The component imports both
lucide-reacticons and the customIconcomponent, creating inconsistency. Consider using only the custom icon system for consistency.- import { MonitorDown, Moon, Sun } from "lucide-react"; - import Icon from "@site/src/components/icon"; + import Icon from "@site/src/components/icon";- <MonitorDown size={16} /> + <Icon name="monitor-down" size={16} />- {colorMode === "dark" ? ( - <Moon size={18} /> - ) : ( - <Sun size={18} /> - )} + <Icon name={colorMode === "dark" ? "moon" : "sun"} size={18} />Also applies to: 70-70, 83-83, 104-104, 106-106
88-95: Move inline styles to CSS classes.The inline styling for the separator should be moved to CSS classes for better maintainability and consistency with the rest of the styling.
- <div - style={{ - width: '1px', - height: '20px', - background: 'var(--ifm-color-emphasis-300)', - margin: '0 0.25rem' - }} - ></div> + <div className="lf-navbar-separator"></div>Add to your CSS file:
.lf-navbar-separator { width: 1px; height: 20px; background: var(--ifm-color-emphasis-300); margin: 0 0.25rem; }docs/src/components/CustomIcon/index.tsx (1)
10-64: Consider adding missing icons for complete lucide-react replacement.The component is missing some icons that are used in the navbar (like
monitor-down,moon,sun). Consider adding these to ensure complete replacement of lucide-react usage.const customIcons = { + "monitor-down": (size: number, className?: string) => ( + <svg width={size} height={size} viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" className={className}> + <path d="M12 13V7M9 10L12 13L15 10M20 4V12C20 13.1046 19.1046 14 18 14H6C4.89543 14 4 13.1046 4 12V4C4 2.89543 4.89543 2 6 2H18C19.1046 2 20 2.89543 20 4ZM16 18H8M12 18V22M8 22H16" stroke="currentColor" strokeWidth={1.5} strokeLinecap="round" strokeLinejoin="round"/> + </svg> + ), + moon: (size: number, className?: string) => ( + <svg width={size} height={size} viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" className={className}> + <path d="M21 12.79A9 9 0 1 1 11.21 3A7 7 0 0 0 21 12.79Z" stroke="currentColor" strokeWidth={1.5} strokeLinecap="round" strokeLinejoin="round"/> + </svg> + ), + sun: (size: number, className?: string) => ( + <svg width={size} height={size} viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" className={className}> + <circle cx="12" cy="12" r="5" stroke="currentColor" strokeWidth={1.5}/> + <path d="M12 1V3M12 21V23M4.22 4.22L5.64 5.64M18.36 18.36L19.78 19.78M1 12H3M21 12H23M4.22 19.78L5.64 18.36M18.36 5.64L19.78 4.22" stroke="currentColor" strokeWidth={1.5} strokeLinecap="round"/> + </svg> + ), agents: (size: number, className?: string) => (docs/src/components/icon/index.tsx (1)
4-10: Update documentation comment to reflect new implementation.The comment example still references "AlertCircle" which is a lucide-react icon name, but the component now only supports custom icons. Update the example to use an icon that exists in the CustomIcon component.
/* How to use this component: import Icon from "@site/src/components/icon"; -<Icon name="AlertCircle" size={24} color="red" /> +<Icon name="github" size={24} className="text-red-500" /> */docs/src/pages/index.tsx (1)
22-24: Unused variablebaseUrlcan be dropped
const baseUrl = useBaseUrl('/')is never referenced afterwards. Leaving it will trip most linters/CI and slightly inflates the bundle.- const baseUrl = useBaseUrl('/');docs/src/pages/index.module.css (2)
24-30: Avoid!importantin component-scoped CSSUsing
!important(font-size: 2rem !important;) inside a CSS-module defeats its encapsulation and makes future overrides painful. The selector already has module hashing ‑ removing the flag should be safe.- font-size: 2rem !important; + font-size: 2rem;
121-131: DuplicatecardsGriddeclarations – consolidate for maintainability
.cardsGridgets its column layout defined three times (default 4, ≥768 4, ≤767 2). The ≥768 block re-states the default and can be removed; keeping only default + ≤767 is clearer.@media (min-width: 768px) { - .cardsGrid { - grid-template-columns: repeat(4, 1fr); - } }Also applies to: 259-263, 268-272
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (3)
docs/package-lock.jsonis excluded by!**/package-lock.jsondocs/static/img/lf-agent.pngis excluded by!**/*.pngdocs/yarn.lockis excluded by!**/yarn.lock,!**/*.lock
📒 Files selected for processing (80)
docs/css/custom.css(6 hunks)docs/docs/API-Reference/api-build.md(3 hunks)docs/docs/API-Reference/api-files.md(5 hunks)docs/docs/API-Reference/api-flows-run.md(4 hunks)docs/docs/API-Reference/api-flows.md(3 hunks)docs/docs/API-Reference/api-monitor.md(1 hunks)docs/docs/API-Reference/api-projects.md(1 hunks)docs/docs/API-Reference/api-reference-api-examples.md(4 hunks)docs/docs/Agents/agents-tools.md(3 hunks)docs/docs/Agents/agents.md(4 hunks)docs/docs/Components/components-agents.md(1 hunks)docs/docs/Components/components-custom-components.md(4 hunks)docs/docs/Components/components-data.md(5 hunks)docs/docs/Components/components-embedding-models.md(3 hunks)docs/docs/Components/components-helpers.md(4 hunks)docs/docs/Components/components-io.md(5 hunks)docs/docs/Components/components-logic.md(5 hunks)docs/docs/Components/components-memories.md(1 hunks)docs/docs/Components/components-models.md(4 hunks)docs/docs/Components/components-processing.md(28 hunks)docs/docs/Components/components-prompts.md(2 hunks)docs/docs/Components/components-tools.md(4 hunks)docs/docs/Components/components-vector-stores.md(24 hunks)docs/docs/Components/mcp-client.md(5 hunks)docs/docs/Concepts/concepts-components.md(2 hunks)docs/docs/Concepts/concepts-file-management.md(1 hunks)docs/docs/Concepts/concepts-objects.md(1 hunks)docs/docs/Concepts/concepts-overview.md(5 hunks)docs/docs/Concepts/concepts-playground.md(3 hunks)docs/docs/Concepts/concepts-publish.md(2 hunks)docs/docs/Concepts/concepts-voice-mode.md(3 hunks)docs/docs/Concepts/embedded-chat-widget.md(3 hunks)docs/docs/Concepts/mcp-server.md(6 hunks)docs/docs/Configuration/configuration-api-keys.md(2 hunks)docs/docs/Configuration/configuration-authentication.md(1 hunks)docs/docs/Configuration/configuration-global-variables.md(1 hunks)docs/docs/Contributing/contributing-community.md(2 hunks)docs/docs/Contributing/contributing-components.md(3 hunks)docs/docs/Contributing/contributing-github-issues.md(2 hunks)docs/docs/Deployment/deployment-docker.md(1 hunks)docs/docs/Deployment/deployment-kubernetes-prod.md(1 hunks)docs/docs/Deployment/deployment-overview.md(2 hunks)docs/docs/Develop/Clients/typescript-client.md(4 hunks)docs/docs/Develop/develop-application.md(9 hunks)docs/docs/Develop/develop-overview.md(1 hunks)docs/docs/Develop/memory.md(2 hunks)docs/docs/Develop/session-id.md(1 hunks)docs/docs/Develop/webhook.md(3 hunks)docs/docs/Get-Started/get-started-installation.md(4 hunks)docs/docs/Get-Started/get-started-quickstart.md(4 hunks)docs/docs/Get-Started/welcome-to-langflow.md(0 hunks)docs/docs/Integrations/Arize/integrations-arize.md(1 hunks)docs/docs/Integrations/Cleanlab/integrations-cleanlab.md(1 hunks)docs/docs/Integrations/Composio/integrations-composio.md(2 hunks)docs/docs/Integrations/Google/integrations-setup-google-cloud-vertex-ai-langflow.md(1 hunks)docs/docs/Integrations/Google/integrations-setup-google-oauth-langflow.md(1 hunks)docs/docs/Integrations/Notion/notion-agent-conversational.md(1 hunks)docs/docs/Integrations/Notion/notion-agent-meeting-notes.md(1 hunks)docs/docs/Integrations/Nvidia/integrations-nvidia-g-assist.md(1 hunks)docs/docs/Integrations/Nvidia/integrations-nvidia-ingest.md(2 hunks)docs/docs/Integrations/Nvidia/integrations-nvidia-nim-wsl2.md(1 hunks)docs/docs/Integrations/mcp-component-astra.md(3 hunks)docs/docs/Support/troubleshooting.md(4 hunks)docs/docs/Templates/basic-prompting.md(1 hunks)docs/docs/Templates/blog-writer.md(1 hunks)docs/docs/Templates/document-qa.md(2 hunks)docs/docs/Templates/financial-report-parser.md(2 hunks)docs/docs/Templates/memory-chatbot.md(2 hunks)docs/docs/Templates/sequential-agent.md(2 hunks)docs/docs/Templates/simple-agent.md(2 hunks)docs/docs/Templates/travel-planning-agent.md(1 hunks)docs/docs/Templates/vector-store-rag.md(1 hunks)docs/docusaurus.config.js(5 hunks)docs/sidebars.js(0 hunks)docs/src/components/CustomIcon/index.tsx(1 hunks)docs/src/components/icon/index.tsx(2 hunks)docs/src/pages/index.module.css(1 hunks)docs/src/pages/index.tsx(1 hunks)docs/src/theme/Footer.js(1 hunks)docs/src/theme/Navbar.js(1 hunks)
💤 Files with no reviewable changes (2)
- docs/sidebars.js
- docs/docs/Get-Started/welcome-to-langflow.md
🧰 Additional context used
📓 Path-based instructions (2)
`docs/docs/**/*.{md,mdx}`: All documentation content must be placed within the '...
docs/docs/**/*.{md,mdx}: All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
All documentation markdown files must start with a frontmatter block containing at least 'title' and 'description' fields.
Use admonitions (:::tip, :::warning, :::danger) in markdown files to highlight important information, warnings, or critical issues.
Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Use code blocks with language identifiers and optional titles for code examples in markdown documentation.
Documentation 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', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
📄 Source: CodeRabbit Inference Engine (.cursor/rules/docs_development.mdc)
List of files the instruction was applied to:
docs/docs/API-Reference/api-monitor.mddocs/docs/Integrations/Nvidia/integrations-nvidia-nim-wsl2.mddocs/docs/Templates/financial-report-parser.mddocs/docs/Develop/session-id.mddocs/docs/Configuration/configuration-global-variables.mddocs/docs/Templates/travel-planning-agent.mddocs/docs/Concepts/concepts-overview.mddocs/docs/Integrations/Arize/integrations-arize.mddocs/docs/Configuration/configuration-authentication.mddocs/docs/Integrations/Notion/notion-agent-conversational.mddocs/docs/Contributing/contributing-github-issues.mddocs/docs/API-Reference/api-flows.mddocs/docs/Deployment/deployment-docker.mddocs/docs/Support/troubleshooting.mddocs/docs/Integrations/Nvidia/integrations-nvidia-g-assist.mddocs/docs/Templates/vector-store-rag.mddocs/docs/Deployment/deployment-kubernetes-prod.mddocs/docs/Develop/develop-application.mddocs/docs/Templates/basic-prompting.mddocs/docs/Integrations/Cleanlab/integrations-cleanlab.mddocs/docs/Agents/agents.mddocs/docs/Configuration/configuration-api-keys.mddocs/docs/Develop/develop-overview.mddocs/docs/Concepts/concepts-objects.mddocs/docs/Concepts/concepts-playground.mddocs/docs/Templates/document-qa.mddocs/docs/Templates/blog-writer.mddocs/docs/Integrations/Google/integrations-setup-google-oauth-langflow.mddocs/docs/Concepts/embedded-chat-widget.mddocs/docs/Integrations/Notion/notion-agent-meeting-notes.mddocs/docs/Contributing/contributing-community.mddocs/docs/Concepts/concepts-voice-mode.mddocs/docs/API-Reference/api-projects.mddocs/docs/API-Reference/api-reference-api-examples.mddocs/docs/Agents/agents-tools.mddocs/docs/API-Reference/api-flows-run.mddocs/docs/Components/components-prompts.mddocs/docs/Concepts/concepts-publish.mddocs/docs/Integrations/Nvidia/integrations-nvidia-ingest.mddocs/docs/Deployment/deployment-overview.mddocs/docs/Integrations/Composio/integrations-composio.mddocs/docs/Templates/simple-agent.mddocs/docs/Develop/memory.mddocs/docs/Develop/webhook.mddocs/docs/Concepts/concepts-components.mddocs/docs/Templates/sequential-agent.mddocs/docs/API-Reference/api-files.mddocs/docs/Components/components-io.mddocs/docs/Components/mcp-client.mddocs/docs/Components/components-memories.mddocs/docs/Integrations/mcp-component-astra.mddocs/docs/Get-Started/get-started-installation.mddocs/docs/Components/components-processing.mddocs/docs/Components/components-helpers.mddocs/docs/Components/components-logic.mddocs/docs/Components/components-custom-components.mddocs/docs/Components/components-agents.mddocs/docs/Concepts/mcp-server.mddocs/docs/Integrations/Google/integrations-setup-google-cloud-vertex-ai-langflow.mddocs/docs/Components/components-tools.mddocs/docs/Components/components-models.mddocs/docs/Contributing/contributing-components.mddocs/docs/Concepts/concepts-file-management.mddocs/docs/Components/components-data.mddocs/docs/API-Reference/api-build.mddocs/docs/Get-Started/get-started-quickstart.mddocs/docs/Components/components-embedding-models.mddocs/docs/Templates/memory-chatbot.mddocs/docs/Develop/Clients/typescript-client.mddocs/docs/Components/components-vector-stores.md
`docs/docusaurus.config.js`: Site configuration, including navbar, title, and theme settings, must be managed in 'docs/docusaurus.config.js'.
docs/docusaurus.config.js: Site configuration, including navbar, title, and theme settings, must be managed in 'docs/docusaurus.config.js'.
📄 Source: CodeRabbit Inference Engine (.cursor/rules/docs_development.mdc)
List of files the instruction was applied to:
docs/docusaurus.config.js
🧠 Learnings (34)
📓 Common learnings
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docusaurus.config.js : Site configuration, including navbar, title, and theme settings, must be managed in 'docs/docusaurus.config.js'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/sidebars.js : Sidebar navigation must be configured and updated in 'docs/sidebars.js' to reflect the current documentation structure.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: The documentation site is built and served locally using 'yarn build' and 'yarn serve', and is automatically deployed on commit to the main branch.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
docs/docs/Templates/financial-report-parser.md (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
docs/docs/Templates/travel-planning-agent.md (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
docs/docs/Concepts/concepts-overview.md (6)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-23T12:46:42.048Z
Learning: Custom React Flow node types should be implemented as memoized components, using Handle components for connection points and supporting optional icons and labels.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.510Z
Learning: Applies to src/frontend/src/components/**/*FlowGraph.tsx : Use React Flow for flow graph visualization components.
docs/docs/Configuration/configuration-authentication.md (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
docs/docs/Contributing/contributing-github-issues.md (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
docs/docs/API-Reference/api-flows.md (5)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
docs/docs/Deployment/deployment-docker.md (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Before deployment, documentation must be reviewed for accuracy, completeness, clarity, and navigation, including checking for broken links and up-to-date screenshots.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
docs/docs/Support/troubleshooting.md (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
docs/docs/Templates/vector-store-rag.md (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
docs/docs/Templates/basic-prompting.md (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
docs/docs/Concepts/concepts-playground.md (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.464Z
Learning: Edit and test components in the UI first for fast iteration, then save to source
docs/docs/Templates/document-qa.md (10)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/package.json : All dependencies and scripts for the documentation site must be managed in 'docs/package.json'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Before deployment, documentation must be reviewed for accuracy, completeness, clarity, and navigation, including checking for broken links and up-to-date screenshots.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
docs/docs/Templates/blog-writer.md (5)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
docs/docs/Concepts/embedded-chat-widget.md (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Headers in documentation should use sentence case, and formatting should include inline code with backticks, bold for UI elements, and italic for emphasis.
docs/docs/Concepts/concepts-voice-mode.md (10)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/sidebars.js : Sidebar navigation must be configured and updated in 'docs/sidebars.js' to reflect the current documentation structure.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/package.json : All dependencies and scripts for the documentation site must be managed in 'docs/package.json'.
docs/docs/Deployment/deployment-overview.md (10)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Before deployment, documentation must be reviewed for accuracy, completeness, clarity, and navigation, including checking for broken links and up-to-date screenshots.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Documentation must build successfully with 'yarn build' before deployment.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/package.json : All dependencies and scripts for the documentation site must be managed in 'docs/package.json'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/static/img/**/* : Place images and static assets in the 'docs/static/img/' directory and use descriptive alt text for all images.
docs/docs/Concepts/concepts-components.md (9)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.464Z
Learning: Applies to src/backend/base/langflow/components/**/*.py : Add new backend components to the appropriate subdirectory under src/backend/base/langflow/components/
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to src/backend/tests/**/*.py : Inherit from the appropriate ComponentTestBase class ('ComponentTestBase', 'ComponentTestBaseWithClient', or 'ComponentTestBaseWithoutClient') and provide the required fixtures: 'component_class', 'default_kwargs', and 'file_names_mapping' when adding a new component test.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.464Z
Learning: Applies to src/backend/base/langflow/components/**/__init__.py : Update __init__.py with alphabetical imports when adding new components
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: Applies to src/backend/**/components/**/*.py : In your Python component class, set the `icon` attribute to a string matching the frontend icon mapping exactly (case-sensitive).
docs/docs/Templates/sequential-agent.md (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
docs/docs/Integrations/mcp-component-astra.md (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
docs/docs/Get-Started/get-started-installation.md (9)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Before deployment, documentation must be reviewed for accuracy, completeness, clarity, and navigation, including checking for broken links and up-to-date screenshots.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/package.json : All dependencies and scripts for the documentation site must be managed in 'docs/package.json'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
docs/docs/Components/components-helpers.md (10)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Headers in documentation should use sentence case, and formatting should include inline code with backticks, bold for UI elements, and italic for emphasis.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/sidebars.js : Sidebar navigation must be configured and updated in 'docs/sidebars.js' to reflect the current documentation structure.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Sidebar and navigation should be kept current to ensure users can easily find all documentation sections and cross-references.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
docs/docs/Components/components-logic.md (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.510Z
Learning: Applies to src/frontend/src/components/**/*FlowGraph.tsx : Use React Flow for flow graph visualization components.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-23T12:46:42.048Z
Learning: Custom React Flow node types should be implemented as memoized components, using Handle components for connection points and supporting optional icons and labels.
docs/docs/Integrations/Google/integrations-setup-google-cloud-vertex-ai-langflow.md (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
docs/docs/Components/components-models.md (6)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
docs/docs/Contributing/contributing-components.md (10)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,src/frontend/**/*.test.{ts,tsx,js,jsx},src/frontend/**/*.spec.{ts,tsx,js,jsx},tests/**/*.py} : Create comprehensive unit tests for all new components.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to src/backend/tests/**/*.py : Inherit from the appropriate ComponentTestBase class ('ComponentTestBase', 'ComponentTestBaseWithClient', or 'ComponentTestBaseWithoutClient') and provide the required fixtures: 'component_class', 'default_kwargs', and 'file_names_mapping' when adding a new component test.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.464Z
Learning: Applies to src/backend/tests/unit/components/**/*.py : Create comprehensive unit tests for all new components
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.md,tests/**/*.md} : If unit tests are incomplete, create a Markdown file with manual testing steps in the same directory as the unit tests, using the same filename as the component but with a '.md' extension.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.464Z
Learning: Applies to src/backend/tests/unit/components/**/*.py : Use ComponentTestBaseWithClient or ComponentTestBaseWithoutClient as base classes for component unit tests
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,src/frontend/**/*.test.{ts,tsx,js,jsx},src/frontend/**/*.spec.{ts,tsx,js,jsx},tests/**/*.py} : Complex test setups should be commented, and mock usage should be documented within the test code.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.464Z
Learning: Applies to src/backend/tests/unit/components/**/*.py : Mirror the component directory structure in unit tests under src/backend/tests/unit/components/
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,src/frontend/**/*.test.{ts,tsx,js,jsx},src/frontend/**/*.spec.{ts,tsx,js,jsx},tests/**/*.py} : Test component initialization and configuration.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.510Z
Learning: All changes must be tested in both light and dark mode before committing.
docs/docs/Components/components-data.md (10)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/sidebars.js : Sidebar navigation must be configured and updated in 'docs/sidebars.js' to reflect the current documentation structure.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/package.json : All dependencies and scripts for the documentation site must be managed in 'docs/package.json'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Headers in documentation should use sentence case, and formatting should include inline code with backticks, bold for UI elements, and italic for emphasis.
docs/docs/Get-Started/get-started-quickstart.md (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test Langflow's REST API endpoints using the async 'client' fixture and assert correct status codes and response structure.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
docs/docs/Components/components-embedding-models.md (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
docs/docs/Templates/memory-chatbot.md (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.849Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test Langflow's 'Message' objects and chat functionality by asserting correct properties and structure.
docs/docusaurus.config.js (7)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/sidebars.js : Sidebar navigation must be configured and updated in 'docs/sidebars.js' to reflect the current documentation structure.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docusaurus.config.js : Site configuration, including navbar, title, and theme settings, must be managed in 'docs/docusaurus.config.js'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation 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.
docs/src/theme/Navbar.js (7)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docusaurus.config.js : Site configuration, including navbar, title, and theme settings, must be managed in 'docs/docusaurus.config.js'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: Custom SVG icon components in React should always support both light and dark mode by accepting an 'isdark' prop and adjusting colors accordingly.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: Applies to src/frontend/src/icons/*/*.jsx : Always support both light and dark mode for custom icons by using the `isdark` prop in your SVG component.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-23T12:46:42.048Z
Learning: Dark mode support should be implemented using a dedicated Zustand store (e.g., useDarkStore), and toggled via a custom hook (e.g., useDarkMode) that exposes isDark and toggle.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.510Z
Learning: Applies to src/frontend/src/{components,hooks}/**/*.{ts,tsx} : Implement dark mode support in components and hooks where needed.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: Export custom icon components in React using React.forwardRef to ensure proper ref forwarding and compatibility with parent components.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: Applies to src/frontend/src/icons/*/* : Create a new directory for your icon in `src/frontend/src/icons/YourIconName/` and add your SVG as a React component (e.g., `YourIconName.jsx`) that uses the `isdark` prop to support both light and dark mode.
docs/src/components/CustomIcon/index.tsx (10)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: Applies to src/frontend/src/icons/*/* : Create a new directory for your icon in `src/frontend/src/icons/YourIconName/` and add your SVG as a React component (e.g., `YourIconName.jsx`) that uses the `isdark` prop to support both light and dark mode.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: Applies to src/frontend/src/icons/*/index.tsx : Create an `index.tsx` in your icon directory that exports your icon using `forwardRef` and passes the `isdark` prop.
Learnt from: dolfim-ibm
PR: langflow-ai/langflow#8394
File: src/frontend/src/icons/Docling/index.tsx:4-6
Timestamp: 2025-06-16T11:14:04.200Z
Learning: The Langflow codebase consistently uses `React.PropsWithChildren<{}>` as the prop type for all icon components using forwardRef, rather than `React.SVGProps<SVGSVGElement>`. This is an established pattern across hundreds of icon files in src/frontend/src/icons/.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.510Z
Learning: Applies to src/frontend/src/icons/**/*.{ts,tsx,js,jsx} : Use Lucide React for icons in frontend components.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: Export custom icon components in React using React.forwardRef to ensure proper ref forwarding and compatibility with parent components.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: Applies to src/frontend/src/icons/*/*.jsx : Always support both light and dark mode for custom icons by using the `isdark` prop in your SVG component.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: Custom SVG icon components in React should always support both light and dark mode by accepting an 'isdark' prop and adjusting colors accordingly.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.846Z
Learning: Applies to src/frontend/src/icons/lazyIconImports.ts : Add your icon to the `lazyIconsMapping` object in `src/frontend/src/icons/lazyIconImports.ts` with a key that matches the backend icon string exactly.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: If a custom icon does not exist for a component, use a generic lucide icon as a fallback and request a new custom icon if needed.
docs/docs/Develop/Clients/typescript-client.md (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Applies to docs/docs/api-reference/**/*.{md,mdx} : API documentation pages must follow the provided template, including sections for Endpoint, Request, Response, and Example.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.682Z
Learning: Internal links in documentation must be functional and tested.
🧬 Code Graph Analysis (1)
docs/src/components/icon/index.tsx (2)
docs/src/components/CustomIcon/index.tsx (1)
CustomIcon(66-69)src/backend/base/langflow/base/astra_assistants/util.py (1)
name(147-151)
🪛 LanguageTool
docs/docs/Templates/financial-report-parser.md
[misspelling] ~10-~10: This word is normally spelled as one.
Context: ...xample, the Chat Input component is pre-loaded with a sample financial report to demon...
(EN_COMPOUNDS_PRE_LOADED)
docs/docs/Support/troubleshooting.md
[uncategorized] ~143-~143: The grammatical number of this noun doesn’t look right. Consider replacing it.
Context: ...g-mcp-server) ## Custom components and integrations issues For troubleshooting advice for ...
(AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER)
docs/docs/Contributing/contributing-community.md
[grammar] ~35-~35: The word ‘help’ is a conjunction. In formal texts, use “to”.
Context: ...ry. For more information, see [Get help and request enhancements](/docs/contributin...
(HELP_AND_VB)
docs/docs/API-Reference/api-projects.md
[uncategorized] ~77-~77: A punctuation mark might be missing here.
Context: ..._listandflows_list values from the [/all`](/docs/api-reference-api-examples#...
(AI_EN_LECTOR_MISSING_PUNCTUATION)
docs/docs/API-Reference/api-reference-api-examples.md
[style] ~162-~162: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...I to upload files. - Use the Langflow API to [get flow logs](/do...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
docs/docs/Integrations/Nvidia/integrations-nvidia-ingest.md
[uncategorized] ~88-~88: Possible missing comma found.
Context: ...ta](/docs/concepts-objects#data-object) objects where each object contains: - text: T...
(AI_HYDRA_LEO_MISSING_COMMA)
docs/docs/Deployment/deployment-overview.md
[style] ~20-~20: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ment for creating and testing flows. * [Langflow runtime](/docs/deployment-kubernetes-pr...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
docs/docs/Templates/sequential-agent.md
[grammar] ~54-~54: This noun or verb “problem-solving” is spelled with a hyphen.
Context: ...our own multi-agent flow, see Create a problem solving agent.
(PROBLEM_SOLVE_HYPHEN)
docs/docs/API-Reference/api-files.md
[style] ~275-~275: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...low, send it to the File component. To retrieve the File component's full ...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
docs/docs/Components/mcp-client.md
[style] ~75-~75: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...e from the targeted Langflow server. 2. In the [component's header menu](/docs/con...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
docs/docs/Components/components-memories.md
[formatting] ~10-~10: If the ‘because’ clause is essential to the meaning, do not use a comma before the clause.
Context: ...re distinct from vector store components, because they are built specifically for storing...
(COMMA_BEFORE_BECAUSE)
docs/docs/Components/components-agents.md
[uncategorized] ~24-~24: Possible missing comma found.
Context: ...ow-simple-agent.png) For a multi-agent example see [Create a flow with an agent](/docs...
(AI_HYDRA_LEO_MISSING_COMMA)
docs/docs/Components/components-models.md
[uncategorized] ~277-~277: Possible missing comma found.
Context: ...urity-tokens) to authenticate. In this example based on the [Basic prompting flow](/do...
(AI_HYDRA_LEO_MISSING_COMMA)
docs/docs/Contributing/contributing-components.md
[uncategorized] ~49-~49: Loose punctuation mark.
Context: ...to-the-frontend-folder). * priority: An optional integer to control display ...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~50-~50: Loose punctuation mark.
Context: ... Lower numbers appear first. * name: An optional internal identifier that de...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~50-~50: You might be missing the article “the” here.
Context: ...al internal identifier that defaults to class name. 4. Define the component's interf...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
🪛 markdownlint-cli2 (0.17.2)
docs/docs/Support/troubleshooting.md
23-23: Images should have alternate text (alt text)
(MD045, no-alt-text)
docs/docs/Concepts/concepts-playground.md
94-94: Unordered list style
Expected: asterisk; Actual: dash
(MD004, ul-style)
docs/docs/API-Reference/api-reference-api-examples.md
51-51: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
96-96: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
docs/docs/Components/components-processing.md
22-22: Images should have alternate text (alt text)
(MD045, no-alt-text)
176-176: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
675-675: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
747-747: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
🔇 Additional comments (92)
docs/docs/Templates/basic-prompting.md (1)
17-18: Internal link prefix looks good.The added
/docsprefix aligns with the new routing convention.docs/docs/API-Reference/api-monitor.md (1)
675-678: Link update acknowledged.
/docs/session-idmatches the new docs location.docs/docs/Concepts/concepts-objects.md (1)
208-211: Updated link path is correct.No further issues spotted.
docs/docs/Templates/travel-planning-agent.md (1)
18-19: Link prefix conforms to new structure.Great catch updating the prerequisite URL.
docs/docs/Deployment/deployment-docker.md (1)
146-146: Updated link correctly adopts the new/docsprefixThis brings the reference in line with the site-wide routing convention and should render properly once deployed. No follow-up needed.
docs/docs/Integrations/Arize/integrations-arize.md (1)
70-70: Internal link now conforms to the standardized docs pathThe switch to
/docs/simple-agentis consistent with other internal links and should resolve without issues.docs/docs/Integrations/Notion/notion-agent-conversational.md (1)
12-12: Link prefix corrected—looks goodUsing
/docs/integrations/notion/setupaligns with the new link schema.docs/docs/Integrations/Notion/notion-agent-meeting-notes.md (1)
11-11: Consistent/docsprefix appliedThe prerequisite link now follows the unified internal-link format.
docs/docs/Integrations/Nvidia/integrations-nvidia-nim-wsl2.md (1)
25-25: Documentation link updated to new base path
/docs/get-started-quickstartadheres to the revised routing convention.docs/docs/Templates/vector-store-rag.md (1)
22-22: Internal link now complies with new/docsroutingLink update aligns with the site-wide URL scheme change—no further action needed.
docs/docs/Develop/session-id.md (1)
36-36: Link prefix corrected to/docsChange resolves the old broken anchor path; looks good.
docs/docs/Templates/blog-writer.md (1)
14-14: Prerequisite link updated correctlyMatches the new doc structure; nothing else required.
docs/docs/Integrations/Cleanlab/integrations-cleanlab.md (1)
138-138: RAG template link fixedRefers to the right page under the new hierarchy.
docs/docs/Configuration/configuration-global-variables.md (1)
212-212: Environment-variables reference path correctedUpdate follows the standardized
/docsprefix; good to merge.docs/docs/Contributing/contributing-github-issues.md (2)
6-6: Internal link update looks correct — double-check for/docs/docsduplication.If
routeBasePathindocusaurus.config.jsis already/docs, prepending/docshere will produce/docs/contributing-community, which is fine.
However, if the site root is also/docs, links will effectively become/docs/docs/.... Please verify locally.
24-24: Same link-prefix concern as above.Confirm that
/docs/contributing-communityresolves and does not duplicate the base path.docs/docs/Concepts/concepts-playground.md (1)
32-32: Link path LGTM.
/docs/components-memoriesresolves correctly under the new route structure.docs/docs/Develop/develop-application.md (13)
9-9: Link prefix looks right — verify locally.Ensure
/docs/deployment-dockerloads after the routeBasePath change.
28-28: Good catch on environment-variables link.Path appears valid.
38-38: Dependency install link verified.No issues spotted.
50-50: Environment-variables link confirmed.All good.
61-63: Memory and authentication links OK.Both slugs resolve; no action needed.
69-69: Flows link LGTM.Resolves under new structure.
106-106: Logging link LGTM.No issues.
111-111: Docker link OK.Path verified.
123-123: Docker-hub reference looks fine.No changes required.
139-139: Session-ID link OK.Resolves correctly.
155-155: Webhook link LGTM.Confirmed.
159-159: /run-endpoint anchor works — verify case-sensitive servers.Docusaurus converts headers to lowercase-kebab by default; make sure
#run-flowmatches final slug.
163-165: Kubernetes docs links OK.Both paths are correct.
docs/docs/Deployment/deployment-kubernetes-prod.md (1)
36-36: Updated Docker link checks out.Path/anchor combination resolves; nothing further.
docs/docs/Templates/financial-report-parser.md (1)
40-40: LGTM – link prefix fix is correct.
No further action needed here.docs/docs/Agents/agents-tools.md (1)
15-15: LGTM – link correction looks good.docs/docs/Concepts/concepts-publish.md (2)
67-67: LGTM – link prefix fix is correct.
81-81: LGTM – link prefix fix is correct.docs/docs/Concepts/embedded-chat-widget.md (1)
10-10: Internal-link prefix looks correct – good catch.All three URLs now resolve under
/docs/..., matching the updated base path.
No further action needed.Also applies to: 19-19, 62-62
docs/docs/Templates/document-qa.md (1)
29-29: Updated link LGTM.Link now points to
/docs/concepts-file-managementand matches the new structure.docs/docs/Agents/agents.md (1)
10-11: Good fix on component link.
/docs/components-agents#agent-componentresolves correctly.docs/docs/Concepts/concepts-overview.md (3)
18-19: Double-check new quick-start link
/docs/get-started-quickstartlooks out of line with the usualGet-Started/quickstartpattern used elsewhere.
Please verify that the page actually resolves after the router change.
68-77: Verify newly prefixed slugs existThe added links
/docs/concepts-playgroundand/docs/concepts-publishmust exist after the site build; otherwise they will 404.
Runyarn build && yarn servelocally or CI link checker to confirm.
121-122: Minor: confirm “Manage files” pathSame as above—ensure
/docs/concepts-file-managementis present; earlier files sometimes lived under/Concepts/concepts-file-management.md.docs/docs/Integrations/Composio/integrations-composio.md (1)
22-23: Confirm “configuration-global-variables” routeBoth updated links rely on
/docs/configuration-global-variables. Make sure that file was moved accordingly in this PR; otherwise these two references will break.Also applies to: 38-39
docs/docs/Deployment/deployment-overview.md (1)
13-14: Link-existence sweepMultiple freshly prefixed links (
/docs/deployment-docker,/docs/deployment-kubernetes-dev,/docs/deployment-kubernetes-prod) were introduced. Please run the docs link checker to guarantee none of them 404 after build.Also applies to: 19-24, 36-37, 42-43
docs/docs/API-Reference/api-flows.md (1)
11-12: API reference links – verify anchors
/docs/api-flows-run/docs/concepts-flows#langflow-json-file-contents/docs/api-projects#read-projectsEnsure each target file contains the specified anchor IDs; otherwise in-page navigation will fail.
Also applies to: 264-266, 295-299
docs/docs/Integrations/Google/integrations-setup-google-cloud-vertex-ai-langflow.md (1)
6-6: Link update looks correct
/docs/components-embedding-models#vertexai-embeddings&/docs/components-models#vertexaimatch the new docs base path—good catch.
No further action required.docs/docs/Configuration/configuration-api-keys.md (2)
77-77: LGTM on link correctionThe
/docs/configuration-authentication#langflow_secret_keytarget aligns with the new routing scheme.
116-116: LGTM on link correction
/docs/configuration-global-variablespath is accurate.docs/docs/Templates/simple-agent.md (2)
6-6: Link path approved
/docs/agentscorrectly references the Agent component page after the restructure.
15-15: Prerequisite link confirmed
/docs/get-started-installationreflects the new docs base path.docs/docs/Develop/webhook.md (1)
13-14: Updated links verified
/docs/components-processing#parserand following internal links align with the new structure.docs/docs/Support/troubleshooting.md (5)
14-15: Link corrections look good
/docs/components-bundle-componentsand/docs/concepts-components#component-menusresolve correctly under the new docs prefix.
45-45: Verified installation link
/docs/get-started-installation#install-and-run-the-langflow-oss-python-packageis accurate after the move.
140-148: Anchor targets validatedMCP troubleshooting links now correctly point to
/docs/mcp-server#….
No action required.
147-148: Link and capitalization approved
/docs/components-custom-components#error-handling-and-loggingis valid, and terminology follows the style guide.
151-152: GitHub references verifiedLinks to contributing pages are now under
/docs, matching the new routing.docs/docs/Develop/develop-overview.md (1)
8-19: Links look good – no further issuesAll updated URLs correctly use the new
/docs/prefix and the surrounding text follows the style guide.docs/docs/API-Reference/api-flows-run.md (1)
194-195: Verify Webhook link target
/docs/components-data#webhookassumes an anchor namedwebhookexists in Components → Data. Please confirm the anchor exists; otherwise readers will land at the top of the page.docs/docs/Components/mcp-client.md (1)
14-15: All updated links look correctAll newly prefixed
/docs/...links resolve to the expected slugs and anchors, so navigation should work after the restructuring.Also applies to: 18-19, 24-24, 34-35, 48-50, 66-66, 75-76, 98-99
docs/docs/Concepts/concepts-components.md (1)
19-20: Links correctly updatedBoth internal links now include the
/docsprefix and point to valid targets. No further action needed.Also applies to: 126-127
docs/docs/Concepts/concepts-voice-mode.md (1)
22-23: Verify destination slug for “Simple agent” linkThe link now points to
/docs/simple-agent, but the actual doc slug is often nested (e.g./docs/getting-started-simple-agent). Please double-check the real path or the link will 404.docs/docs/Components/components-models.md (1)
548-551: Broken internal link: missing/docsprefix-…custom model for an [Agent](/docs/components-agents) component. +…custom model for an [Agent](/docs/components-agents) component.(If this link intentionally pointed to
/docs, ignore. Otherwise make sure every internal path is aligned.)docs/docs/Components/components-helpers.md (1)
16-18: Internal link prefix looks correctThe
/docs/...prefix brings the links in line with the new routing. No other issues spotted.Also applies to: 24-24
docs/docs/API-Reference/api-files.md (1)
67-68: Link-prefix updates LGTMAll modified links now use the
/docsbase path and resolve correctly – nice catch.Also applies to: 90-91, 191-193, 243-248
docs/docs/Contributing/contributing-components.md (1)
48-48: Link fixes acknowledgedThe new
/docs/...paths are correct.Also applies to: 55-55, 128-128, 172-172
docs/docs/Components/components-embedding-models.md (1)
72-76: Updated anchors look goodThe new prefixed links resolve and the anchors match existing headings.
Also applies to: 283-284, 428-428
docs/docs/Components/components-processing.md (1)
12-13: Bulk link-prefix corrections verifiedAll changed references now point to
/docs/concepts-objects...or the correct prefixed component pages. No broken anchors detected.Also applies to: 22-23, 107-111, 156-158, 176-177, 196-199, 516-517, 566-577, 662-663, 675-676, 747-748, 883-884, 899-900
docs/docs/Components/components-custom-components.md (2)
179-180: Link target looks suspicious – verify path
/docs/environment-variables#LANGFLOW_COMPONENTS_PATHmay not exist; current structure usesconfiguration-global-variables.md.
559-560: Broken link risk – ensure new path exists.
/docs/contributing-componentsmust resolve after the restructure.docs/docs/Get-Started/get-started-quickstart.md (1)
61-62: Confirm link correctness –/docs/deployment-overviewmust exist after move.docs/docs/Concepts/mcp-server.md (2)
93-97: Verify environment-variables linkPath
/docs/environment-variables#LANGFLOW_AUTO_LOGINmay be outdated after docs re-org.
355-356: Double-check “MCP client” & “Astra DB” linksEnsure
/docs/mcp-clientand/docs/mcp-component-astraexist.docs/docs/Concepts/concepts-file-management.md (1)
37-45: Internal links now point to correct/docspath – looks good
All three modified links resolve the earlier broken navigation after the routeBase change.docs/docs/Components/components-logic.md (4)
12-15: Link prefix updated correctly
Loop component reference now matches new routing scheme.
150-151: Consistent object anchor retained
TheDataobject anchor is still present after the path change – nice catch.
235-241: Run-flow references fixed
Both the component and the Simple Agent page links are updated; navigation will work again.
326-351: Deprecation notice link corrected
Deprecated component docs now correctly direct users to the replacement.docs/docs/Components/components-tools.md (3)
22-23: Starter-project link fixed
URL now resolves under the new docs root.
29-29: Anchor link updated – good
The “Make any component a tool” section link is working again.
312-320: MCP links corrected
Both forward and replacement references render properly after the path change.docs/docs/API-Reference/api-build.md (3)
13-16: Correct endpoint guidance
Switching the flow-trigger link to/docs/api-flows-runfixes the broken reference.
107-109: Component-ID anchor links OK
The two parameter-table references now match the new docs root.
163-165: See-also links updated
Vertex-monitoring and Session-ID docs now resolve.docs/docs/Components/components-data.md (5)
112-118: File-management link verified
Path now correct; no further action.
140-143: Anchored links intact
DataFrameandMessageanchors remain accurate after prefix change.
255-258: Output table links fixed
All three object-type links use the correct path/anchor combination.
280-281: Parser link corrected
Processing-component anchor now navigates properly.
303-304: Chat-output link corrected
I/O-component reference resolves under/docs.docs/docusaurus.config.js (2)
18-18: LGTM: Appropriate setting for documentation restructuring.Changing from "throw" to "warn" for broken links is a reasonable approach during documentation restructuring to avoid build failures while maintaining visibility of issues.
137-278: LGTM: Consistent documentation URL restructuring.All redirect paths have been systematically updated to include the
/docsprefix, properly supporting the new documentation structure. The pattern is consistent and complete.docs/src/components/icon/index.tsx (1)
17-19: LGTM: Clean delegation to CustomIcon.The simplified implementation properly delegates to the CustomIcon component and allows passing through additional props with the index signature.
docs/docs/Components/components-vector-stores.md (1)
14-14: LGTM: Systematic documentation link updates.All internal documentation links have been consistently updated to include the
/docsprefix, properly supporting the new documentation URL structure. The changes are systematic and complete.Also applies to: 18-18, 25-25, 28-28, 68-68, 76-76, 84-84, 128-128, 173-173, 249-249, 304-304, 417-417, 449-449, 478-478, 507-507, 560-560, 632-632, 666-666, 694-694, 725-725, 763-763, 793-793, 823-823, 854-854, 883-883, 910-910, 969-969
docs/src/pages/index.tsx (1)
65-74: Ensure CustomIcon mapping contains ‘agents’The runtime will throw if the
CustomIconcomponent doesn’t have the"agents"case wired up. Double-checkdocs/src/components/CustomIcon/index.tsxexposes that name.
| ## Next steps | ||
|
|
||
| To create your own multi-agent flow, see [Create a problem solving agent](/agents). No newline at end of file | ||
| To create your own multi-agent flow, see [Create a problem solving agent](/docs/agents). No newline at end of file |
Contributor
There was a problem hiding this comment.
Hyphenate compound modifier “problem-solving”.
-To create your own multi-agent flow, see [Create a problem solving agent](/docs/agents).
+To create your own multi-agent flow, see [Create a problem-solving agent](/docs/agents).📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| To create your own multi-agent flow, see [Create a problem solving agent](/docs/agents). | |
| To create your own multi-agent flow, see [Create a problem-solving agent](/docs/agents). |
🧰 Tools
🪛 LanguageTool
[grammar] ~54-~54: This noun or verb “problem-solving” is spelled with a hyphen.
Context: ...our own multi-agent flow, see Create a problem solving agent.
(PROBLEM_SOLVE_HYPHEN)
🤖 Prompt for AI Agents
In docs/docs/Templates/sequential-agent.md at line 54, the phrase "problem
solving agent" should use a hyphen to form the compound modifier
"problem-solving agent." Update the text to include the hyphen between "problem"
and "solving" to correctly hyphenate the compound adjective.
Comment on lines
37
to
38
| To allow agents to use tools from MCP servers, use the [**MCP connection** component](/docs/components-tools#mcp-connection). | ||
| ::: |
Contributor
There was a problem hiding this comment.
One lingering root-level link breaks navigation.
Line 42 (outside the diff) still links to /, whereas surrounding links were updated.
Replace with the correct docs path:
-For more information, see [Configure tools for agents](/)
+For more information, see [Configure tools for agents](/docs/agents-tools)Also verify the two other updated links – they look correct.
Also applies to: 64-65, 91-91
🤖 Prompt for AI Agents
In docs/docs/Agents/agents.md around lines 37-38 and also at lines 64-65 and 91,
update the root-level link that currently points to '/' to use the correct docs
path consistent with the surrounding links. Verify and correct these links to
ensure they navigate properly within the documentation site.
| import TOCInline from '@theme/TOCInline'; | ||
|
|
||
| Langflow integrates with [Google OAuth](https://developers.google.com/identity/protocols/oauth2) for authenticating the [Gmail loader](/components-data#gmail-loader), [Google Drive loader](components-data#google-drive-loader), and [Google Drive Search](/components-data#google-drive-search) components. | ||
| Langflow integrates with [Google OAuth](https://developers.google.com/identity/protocols/oauth2) for authenticating the [Gmail loader](/docs/components-data#gmail-loader), [Google Drive loader](components-data#google-drive-loader), and [Google Drive Search](/docs/components-data#google-drive-search) components. |
Contributor
There was a problem hiding this comment.
Broken internal link – missing /docs prefix
The Google Drive loader link still lacks the /docs prefix introduced by the new routing scheme, so it 404s.
-Langflow integrates with [Google OAuth](https://developers.google.com/identity/protocols/oauth2) for authenticating the [Gmail loader](/docs/components-data#gmail-loader), [Google Drive loader](components-data#google-drive-loader), and [Google Drive Search](/docs/components-data#google-drive-search) components.
+Langflow integrates with [Google OAuth](https://developers.google.com/identity/protocols/oauth2) for authenticating the [Gmail loader](/docs/components-data#gmail-loader), [Google Drive loader](/docs/components-data#google-drive-loader), and [Google Drive Search](/docs/components-data#google-drive-search) components.Please update to keep navigation consistent and functional.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| Langflow integrates with [Google OAuth](https://developers.google.com/identity/protocols/oauth2) for authenticating the [Gmail loader](/docs/components-data#gmail-loader), [Google Drive loader](components-data#google-drive-loader), and [Google Drive Search](/docs/components-data#google-drive-search) components. | |
| Langflow integrates with [Google OAuth](https://developers.google.com/identity/protocols/oauth2) for authenticating the [Gmail loader](/docs/components-data#gmail-loader), [Google Drive loader](/docs/components-data#google-drive-loader), and [Google Drive Search](/docs/components-data#google-drive-search) components. |
🤖 Prompt for AI Agents
In docs/docs/Integrations/Google/integrations-setup-google-oauth-langflow.md at
line 8, the internal link to the Google Drive loader is missing the /docs
prefix, causing a 404 error. Update the link URL to include the /docs prefix so
it reads /docs/components-data#google-drive-loader to ensure the link navigates
correctly.
| For an example of using local chat memory, see the [Memory chatbot](/memory-chatbot) starter flow. | ||
| For an example of using local chat memory, see the [Memory chatbot](/docs/memory-chatbot) starter flow. | ||
|
|
||
| To store or retrieve chat messages from external memory, connect the **External memory** port of the **Message store** or **Message history** component to a **Memory** component, like the [Astra DB chat memory](components-memories#astradbchatmemory-component) component. An example flow looks like this: |
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion
Missing /docs prefix in internal link
All other internal links were updated, but the reference to the Astra DB chat memory component is still missing the new /docs prefix, so the link will break after the routing change.
-… to a **Memory** component, like the [Astra DB chat memory](components-memories#astradbchatmemory-component) component.
+… to a **Memory** component, like the [Astra DB chat memory](/docs/components-memories#astradbchatmemory-component) component.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| To store or retrieve chat messages from external memory, connect the **External memory** port of the **Message store** or **Message history** component to a **Memory** component, like the [Astra DB chat memory](components-memories#astradbchatmemory-component) component. An example flow looks like this: | |
| To store or retrieve chat messages from external memory, connect the **External memory** port of the **Message store** or **Message history** component to a **Memory** component, like the [Astra DB chat memory](/docs/components-memories#astradbchatmemory-component) component. An example flow looks like this: |
🤖 Prompt for AI Agents
In docs/docs/Develop/memory.md at line 52, the internal link to the Astra DB
chat memory component is missing the required /docs prefix. Update the link URL
by adding the /docs prefix before
components-memories#astradbchatmemory-component to ensure the link works
correctly after the routing change.
Comment on lines
91
to
93
| - You can find flow IDs on the [Publish pane](/docs/concepts-publish), in a flow's URL, and with [`GET /flows`](/docs/api-flows#read-flows). | ||
| - You can retrieve project IDs with `GET /projects`(/api-projects#read-projects). | ||
| ::: |
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion
Formatting & link issues in bullet list
- The second bullet is missing the
/docsprefix. - The markdown back-tick closes before the link, so the link isn’t rendered.
-- You can retrieve project IDs with `GET /projects`(/api-projects#read-projects).
+- You can retrieve project IDs with [`GET /projects`](/docs/api-projects#read-projects).📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| - You can find flow IDs on the [Publish pane](/docs/concepts-publish), in a flow's URL, and with [`GET /flows`](/docs/api-flows#read-flows). | |
| - You can retrieve project IDs with `GET /projects`(/api-projects#read-projects). | |
| ::: | |
| - You can find flow IDs on the [Publish pane](/docs/concepts-publish), in a flow's URL, and with [`GET /flows`](/docs/api-flows#read-flows). | |
| - You can retrieve project IDs with [`GET /projects`](/docs/api-projects#read-projects). | |
| ::: |
🤖 Prompt for AI Agents
In docs/docs/API-Reference/api-reference-api-examples.md around lines 91 to 93,
fix the second bullet point by adding the missing /docs prefix to the URL path
and ensure the markdown back-tick correctly surrounds only the HTTP method and
endpoint, not the link, so the link renders properly. Adjust the syntax to have
the back-ticks around `GET /projects` and the link in parentheses immediately
after.
Comment on lines
+30
to
+38
| const socialLinks = [ | ||
| { | ||
| href: "https://github.com/langflow-ai/langflow", | ||
| icon: "github", | ||
| label: "GitHub", | ||
| }, | ||
| { href: "https://x.com/langflow_ai", icon: "x", label: "X" }, | ||
| { href: "https://discord.gg/langflow", icon: "discord", label: "Discord" }, | ||
| ]; |
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion
Use configuration values instead of hardcoding social links.
The social links are hardcoded but should be retrieved from the Docusaurus configuration to maintain consistency and avoid duplication. Also, the Discord link doesn't match the one in docusaurus.config.js (this uses discord.gg/langflow while config has discord.gg/EqksyE2EX9).
- // Social links (reuse from config or hardcode for now)
- const socialLinks = [
- {
- href: "https://github.com/langflow-ai/langflow",
- icon: "github",
- label: "GitHub",
- },
- { href: "https://x.com/langflow_ai", icon: "x", label: "X" },
- { href: "https://discord.gg/langflow", icon: "discord", label: "Discord" },
- ];
+ // Extract social links from config
+ const socialLinks = [
+ {
+ href: "https://github.com/langflow-ai/langflow",
+ icon: "github",
+ label: "GitHub",
+ },
+ { href: "https://twitter.com/langflow_ai", icon: "x", label: "X" },
+ { href: "https://discord.gg/EqksyE2EX9", icon: "discord", label: "Discord" },
+ ];Committable suggestion skipped: line range outside the PR's diff.
🤖 Prompt for AI Agents
In docs/src/theme/Navbar.js around lines 30 to 38, the social links are
hardcoded and the Discord URL does not match the one in docusaurus.config.js.
Replace the hardcoded socialLinks array by retrieving the social links from the
Docusaurus site configuration instead, ensuring the Discord link and others are
consistent with the config file to avoid duplication and maintain uniformity.
Comment on lines
+3
to
+7
| interface IconProps { | ||
| name: string; | ||
| size?: number; | ||
| className?: string; | ||
| } |
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion
Add dark mode support and forwardRef for icon consistency.
Based on the retrieved learnings, custom icon components should support dark mode with an isDark prop and use React.forwardRef for proper ref forwarding.
interface IconProps {
name: string;
size?: number;
className?: string;
+ isDark?: boolean;
}-export default function CustomIcon({ name, size = 24, className }: IconProps) {
+const CustomIcon = React.forwardRef<SVGSVGElement, IconProps>(
+ ({ name, size = 24, className, isDark }, ref) => {
const icon = customIcons[name as keyof typeof customIcons];
- return icon ? icon(size, className) : null;
-}
+ return icon ? icon(size, className, isDark, ref) : null;
+});
+
+CustomIcon.displayName = "CustomIcon";
+export default CustomIcon;You'll also need to update the icon functions to accept the isDark and ref parameters and apply appropriate color changes based on the theme.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| interface IconProps { | |
| name: string; | |
| size?: number; | |
| className?: string; | |
| } | |
| // docs/src/components/CustomIcon/index.tsx | |
| import React from "react"; | |
| import customIcons from "./customIcons"; | |
| interface IconProps { | |
| name: string; | |
| size?: number; | |
| className?: string; | |
| isDark?: boolean; | |
| } | |
| const CustomIcon = React.forwardRef<SVGSVGElement, IconProps>( | |
| ({ name, size = 24, className, isDark }, ref) => { | |
| const IconComponent = customIcons[name as keyof typeof customIcons]; | |
| return IconComponent | |
| ? IconComponent({ size, className, isDark, ref }) | |
| : null; | |
| } | |
| ); | |
| CustomIcon.displayName = "CustomIcon"; | |
| export default CustomIcon; |
🤖 Prompt for AI Agents
In docs/src/components/CustomIcon/index.tsx around lines 3 to 7, the IconProps
interface and icon components lack dark mode support and ref forwarding. Add an
optional boolean isDark prop to IconProps for theme control. Refactor the icon
components to use React.forwardRef, accepting ref and isDark parameters, and
apply conditional styling or color changes based on isDark to support dark mode.
Comment on lines
+90
to
+119
| <Link to={useBaseUrl('/')} className={styles.card}> | ||
| <div className={styles.cardIcon}> | ||
| <BookMarked size={16} strokeWidth={1.25} /> | ||
| </div> | ||
| <div className={styles.cardContent}> | ||
| <div className={styles.cardTitle}>About Langflow</div> | ||
| </div> | ||
| <div className={styles.cardArrow}> | ||
| <ArrowRight size={20} strokeWidth={1.25} /> | ||
| </div> | ||
| </Link> | ||
| <Link to={useBaseUrl('/docs/get-started-installation')} className={styles.card}> | ||
| <div className={styles.cardIcon}> | ||
| <MonitorDown size={16} strokeWidth={1.25} /> | ||
| </div> | ||
| <div className={styles.cardContent}> | ||
| <div className={styles.cardTitle}>Install Langflow</div> | ||
| </div> | ||
| <div className={styles.cardArrow}> | ||
| <ArrowRight size={20} strokeWidth={1.25} /> | ||
| </div> | ||
| </Link> | ||
| <Link to={useBaseUrl('/')} className={styles.card}> | ||
| <div className={styles.cardIcon}> | ||
| <GraduationCap size={16} strokeWidth={1.25} /> | ||
| </div> | ||
| <div className={styles.cardContent}> | ||
| <div className={styles.cardTitle}>Tutorial</div> | ||
| </div> | ||
| <div className={styles.cardArrow}> | ||
| <ArrowRight size={20} strokeWidth={1.25} /> | ||
| </div> | ||
| </Link> |
Contributor
There was a problem hiding this comment.
Self-linking cards likely placeholder – update before merge
Both “About Langflow” and “Tutorial” cards point to /, which reloads the same homepage and breaks the expectation of reaching dedicated docs.
Either wire them to their final paths (e.g. /docs/about & /docs/get-started-tutorial) or comment them out until those pages exist to avoid dead-end navigation.
- <Link to={useBaseUrl('/')} className={styles.card}>
+ <Link to={useBaseUrl('/docs/about')} className={styles.card}>
...
- <Link to={useBaseUrl('/')} className={styles.card}>
+ <Link to={useBaseUrl('/docs/get-started-tutorial')} className={styles.card}>📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| <Link to={useBaseUrl('/')} className={styles.card}> | |
| <div className={styles.cardIcon}> | |
| <BookMarked size={16} strokeWidth={1.25} /> | |
| </div> | |
| <div className={styles.cardContent}> | |
| <div className={styles.cardTitle}>About Langflow</div> | |
| </div> | |
| <div className={styles.cardArrow}> | |
| <ArrowRight size={20} strokeWidth={1.25} /> | |
| </div> | |
| </Link> | |
| <Link to={useBaseUrl('/docs/get-started-installation')} className={styles.card}> | |
| <div className={styles.cardIcon}> | |
| <MonitorDown size={16} strokeWidth={1.25} /> | |
| </div> | |
| <div className={styles.cardContent}> | |
| <div className={styles.cardTitle}>Install Langflow</div> | |
| </div> | |
| <div className={styles.cardArrow}> | |
| <ArrowRight size={20} strokeWidth={1.25} /> | |
| </div> | |
| </Link> | |
| <Link to={useBaseUrl('/')} className={styles.card}> | |
| <div className={styles.cardIcon}> | |
| <GraduationCap size={16} strokeWidth={1.25} /> | |
| </div> | |
| <div className={styles.cardContent}> | |
| <div className={styles.cardTitle}>Tutorial</div> | |
| </div> | |
| <div className={styles.cardArrow}> | |
| <ArrowRight size={20} strokeWidth={1.25} /> | |
| </div> | |
| </Link> | |
| <Link to={useBaseUrl('/docs/about')} className={styles.card}> | |
| <div className={styles.cardIcon}> | |
| <BookMarked size={16} strokeWidth={1.25} /> | |
| </div> | |
| <div className={styles.cardContent}> | |
| <div className={styles.cardTitle}>About Langflow</div> | |
| </div> | |
| <div className={styles.cardArrow}> | |
| <ArrowRight size={20} strokeWidth={1.25} /> | |
| </div> | |
| </Link> | |
| <Link to={useBaseUrl('/docs/get-started-installation')} className={styles.card}> | |
| <div className={styles.cardIcon}> | |
| <MonitorDown size={16} strokeWidth={1.25} /> | |
| </div> | |
| <div className={styles.cardContent}> | |
| <div className={styles.cardTitle}>Install Langflow</div> | |
| </div> | |
| <div className={styles.cardArrow}> | |
| <ArrowRight size={20} strokeWidth={1.25} /> | |
| </div> | |
| </Link> | |
| <Link to={useBaseUrl('/docs/get-started-tutorial')} className={styles.card}> | |
| <div className={styles.cardIcon}> | |
| <GraduationCap size={16} strokeWidth={1.25} /> | |
| </div> | |
| <div className={styles.cardContent}> | |
| <div className={styles.cardTitle}>Tutorial</div> | |
| </div> | |
| <div className={styles.cardArrow}> | |
| <ArrowRight size={20} strokeWidth={1.25} /> | |
| </div> | |
| </Link> |
🤖 Prompt for AI Agents
In docs/src/pages/index.tsx between lines 90 and 122, the "About Langflow" and
"Tutorial" Link components both point to the homepage path '/', causing dead-end
navigation. Update the "About Langflow" link to point to its intended
documentation path such as '/docs/about' and the "Tutorial" link to
'/docs/get-started-tutorial' or comment out these links until their target pages
are implemented to prevent user confusion.
Comment on lines
113
to
116
| body { | ||
| font-size: 16px; | ||
| padding-top: 56px; /* Account for fixed navbar height */ | ||
| } |
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion
Hard-coded 56 px body padding couples layout to navbar height
If the navbar height ever changes, every page will mis-align. Declare a CSS-custom-property (--lf-navbar-height) and reference it instead.
- padding-top: 56px; /* Account for fixed navbar height */
+ --lf-navbar-height: 56px;
+ padding-top: var(--lf-navbar-height);📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| body { | |
| font-size: 16px; | |
| padding-top: 56px; /* Account for fixed navbar height */ | |
| } | |
| body { | |
| font-size: 16px; | |
| --lf-navbar-height: 56px; | |
| padding-top: var(--lf-navbar-height); | |
| } |
🤖 Prompt for AI Agents
In docs/css/custom.css around lines 113 to 116, the body padding-top is
hard-coded to 56px, which tightly couples the layout to the navbar height.
Define a CSS custom property named --lf-navbar-height with the value 56px, then
update the body's padding-top to use this variable instead of the fixed value.
This makes the layout adaptable if the navbar height changes.
Comment on lines
+490
to
+498
| .lf-navbar-search .navbar__search input { | ||
| width: 100% !important; | ||
| min-width: 500px !important; | ||
| } | ||
|
|
||
| .lf-navbar-search .DocSearch-Button { | ||
| width: 100% !important; | ||
| min-width: 300px !important; | ||
| max-width: 500px !important; |
Contributor
There was a problem hiding this comment.
Fixed 500 px min-width breaks on small laptops
min-width: 500px for the DocSearch input prevents the navbar from fitting on 13'' screens. Let it shrink gracefully:
- min-width: 500px !important;
+ min-width: 0 !important;(The surrounding flex layout already keeps the control usable.)
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| .lf-navbar-search .navbar__search input { | |
| width: 100% !important; | |
| min-width: 500px !important; | |
| } | |
| .lf-navbar-search .DocSearch-Button { | |
| width: 100% !important; | |
| min-width: 300px !important; | |
| max-width: 500px !important; | |
| .lf-navbar-search .navbar__search input { | |
| width: 100% !important; | |
| min-width: 0 !important; | |
| } | |
| .lf-navbar-search .DocSearch-Button { | |
| width: 100% !important; | |
| min-width: 300px !important; | |
| max-width: 500px !important; | |
| } |
🤖 Prompt for AI Agents
In docs/css/custom.css around lines 490 to 498, the min-width of 500px on the
DocSearch input causes layout issues on smaller screens like 13'' laptops.
Remove or reduce the min-width property on the input element to allow it to
shrink gracefully within the flex layout, ensuring the navbar fits properly on
smaller displays.
kurtenj
force-pushed
the
welcome-page-redesign
branch
from
6952ec1 to
708094e
Compare
github-actions
Bot
added
documentation
Contributor
|
Build successful! ✅ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Complete redesign of the Langflow documentation welcome page with React components, responsive design, and improved user experience. This PR includes custom icon system, hero image, extendable use case cards, and polished styling throughout.
Summary by CodeRabbit
New Features
Style
Documentation
/docsprefix for consistency and navigation accuracy.