docs: Remove template pages because templates already include explanatory notes within Langflow#9235
Conversation
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the WalkthroughThis change removes all individual documentation pages for flow templates (such as "Basic Prompting," "Simple Agent," and others), updates all references to these templates throughout the documentation to use plain bold text without markdown links, and consolidates sidebar and redirect configurations to reflect the removal of template-specific docs. The sidebar no longer lists template flows, and redirects send legacy template paths to a general flows concept page. Several documentation sections were also expanded or clarified for improved instructional clarity. Changes
Sequence Diagram(s)No sequence diagrams generated, as the changes are documentation-only and do not introduce or modify control flow. Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Suggested labels
Suggested reviewers
✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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
|
|
Build successful! ✅ |
github-actions
Bot
added
the
documentation
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🔭 Outside diff range comments (5)
docs/docs/Tutorials/chat-with-files.mdx (1)
1-4: Front-matter is missing adescriptionfieldAll docs pages must include at least
titleanddescriptionaccording to the style guide.
Add a short, sentence-case description for SEO and in-product search.--- title: Create a chatbot that can ingest files slug: /chat-with-files +description: Learn how to build a Langflow flow that ingests uploaded files and answers questions about them. ---docs/docs/Tutorials/mcp-tutorial.mdx (1)
1-4: Adddescriptionto front-matterSame issue as other pages—please include a
descriptionline.docs/docs/Tutorials/agent.mdx (1)
1-4: Missingdescriptionin front-matterPlease add a short description.
docs/docs/Integrations/Arize/integrations-arize.mdx (1)
1-4: Front-matter needs adescriptionAdd a descriptive sentence per documentation guidelines.
docs/docs/Agents/agents.mdx (1)
1-4: Adddescriptionto front-matterRequired by docs rules.
🧹 Nitpick comments (20)
docs/docs/Develop/develop-application.mdx (1)
209-214: Add a link now that dedicated template pages are goneWith the individual template docs removed, mentioning the Pokédex template without a pointer may leave readers wondering where to find it.
Consider linking to the generic flows page so the reference is still actionable:-This command runs the **Pokédex** template flow. +This command runs the **Pokédex** template flow (see [/concepts-flows](/concepts-flows) for details about built-in templates).docs/docs/Get-Started/about-langflow.mdx (1)
17-20: Restore discoverability for templatesGood call removing the stale links, but now the sentence drops the reader at a dead end.
Add an inline link to the flows overview so newcomers can still locate the templates:-Langflow includes several pre-built templates that are ready to use or customize to your needs. +Langflow includes several pre-built templates that you can use out of the box or customize to your needs—see [/concepts-flows](/concepts-flows) for the full list.docs/docs/Integrations/mcp-component-astra.mdx (1)
20-22: Optional: keep the template reference actionableSimilar to the other docs, once the dedicated template pages were excised, "Simple Agent template" is no longer clickable.
If you want to preserve a navigation path, link to/concepts-flows:-5. To follow along with this guide, create a flow based on the **Simple Agent** template. +5. To follow along with this guide, create a flow based on the **Simple Agent** template (see [/concepts-flows](/concepts-flows)).docs/docs/Concepts/concepts-voice-mode.mdx (1)
30-35: Mirror the template link removal patternFor consistency with other pages, consider appending a link to the flows overview next to the bold Simple Agent reference so users can still discover the template:
-The following steps use the **Simple Agent** template to demonstrate how to enable voice mode: +The following steps use the **Simple Agent** template (see [/concepts-flows](/concepts-flows)) to demonstrate how to enable voice mode:docs/docs/Components/bundles-huggingface.mdx (1)
64-65: Phrase now diverges from the new “template flow” conventionMost files in this PR re-phrase template references as “XYZ template flow”, but here it still says “Vector Store RAG template”. For consistency and discoverability, consider updating:
-2. For this example, create a flow from the **Vector Store RAG** template. +2. For this example, create a Flow from the **Vector Store RAG** template flow.Capitalizing “Flow” keeps terminology uniform per the style guide.
docs/docs/Components/components-data.mdx (1)
420-422: Align wording with global docs wordingOther files now use “template flow”; this step still says “template”. Recommend:
-1. Create a flow based on the **Basic Prompting** template. +1. Create a Flow based on the **Basic Prompting** template flow.Minor, but it keeps phrasing identical across guides and satisfies the “Flow” capitalization rule.
docs/docs/API-Reference/api-flows-run.mdx (1)
23-25: Capitalize “Flow” for consistencyThe revised sentence is great, but “flow” should be capitalized to match the docs convention:
-The following example runs the **Basic Prompting** template flow with flow parameters passed in the request body. +The following example runs the **Basic Prompting** template Flow with Flow parameters passed in the request body.This also avoids mixing lowercase/uppercase “flow/Flow” in the same sentence.
docs/docs/Concepts/concepts-publish.mdx (1)
140-142: Minor wording tweak for uniformitySame convention issue:
-For example, the following HTML embeds a chat widget for a **Basic Prompting** template flow hosted on a Langflow server deployed on ngrok: +For example, the following HTML embeds a chat widget for a **Basic Prompting** template Flow hosted on a Langflow server deployed on ngrok:Keeps “Flow” capitalized and matches other pages.
docs/docs/Components/components-models.mdx (1)
21-23: Standardize template wordingHere we still say “template”, whereas other docs now say “template flow”. Consider:
-The following example uses the core **Language Model** component and a built-in LLM to create a chatbot flow similar to the **Basic Prompting** template. +The following example uses the core **Language Model** component and a built-in LLM to create a chatbot Flow similar to the **Basic Prompting** template Flow.This brings capitalization and phrasing in line with the rest of the docs.
docs/docs/Components/components-processing.mdx (1)
726-733: Consider restoring a contextual link now that dedicated template pages are gone.With the template docs removed, readers who are unfamiliar with Basic Prompting have no easy path to discover what the template does.
Either:
- Add a short parenthetical “(see Concepts → Flows for an overview of templates)” after the first mention, or
- Inline a one-sentence description of the template.
That preserves discoverability without re-introducing dead links.
docs/docs/API-Reference/api-files.mdx (1)
88-90: Linkless template reference may confuse API readersThe phrase “Basic Prompting template flow” is not self-describing for users reading the API docs in isolation.
Recommend appending a hint or a link to/concepts-flowsso that the flow’s purpose is clear:- The following example runs the **Basic Prompting** template flow + The following example runs the **Basic Prompting** template flow + (see [/concepts-flows](/concepts-flows) for template details)docs/docs/Components/components-io.mdx (1)
120-121: Minor terminology consistencyGuidelines state that “Flow” is capitalised when referring to Langflow entities.
Consider:-* **Basic Prompting** template: Create an LLM-based chat flow +* **Basic Prompting** template: Create an LLM-based chat **Flow**Also think about adding a pointer to
/concepts-flowsfor users who can’t see the removed template page.docs/docs/Concepts/mcp-server.mdx (1)
74-75: Capitalize “Flow” per style guide- For example, assume you create a flow based on the **Document Q&A** template + For example, assume you create a **Flow** based on the **Document Q&A** templateThis keeps terminology consistent with earlier documentation rules.
docs/docs/Tutorials/mcp-tutorial.mdx (1)
80-84: Inconsistent capitalisation of template nameLine 82 reverts to
**Simple agent**(lower-case a).
Use the same capitalisation everywhere for clarity.-2. In your **Simple agent** flow, remove the **URL** … +2. In your **Simple Agent** flow, remove the **URL** …docs/docs/Agents/agents.mdx (1)
33-35: Broken guideline: template name should be bold only onceThe inline example still links to the template docs that were removed.
Since the page no longer exists, keep it plain bold for consistency.-For a prebuilt example, use the **Simple Agent** template or try the … +For a prebuilt example, use the **Simple Agent** template or try the …docs/docs/Components/components-prompts.mdx (1)
33-33: Fix capitalization inconsistency in template name.The template name should be "Basic Prompting" (with capital P) to maintain consistency with other template references throughout the documentation, as specified in the terminology guidelines.
-1. Create a flow based on the **Basic prompting** template. +1. Create a flow based on the **Basic Prompting** template.docs/docs/Components/components-helpers.mdx (2)
77-84: Capitalize “Markdown” and “URL” for terminology consistencyThe style-guide requires sentence-case headers and capitalized technical terms.
Line 82 currently reads “Use markdown to format your answer, properly embedding images and urls.” – “markdown” ➔ “Markdown” and “urls” ➔ “URLs”.- Use markdown to format your answer, properly embedding images and urls. + Use Markdown to format your answer, properly embedding images and URLs.
89-92: Minor repetition – consider tightening explanationLines 89-91 repeat “variables dynamically add fields … so that your flow can receive definitions” twice in very similar wording (first generic, then
{memory}example).
Condensing to a single statement will improve readability.docs/docs/Agents/agents-tools.mdx (1)
28-33: Drop the redundant “additional”“Add an additional agent” is wordy; “add a second agent” is clearer.
-To try this for yourself, add an additional agent to the **Simple Agent** template: +To try this for yourself, add a second **Agent** component to the **Simple Agent** template:docs/docs/Concepts/concepts-flows.mdx (1)
23-27: Smooth bullet alignment – drop colon inside listBecause the list item already contains descriptive text, the colon after “blank flow” is unnecessary and breaks parallel structure with later items.
-* **Create a blank flow**: Select a project, click **New Flow**, and then click **Blank Flow**. +* **Create a blank flow** ‒ select a project, click **New Flow**, and then click **Blank Flow**.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (39)
docs/docs/API-Reference/api-files.mdx(1 hunks)docs/docs/API-Reference/api-flows-run.mdx(1 hunks)docs/docs/Agents/agents-tools.mdx(1 hunks)docs/docs/Agents/agents.mdx(2 hunks)docs/docs/Components/bundles-huggingface.mdx(1 hunks)docs/docs/Components/components-agents.mdx(2 hunks)docs/docs/Components/components-data.mdx(1 hunks)docs/docs/Components/components-helpers.mdx(2 hunks)docs/docs/Components/components-io.mdx(1 hunks)docs/docs/Components/components-models.mdx(1 hunks)docs/docs/Components/components-processing.mdx(1 hunks)docs/docs/Components/components-prompts.mdx(3 hunks)docs/docs/Components/components-vector-stores.mdx(2 hunks)docs/docs/Concepts/concepts-file-management.mdx(1 hunks)docs/docs/Concepts/concepts-flows.mdx(1 hunks)docs/docs/Concepts/concepts-overview.mdx(1 hunks)docs/docs/Concepts/concepts-playground.mdx(1 hunks)docs/docs/Concepts/concepts-publish.mdx(1 hunks)docs/docs/Concepts/concepts-voice-mode.mdx(1 hunks)docs/docs/Concepts/mcp-server.mdx(1 hunks)docs/docs/Develop/develop-application.mdx(1 hunks)docs/docs/Get-Started/about-langflow.mdx(1 hunks)docs/docs/Integrations/Arize/integrations-arize.mdx(1 hunks)docs/docs/Integrations/Cleanlab/integrations-cleanlab.mdx(1 hunks)docs/docs/Integrations/mcp-component-astra.mdx(1 hunks)docs/docs/Templates/basic-prompting.mdx(0 hunks)docs/docs/Templates/blog-writer.mdx(0 hunks)docs/docs/Templates/document-qa.mdx(0 hunks)docs/docs/Templates/financial-report-parser.mdx(0 hunks)docs/docs/Templates/memory-chatbot.mdx(0 hunks)docs/docs/Templates/sequential-agent.mdx(0 hunks)docs/docs/Templates/simple-agent.mdx(0 hunks)docs/docs/Templates/travel-planning-agent.mdx(0 hunks)docs/docs/Templates/vector-store-rag.mdx(0 hunks)docs/docs/Tutorials/agent.mdx(1 hunks)docs/docs/Tutorials/chat-with-files.mdx(1 hunks)docs/docs/Tutorials/mcp-tutorial.mdx(1 hunks)docs/docusaurus.config.js(1 hunks)docs/sidebars.js(0 hunks)
💤 Files with no reviewable changes (10)
- docs/sidebars.js
- docs/docs/Templates/simple-agent.mdx
- docs/docs/Templates/sequential-agent.mdx
- docs/docs/Templates/basic-prompting.mdx
- docs/docs/Templates/memory-chatbot.mdx
- docs/docs/Templates/financial-report-parser.mdx
- docs/docs/Templates/blog-writer.mdx
- docs/docs/Templates/travel-planning-agent.mdx
- docs/docs/Templates/vector-store-rag.mdx
- docs/docs/Templates/document-qa.mdx
🧰 Additional context used
📓 Path-based instructions (2)
docs/docs/**/*.{md,mdx}
📄 CodeRabbit Inference Engine (.cursor/rules/docs_development.mdc)
docs/docs/**/*.{md,mdx}: All documentation content must be written in Markdown or MDX files located under docs/docs/, following the prescribed directory structure for guides, reference, how-to, concepts, and API documentation.
All documentation Markdown and MDX files must begin with a frontmatter block including at least title and description fields.
Use admonitions (:::tip, :::warning, :::danger) in Markdown/MDX files to highlight important information, warnings, or critical issues.
All images referenced in documentation must include descriptive alt text for accessibility.
All code examples included in documentation must be tested and verified to work as shown.
Internal links in documentation must be functional and not broken.
Content must follow the style guide: professional but approachable tone, second person voice, present tense, short paragraphs, sentence case headers, inline code with backticks, bold for UI elements, italic for emphasis, and parallel structure in lists.
Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
Files:
docs/docs/Integrations/mcp-component-astra.mdxdocs/docs/Tutorials/chat-with-files.mdxdocs/docs/API-Reference/api-files.mdxdocs/docs/Components/components-models.mdxdocs/docs/Components/bundles-huggingface.mdxdocs/docs/Concepts/concepts-playground.mdxdocs/docs/Concepts/concepts-publish.mdxdocs/docs/Components/components-io.mdxdocs/docs/Tutorials/agent.mdxdocs/docs/Concepts/mcp-server.mdxdocs/docs/Concepts/concepts-overview.mdxdocs/docs/Components/components-data.mdxdocs/docs/Get-Started/about-langflow.mdxdocs/docs/Tutorials/mcp-tutorial.mdxdocs/docs/Develop/develop-application.mdxdocs/docs/Concepts/concepts-voice-mode.mdxdocs/docs/Components/components-processing.mdxdocs/docs/Agents/agents.mdxdocs/docs/Components/components-agents.mdxdocs/docs/Components/components-prompts.mdxdocs/docs/Concepts/concepts-file-management.mdxdocs/docs/Integrations/Cleanlab/integrations-cleanlab.mdxdocs/docs/Integrations/Arize/integrations-arize.mdxdocs/docs/Components/components-helpers.mdxdocs/docs/Agents/agents-tools.mdxdocs/docs/API-Reference/api-flows-run.mdxdocs/docs/Concepts/concepts-flows.mdxdocs/docs/Components/components-vector-stores.mdx
docs/docusaurus.config.js
📄 CodeRabbit Inference Engine (.cursor/rules/docs_development.mdc)
Site configuration such as title, tagline, URL, and navbar items must be managed in docs/docusaurus.config.js.
Files:
docs/docusaurus.config.js
🧠 Learnings (28)
📓 Common learnings
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
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-07-18T18:26:42.027Z
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-07-18T18:26:42.027Z
Learning: Applies to docs/sidebars.js : Sidebar navigation must be updated in docs/sidebars.js to reflect new or reorganized documentation content.
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.
docs/docs/Integrations/mcp-component-astra.mdx (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Internal links in documentation must be functional and not broken.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : 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-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
docs/docs/Tutorials/chat-with-files.mdx (4)
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-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-07-18T18:25:54.486Z
Learning: Starter project files auto-format after langflow run; these formatting changes can be committed or ignored
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/API-Reference/api-files.mdx (10)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
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: 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-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-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All images referenced in documentation must include descriptive alt text for accessibility.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
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-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be written in Markdown or MDX files located under docs/docs/, following the prescribed directory structure for guides, reference, how-to, concepts, and API documentation.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Internal links in documentation must be functional and not broken.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : 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: Images and screenshots in documentation should have descriptive alt text and filenames, and should highlight relevant UI elements.
docs/docs/Components/components-models.mdx (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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-07-18T18:26:42.027Z
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-playground.mdx (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
docs/docs/Concepts/concepts-publish.mdx (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: 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: deon-sanchez
PR: #9158
File: src/backend/base/langflow/api/v1/mcp_projects.py:404-404
Timestamp: 2025-07-23T21:19:22.567Z
Learning: In langflow MCP projects configuration, prefer using dynamically computed URLs (like the sse_url variable) over hardcoded localhost URLs to ensure compatibility across different deployment environments.
docs/docs/Components/components-io.mdx (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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: 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-07-18T18:26:42.027Z
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/Tutorials/agent.mdx (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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: 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-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/mcp-server.mdx (5)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
Learnt from: deon-sanchez
PR: #9158
File: src/backend/base/langflow/api/v1/mcp_projects.py:404-404
Timestamp: 2025-07-23T21:19:22.567Z
Learning: In langflow MCP projects configuration, prefer using dynamically computed URLs (like the sse_url variable) over hardcoded localhost URLs to ensure compatibility across different deployment environments.
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/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/Concepts/concepts-overview.mdx (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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/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/Components/components-data.mdx (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
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-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Internal links in documentation must be functional and not broken.
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/about-langflow.mdx (6)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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: 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-07-18T18:25:54.486Z
Learning: Starter project files auto-format after langflow run; these formatting changes can be committed or ignored
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : 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/Tutorials/mcp-tutorial.mdx (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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/Develop/develop-application.mdx (5)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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: 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-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-07-18T18:25:54.486Z
Learning: Starter project files auto-format after langflow run; these formatting changes can be committed or ignored
docs/docs/Concepts/concepts-voice-mode.mdx (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : 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/Components/components-processing.mdx (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
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: 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/Agents/agents.mdx (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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: 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/Components/components-agents.mdx (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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/Components/components-prompts.mdx (7)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
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: 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-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : 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-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use admonitions (:::tip, :::warning, :::danger) in Markdown/MDX 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-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Internal links in documentation must be functional and not broken.
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/Concepts/concepts-file-management.mdx (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All images referenced in documentation must include descriptive alt text for accessibility.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/static/img/**/* : Images used in documentation must be stored in docs/static/img/ and referenced with descriptive alt text.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Images and screenshots in documentation should have descriptive alt text and filenames, and should highlight relevant UI elements.
docs/docs/Integrations/Cleanlab/integrations-cleanlab.mdx (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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: Documentation content should be concise, with short paragraphs and parallel structure in lists for better readability.
docs/docs/Integrations/Arize/integrations-arize.mdx (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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: 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-helpers.mdx (3)
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-07-18T18:26:42.027Z
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-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
docs/docs/API-Reference/api-flows-run.mdx (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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: 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-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/Concepts/concepts-flows.mdx (6)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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: 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-07-18T18:26:42.027Z
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-07-18T18:25:54.486Z
Learning: Starter project files auto-format after langflow run; these formatting changes can be committed or ignored
docs/docusaurus.config.js (5)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docusaurus.config.js : Site configuration such as title, tagline, URL, and navbar items 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-07-18T18:26:42.027Z
Learning: Applies to docs/sidebars.js : Sidebar navigation must be updated in docs/sidebars.js to reflect new or reorganized documentation content.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Internal links in documentation must be functional and not broken.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be written in Markdown or MDX files located under docs/docs/, following the prescribed directory structure for guides, reference, how-to, concepts, and API documentation.
docs/docs/Components/components-vector-stores.mdx (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
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.
🪛 LanguageTool
docs/docs/Agents/agents-tools.mdx
[style] ~30-~30: This phrase might be redundant. Consider either removing or replacing the adjective ‘additional’.
Context: ...* component. To try this for yourself, add an additional agent to the Simple Agent template: 1. C...
(ADD_AN_ADDITIONAL)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: build-and-deploy
🔇 Additional comments (20)
docs/docs/Concepts/concepts-playground.mdx (1)
72-76: Sentence reads well – no issuesThe added clarification accurately defines what a
session_idrepresents and matches the terminology guidelines.
Nothing to change here.docs/docs/Concepts/concepts-file-management.mdx (1)
73-85: Good clarification on base64 image payload ✅
The new wording (“attach image data as a base64-encoded string”) is clearer and aligns with API field expectations.docs/docs/Tutorials/chat-with-files.mdx (1)
28-30: Change looks goodTemplate name is now plain bold text, avoiding a broken link.
No further action required.docs/docs/Tutorials/mcp-tutorial.mdx (1)
36-37: Consistent capitalisation fixed – nice
**Simple Agent**now matches our template naming convention.docs/docs/Tutorials/agent.mdx (1)
25-30: Good consistency updateBoth occurrences of the template name now use Title Case.
No issues spotted.docs/docs/Integrations/Arize/integrations-arize.mdx (1)
81-82: Template reference updated correctlyLink removal and wording change read well.
Nothing further.docs/docs/Agents/agents.mdx (1)
13-14: Summary wording clarified – niceChanging to a question improves readability.
docs/docs/Concepts/concepts-overview.mdx (2)
48-48: Good template reference standardization.The removal of hyperlink formatting from Basic Prompting template aligns with the broader documentation cleanup effort. The terminology is properly capitalized and maintains the professional tone.
53-53: Effective template reference with alternative guidance.The change removes the hyperlink from Simple Agent template while providing users with an alternative path through the quickstart guide. This maintains user experience while aligning with the template documentation cleanup.
docs/docs/Components/components-prompts.mdx (2)
45-46: Good formatting improvements for code example clarity.The addition of colons and blank lines in the prompt template example improves readability and makes the structure clearer for users to understand and replicate.
Also applies to: 49-50
64-66: Excellent explanatory content addition.The new paragraph provides valuable context about using multiple variables in prompt templates with concrete examples. This enhances user understanding and follows the professional, actionable documentation style.
docs/docs/Integrations/Cleanlab/integrations-cleanlab.mdx (2)
130-131: Clear instructions with proper template reference.The updated instructions clearly describe how to create a flow and connect the necessary outputs to the evaluator component. The Vector Store RAG template name follows proper capitalization guidelines.
135-135: Good formatting improvement.The addition of a colon before the example output improves readability and follows consistent documentation formatting patterns.
docs/docs/Components/components-agents.mdx (2)
10-10: Good improvement to user engagement.Converting the summary text to a question format ("How do agents work?") makes the collapsible section more engaging and user-friendly while maintaining the informational purpose.
32-36: Excellent information reorganization.The restructuring consolidates related information about the Simple Agent template under the quickstart reference, creating a more logical flow. The template name follows proper formatting guidelines and the explanation provides valuable context about the template's capabilities.
docs/docusaurus.config.js (1)
210-238: Efficient redirect consolidation for removed template documentation.The consolidation of multiple individual template redirects into a single rule pointing to "/concepts-flows" is an effective approach for handling the removal of template documentation files. This reduces configuration complexity while ensuring users don't encounter broken links.
docs/docs/Agents/agents-tools.mdx (1)
35-36: Verify model namegpt-4.1OpenAI’s public model list (as of July 2025) does not include
gpt-4.1.
Double-check the exact model identifier (e.g.,gpt-4o,gpt-4-turbo) to avoid confusing users.docs/docs/Components/components-vector-stores.mdx (2)
53-61: Great clarity on Astra parameters – LGTMThe expanded descriptions for
token,database_name,collection_name, and embedding options are concise and meet the component-docs template.
93-94: Reference a removed template – ensure discoverabilityLine 93 points readers to the Vector Store RAG template, but the dedicated template page was deleted in this PR.
Confirm that users can still access the template from the UI or another doc; otherwise replace the reference or add a short inline explanation.docs/docs/Concepts/concepts-flows.mdx (1)
38-40: Confirm/contributing-templateslink existsThe new link looks useful, but no such page was included in this PR. Please verify that it resolves; otherwise create the page or remove the link.
github-actions
Bot
added
documentation
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (12)
docs/docs/Concepts/concepts-playground.mdx (1)
74-75: Minor style nit – capitalise “Session ID” for consistency
Throughout the docs we capitalise key terms (Component, Flow, API, JSON). Using “Session ID” (capital S, capital I) rather than “session ID” keeps that pattern consistent.-Chat sessions are identified by session ID (`session_id`), which is a unique identifier for a flow run. +Chat sessions are identified by **Session ID** (`session_id`), which is a unique identifier for a flow run.docs/docs/Concepts/concepts-file-management.mdx (1)
73-74: Clarify thatfilesexpects an array of strings.The sentence now says “…attach image data as a base64-encoded string,” but the example payload shows an array (
"files": ["data:image/png;base64,…"]).
Consider tightening wording to avoid mismatch:-* When you trigger a flow with the `/api/v1/run/$FLOW_ID` endpoint, you can use the `files` parameter to attach image data as a base64-encoded string: +* When you trigger a flow with the `/api/v1/run/$FLOW_ID` endpoint, use the `files` parameter to pass one or more base64-encoded image strings:docs/docs/Concepts/mcp-server.mdx (1)
67-70: Fix possessive typo in flow description
it's purposeshould be the possessiveits purpose.
Minor but worth correcting since the sentence sits in an explanatory tip box that readers will copy.- This provides no information to an agent about the type of flow or it's purpose. + This provides no information to an agent about the type of flow or its purpose.docs/docs/Agents/agents.mdx (1)
34-35: Consider linking the template entry pointYou reference the Simple Agent template but give readers no quick way to open it if they’re already inside Langflow.
A short parenthetical like “(New Flow ▸ Templates ▸ Simple Agent)” improves discoverability.docs/docs/Get-Started/about-langflow.mdx (1)
17-20: Add internal link for templates for faster onboardingSince you introduce templates here, consider linking “pre-built templates” to the section that explains how to start a flow from a template (
/concepts-flows#create-flows-from-templates).
This keeps the reader in-flow and aligns with the goal of quick prototyping.docs/docs/Tutorials/mcp-tutorial.mdx (1)
82-82: Capitalisation drift: “Simple Agent”In the phrase
your **Simple agent** flow, the “A” in Agent should be capital to stay consistent with the template name used elsewhere.-2. In your **Simple agent** flow, remove the **URL** and **Calculator** tools, and then add the [**MCP Tools**](/mcp-client) component to your workspace. +2. In your **Simple Agent** flow, remove the **URL** and **Calculator** tools, and then add the [**MCP Tools**](/mcp-client) component to your workspace.docs/docs/Components/components-prompts.mdx (2)
33-33: Fix capitalization inconsistency.The template name should be "Basic Prompting" (with capital P) to maintain consistency with other references throughout the documentation.
-1. Create a flow based on the **Basic prompting** template. +1. Create a flow based on the **Basic Prompting** template.
54-54: Fix step numbering sequence.The step numbering jumps from step 2 to step 4, skipping step 3. This should be corrected for clarity.
-4. Click **Check & Save** to save the template. +3. Click **Check & Save** to save the template.docs/docs/Components/components-vector-stores.mdx (1)
93-93: Reference to “Vector Store RAG” template could confuse readersSince dedicated template pages were removed, consider adding a short clarifying clause, e.g. “(available from New Flow → RAG in the UI)” so users know where to find it.
docs/docs/Components/components-helpers.mdx (2)
78-92: Capitalize “URLs” and “Markdown” for consistencyMinor wording tweak to follow the style guide (uppercase API/JSON/URL and proper noun “Markdown”).
-Use markdown to format your answer, properly embedding images and urls. +Use **Markdown** to format your answer, properly embedding images and URLs.
135-149: Same capitalization nit in second exampleApply the same wording fix here to keep examples consistent.
-Use markdown to format your answer, properly embedding images and urls. +Use **Markdown** to format your answer, properly embedding images and URLs.docs/docs/Agents/agents-tools.mdx (1)
28-32: Trim the redundant phrasing “add an additional”Light style polish – “add another agent” is simpler and avoids the LanguageTool warning.
-... add an additional agent to the **Simple Agent** template: +... add another agent to the **Simple Agent** template:
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (39)
docs/docs/API-Reference/api-files.mdx(1 hunks)docs/docs/API-Reference/api-flows-run.mdx(1 hunks)docs/docs/Agents/agents-tools.mdx(1 hunks)docs/docs/Agents/agents.mdx(2 hunks)docs/docs/Components/bundles-huggingface.mdx(1 hunks)docs/docs/Components/components-agents.mdx(2 hunks)docs/docs/Components/components-data.mdx(1 hunks)docs/docs/Components/components-helpers.mdx(2 hunks)docs/docs/Components/components-io.mdx(1 hunks)docs/docs/Components/components-models.mdx(1 hunks)docs/docs/Components/components-processing.mdx(1 hunks)docs/docs/Components/components-prompts.mdx(3 hunks)docs/docs/Components/components-vector-stores.mdx(2 hunks)docs/docs/Concepts/concepts-file-management.mdx(1 hunks)docs/docs/Concepts/concepts-flows.mdx(1 hunks)docs/docs/Concepts/concepts-overview.mdx(1 hunks)docs/docs/Concepts/concepts-playground.mdx(1 hunks)docs/docs/Concepts/concepts-publish.mdx(1 hunks)docs/docs/Concepts/concepts-voice-mode.mdx(1 hunks)docs/docs/Concepts/mcp-server.mdx(1 hunks)docs/docs/Develop/develop-application.mdx(1 hunks)docs/docs/Get-Started/about-langflow.mdx(1 hunks)docs/docs/Integrations/Arize/integrations-arize.mdx(1 hunks)docs/docs/Integrations/Cleanlab/integrations-cleanlab.mdx(1 hunks)docs/docs/Integrations/mcp-component-astra.mdx(1 hunks)docs/docs/Templates/basic-prompting.mdx(0 hunks)docs/docs/Templates/blog-writer.mdx(0 hunks)docs/docs/Templates/document-qa.mdx(0 hunks)docs/docs/Templates/financial-report-parser.mdx(0 hunks)docs/docs/Templates/memory-chatbot.mdx(0 hunks)docs/docs/Templates/sequential-agent.mdx(0 hunks)docs/docs/Templates/simple-agent.mdx(0 hunks)docs/docs/Templates/travel-planning-agent.mdx(0 hunks)docs/docs/Templates/vector-store-rag.mdx(0 hunks)docs/docs/Tutorials/agent.mdx(1 hunks)docs/docs/Tutorials/chat-with-files.mdx(1 hunks)docs/docs/Tutorials/mcp-tutorial.mdx(1 hunks)docs/docusaurus.config.js(1 hunks)docs/sidebars.js(0 hunks)
💤 Files with no reviewable changes (10)
- docs/sidebars.js
- docs/docs/Templates/sequential-agent.mdx
- docs/docs/Templates/simple-agent.mdx
- docs/docs/Templates/financial-report-parser.mdx
- docs/docs/Templates/document-qa.mdx
- docs/docs/Templates/travel-planning-agent.mdx
- docs/docs/Templates/blog-writer.mdx
- docs/docs/Templates/basic-prompting.mdx
- docs/docs/Templates/vector-store-rag.mdx
- docs/docs/Templates/memory-chatbot.mdx
🧰 Additional context used
📓 Path-based instructions (2)
docs/docs/**/*.{md,mdx}
📄 CodeRabbit Inference Engine (.cursor/rules/docs_development.mdc)
docs/docs/**/*.{md,mdx}: All documentation content must be written in Markdown or MDX files located under docs/docs/, following the prescribed directory structure for guides, reference, how-to, concepts, and API documentation.
All documentation Markdown and MDX files must begin with a frontmatter block including at least title and description fields.
Use admonitions (:::tip, :::warning, :::danger) in Markdown/MDX files to highlight important information, warnings, or critical issues.
All images referenced in documentation must include descriptive alt text for accessibility.
All code examples included in documentation must be tested and verified to work as shown.
Internal links in documentation must be functional and not broken.
Content must follow the style guide: professional but approachable tone, second person voice, present tense, short paragraphs, sentence case headers, inline code with backticks, bold for UI elements, italic for emphasis, and parallel structure in lists.
Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
Files:
docs/docs/Components/bundles-huggingface.mdxdocs/docs/Tutorials/agent.mdxdocs/docs/Develop/develop-application.mdxdocs/docs/Concepts/concepts-playground.mdxdocs/docs/Concepts/concepts-voice-mode.mdxdocs/docs/Integrations/mcp-component-astra.mdxdocs/docs/Integrations/Arize/integrations-arize.mdxdocs/docs/Get-Started/about-langflow.mdxdocs/docs/Concepts/concepts-file-management.mdxdocs/docs/Concepts/mcp-server.mdxdocs/docs/Tutorials/chat-with-files.mdxdocs/docs/Components/components-prompts.mdxdocs/docs/Components/components-data.mdxdocs/docs/API-Reference/api-flows-run.mdxdocs/docs/Tutorials/mcp-tutorial.mdxdocs/docs/Components/components-io.mdxdocs/docs/Agents/agents.mdxdocs/docs/API-Reference/api-files.mdxdocs/docs/Components/components-agents.mdxdocs/docs/Concepts/concepts-overview.mdxdocs/docs/Components/components-models.mdxdocs/docs/Concepts/concepts-publish.mdxdocs/docs/Components/components-processing.mdxdocs/docs/Integrations/Cleanlab/integrations-cleanlab.mdxdocs/docs/Components/components-helpers.mdxdocs/docs/Agents/agents-tools.mdxdocs/docs/Concepts/concepts-flows.mdxdocs/docs/Components/components-vector-stores.mdx
docs/docusaurus.config.js
📄 CodeRabbit Inference Engine (.cursor/rules/docs_development.mdc)
Site configuration such as title, tagline, URL, and navbar items must be managed in docs/docusaurus.config.js.
Files:
docs/docusaurus.config.js
🧠 Learnings (28)
📓 Common learnings
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
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-07-18T18:26:42.027Z
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-07-18T18:26:42.027Z
Learning: Applies to docs/sidebars.js : Sidebar navigation must be updated in docs/sidebars.js to reflect new or reorganized documentation content.
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/Tutorials/agent.mdx (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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/Develop/develop-application.mdx (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: 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-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use admonitions (:::tip, :::warning, :::danger) in Markdown/MDX files to highlight important information, warnings, or critical issues.
docs/docs/Concepts/concepts-voice-mode.mdx (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : 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/Integrations/mcp-component-astra.mdx (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Internal links in documentation must be functional and not broken.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : 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-07-18T18:26:42.027Z
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-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
docs/docs/Integrations/Arize/integrations-arize.mdx (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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: 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/Get-Started/about-langflow.mdx (7)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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: 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-07-18T18:25:54.486Z
Learning: Starter project files auto-format after langflow run; these formatting changes can be committed or ignored
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
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-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : 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.mdx (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All images referenced in documentation must include descriptive alt text for accessibility.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/static/img/**/* : Images used in documentation must be stored in docs/static/img/ and referenced with descriptive alt text.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Images and screenshots in documentation should have descriptive alt text and filenames, and should highlight relevant UI elements.
docs/docs/Concepts/mcp-server.mdx (6)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
Learnt from: deon-sanchez
PR: #9158
File: src/backend/base/langflow/api/v1/mcp_projects.py:404-404
Timestamp: 2025-07-23T21:19:22.567Z
Learning: In langflow MCP projects configuration, prefer using dynamically computed URLs (like the sse_url variable) over hardcoded localhost URLs to ensure compatibility across different deployment environments.
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: 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).
docs/docs/Tutorials/chat-with-files.mdx (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-07-18T18:25:54.486Z
Learning: Starter project files auto-format after langflow run; these formatting changes can be committed or ignored
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
docs/docs/Components/components-prompts.mdx (5)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
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: 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-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : 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.
docs/docs/Components/components-data.mdx (6)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
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-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Internal links in documentation must be functional and not broken.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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: 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-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : 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-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use admonitions (:::tip, :::warning, :::danger) in Markdown/MDX files to highlight important information, warnings, or critical issues.
docs/docs/API-Reference/api-flows-run.mdx (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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.
docs/docs/Tutorials/mcp-tutorial.mdx (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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/Components/components-io.mdx (5)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
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-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Internal links in documentation must be functional and not broken.
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-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/Agents/agents.mdx (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
docs/docs/API-Reference/api-files.mdx (8)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
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-07-18T18:26:42.027Z
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-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All images referenced in documentation must include descriptive alt text for accessibility.
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-23T12:46:29.953Z
Learning: Images and screenshots in documentation should have descriptive alt text and filenames, and should highlight relevant UI elements.
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-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : All documentation content must be written in Markdown or MDX files located under docs/docs/, following the prescribed directory structure for guides, reference, how-to, concepts, and API documentation.
docs/docs/Components/components-agents.mdx (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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/Concepts/concepts-overview.mdx (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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/Components/components-models.mdx (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
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: 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-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : 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-publish.mdx (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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: 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-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : 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: deon-sanchez
PR: #9158
File: src/backend/base/langflow/api/v1/mcp_projects.py:404-404
Timestamp: 2025-07-23T21:19:22.567Z
Learning: In langflow MCP projects configuration, prefer using dynamically computed URLs (like the sse_url variable) over hardcoded localhost URLs to ensure compatibility across different deployment environments.
docs/docs/Components/components-processing.mdx (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
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/Integrations/Cleanlab/integrations-cleanlab.mdx (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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: Documentation content should be concise, with short paragraphs and parallel structure in lists for better readability.
docs/docusaurus.config.js (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docusaurus.config.js : Site configuration such as title, tagline, URL, and navbar items 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-07-18T18:26:42.027Z
Learning: Applies to docs/sidebars.js : Sidebar navigation must be updated in docs/sidebars.js to reflect new or reorganized documentation content.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Internal links in documentation must be functional and not broken.
docs/docs/Components/components-helpers.mdx (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
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: 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-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
docs/docs/Agents/agents-tools.mdx (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: 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/Concepts/concepts-flows.mdx (6)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and 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: 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-07-18T18:25:54.486Z
Learning: Starter project files auto-format after langflow run; these formatting changes can be committed or ignored
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
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-vector-stores.mdx (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
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.
🪛 LanguageTool
docs/docs/Agents/agents-tools.mdx
[style] ~30-~30: This phrase might be redundant. Consider either removing or replacing the adjective ‘additional’.
Context: ...* component. To try this for yourself, add an additional agent to the Simple Agent template: 1. C...
(ADD_AN_ADDITIONAL)
🔇 Additional comments (30)
docs/docs/Develop/develop-application.mdx (1)
209-213: Bold-style update is consistent with new template-reference conventionNothing else changed in this vicinity and the bold formatting for “Pokédex” aligns with the new, link-free template naming policy.
docs/docs/Integrations/mcp-component-astra.mdx (1)
20-21: Link removal OK – refine orphaned link verificationThe initial search only returned image embeds (e.g.
/img/workspace-basic-prompting.png), not any leftover docs links to removed templates. To be certain there are no stale markdown links to deleted template pages, please update and rerun the check using a regex that excludes image embeds:# Search for markdown links (not images) to removed template pages find docs/docs -type f \( -name '*.md' -o -name '*.mdx' \) -print0 \ | xargs -0 rg -n '\[[^!][^\]]+\]\(/.*(simple-agent|basic-prompting|vector-store-rag|blog-writer|sequential-agent|memory-chatbot|document-qa|financial-report-parser|travel-planning-agent)[^)]*\)'No matches should remain.
docs/docs/Concepts/concepts-voice-mode.mdx (1)
32-34: Reference style now matches updated docs policySwitching the “Simple Agent” mention to bold text keeps wording clear and avoids a broken link.
docs/docs/Integrations/Arize/integrations-arize.mdx (1)
81-82: Template mention reformatted correctlyThe example now uses bold text for Simple Agent, consistent with the new convention and free of dead links.
docs/docs/Components/components-data.mdx (1)
420-421: Updated template reference complies with style guideThe step now cites Basic Prompting in bold, eliminating a link that would have 404-ed after template page removal.
docs/docs/Components/bundles-huggingface.mdx (1)
64-66: Link removal looks good – reference is now plain bold text
The template name is still clear to the reader and we avoid a broken link after deleting the old template page.docs/docs/Concepts/concepts-publish.mdx (1)
140-142: Updated template reference reads well
The change to “Basic Prompting template flow” matches the new convention. No further action needed.docs/docs/API-Reference/api-flows-run.mdx (1)
23-25: All clear—no stale/basic-promptinglinks found
I reran the search with proper escaping acrossdocs/docs/**/*.{md,mdx}and found zero references to/basic-prompting. There are no remaining broken links.docs/docs/Components/components-processing.mdx (1)
726-733: Template name update is correct and consistent
The step now points to the Basic Prompting template with bold styling, matching the new docs pattern.docs/docs/Components/components-models.mdx (1)
21-21: Link removal is correct – reference is still clear.The link was removed without altering meaning, capitalization is consistent, and no broken link remains.
docs/docs/Tutorials/agent.mdx (1)
25-30: Consistent capitalization of “Simple Agent”.Good catch on standardizing the template name; matches established terminology across docs.
docs/docs/Components/components-io.mdx (1)
118-122: Reference looks good after link removal.The bullet keeps readers aware of the Basic Prompting template without creating a dead link.
docs/docs/Tutorials/chat-with-files.mdx (1)
28-31: Template mention updated correctly.Both occurrences now use proper capitalization and no longer link to removed pages.
docs/docs/Agents/agents.mdx (1)
13-13: Sentence-case heading looks goodChanging the summary title to the question “How do agents work?” follows the docs guidance for sentence-case headers. No action needed.
docs/docs/Tutorials/mcp-tutorial.mdx (1)
36-36: Template name is capitalised correctly – nice catchThe step now references Simple Agent with consistent capitalisation. Looks good.
docs/docs/API-Reference/api-files.mdx (1)
88-90: Flows vs. templates wording is now uniformSwitching to “Basic Prompting template flow” matches the new convention introduced in this PR and avoids a dead link. ✅
docs/docs/Concepts/concepts-overview.mdx (2)
48-48: LGTM: Template reference updated correctly.The change from markdown link to plain bold text for the Basic Prompting template aligns with the PR objective to remove individual template pages while maintaining clear reference to the template.
53-53: Excellent enhancement of user guidance.The expanded instruction provides users with a helpful alternative (the Langflow quickstart) after removing the direct template link, improving the overall user experience while maintaining the instructional flow.
docs/docs/Components/components-prompts.mdx (2)
45-51: Good formatting improvements.The addition of colons and blank lines around the variables improves the readability and clarity of the prompt template example.
64-66: Valuable addition for user guidance.The explanation about using multiple variables and connecting them to other components (Text Input, URL, File) provides practical, actionable guidance that enhances the documentation's instructional value.
docs/docs/Components/components-agents.mdx (3)
10-10: Good stylistic improvement.Converting the heading to question form ("How do agents work?") makes it more user-focused and engaging, which is appropriate for explanatory content.
32-32: Effective restructuring of guidance.Consolidating the guidance to lead with the quickstart while still mentioning the Simple Agent template provides better user flow and aligns with the objective of reducing reliance on individual template pages.
34-35: Appropriate positioning of template information.Moving the Simple Agent template explanation to supporting context while maintaining the technical details provides the right balance of information without over-emphasizing the template itself.
docs/docs/Integrations/Cleanlab/integrations-cleanlab.mdx (2)
130-131: Good clarity improvements.Removing the template link and rephrasing the connection instructions to "from the other components in the RAG flow" makes the guidance clearer and more descriptive while aligning with the PR objectives.
135-135: Minor formatting improvement.Adding the colon before the example output improves readability and follows consistent formatting patterns for introducing examples.
docs/docusaurus.config.js (1)
210-238: Excellent redirect consolidation.Consolidating all template-related redirects to point to
/concepts-flowsis a smart approach that:
- Prevents broken links when template pages are removed
- Reduces configuration redundancy and maintenance burden
- Directs users to relevant conceptual information
- Aligns perfectly with the PR objective
This change properly implements the documentation restructuring while maintaining good user experience.
docs/docs/Concepts/concepts-flows.mdx (2)
38-40: Verify the/contributing-templateslink still resolves now that individual template pages are goneAll template-specific docs were removed in this PR, but the new “contribute templates” link still points at
/contributing-templates.
Double-check that this target page (or redirect) exists; otherwise users will hit a 404.
23-42: Clear, consistent, and terminology-compliant – nice updateThe restructured bullet list cleanly walks users through each creation path, uses capitalized “Langflow”, “Flow”, “Component”, and adopts sentence-case headers.
No issues spotted. 👍docs/docs/Components/components-vector-stores.mdx (1)
53-61: Expanded parameter descriptions read wellThe added context around token scope, database/collection creation, and Vectorize integration improves usability without breaking style-guide rules.
docs/docs/Agents/agents-tools.mdx (1)
38-44: Great practical guidance – thumbs-upThe step-by-step edits to tool metadata and enabling/disabling tools are clear, concise, and align with the refreshed multi-agent workflow.
SonicDMG
temporarily deployed
to
lfoss-1556 - langflow-manual-install PR #9235
Render
Destroyed
github-actions
Bot
added
documentation
|
|
Build successful! ✅ |
…tory notes within Langflow (langflow-ai#9235) * finish template description * remove travel planning and simple agent pages * remove sequential agent and memory chatbot * remove 2 template, finish redirects, sidebar * remove vector store rag page * remove basic prompting page * add bold to template name * fix link
3 participants
Summary by CodeRabbit