fix: standardize "README" title and update API key configuration notes in 3 main flow templates

[deon-sanchez]

This pull request updates the README sections and quickstart instructions in multiple starter project JSON files to provide a more consistent, user-friendly onboarding experience. The changes standardize the introductory sections, clarify credential setup steps, and ensure the documentation is clear and accessible for new users. Additionally, minor metadata updates were made to the .secrets.baseline file.

README and Quickstart Documentation Improvements:

• Standardized the README sections across all starter project JSON files, replacing previous descriptions with a # 📖 README heading and harmonizing the quickstart steps and credential setup instructions to refer to "Model Provider" and API credentials, improving clarity for new users. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]

Project Metadata Updates:

• Updated line numbers and the generated_at timestamp in .secrets.baseline to reflect the latest state of the starter project files and secret scanning. [1] [2]

Summary by CodeRabbit

Release Notes

• Documentation
  • Updated starter project descriptions and setup instructions to use standardized, provider-agnostic guidance.
  • Improved README formatting across all starter projects for consistency.
  • Refreshed quickstart steps to reference generic model provider configuration instead of service-specific credentials.
  • Enhanced metadata and visual formatting for starter project notes.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: c5697e9f-a331-43e0-93f5-68164089f70b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Walkthrough

Updates descriptions and metadata across multiple starter project templates, standardizing note content to README-style formatting with emoji headers and generalizing API configuration instructions from specific service keys to generic "Model Provider" setup. Also updates secret entry baseline timestamps and line numbers.

Changes

Cohort / File(s)	Summary
Secret Baseline .secrets.baseline	Updated line_number values for multiple secret entries and advanced generated_at timestamp from 2026-02-27T23:29:30Z to 2026-03-03T17:44:43Z.
Starter Project Documentation Updates src/backend/base/langflow/initial_setup/starter_projects/*.json (30+ files including Basic Prompt Chaining, Basic Prompting, Blog Writer, Custom Component Generator, Document Q&A, Financial Report Parser, Hybrid Search RAG, Image Sentiment Analysis, Instagram Copywriter, Invoice Summarizer, Knowledge Ingestion, Knowledge Retrieval, Market Research, Meeting Summary, Memory Chatbot, News Aggregator, Nvidia Remix, Pokédex Agent, Portfolio Website Code Generator, Price Deal Finder, Research Agent, Research Translation Loop, SEO Keyword Generator, SaaS Pricing, Search agent, Sequential Tasks Agents, Simple Agent, Social Media Agent, Text Sentiment Analysis, Travel Planning Agents, Twitter Thread Generator, Vector Store RAG, Youtube Analysis)	Standardized note descriptions to README-style format (heading changed to "# 📖 README"). Updated quickstart instructions to reference generic "Configure your Model Provider" instead of specific API keys. Changed "Quickstart" to "Quick start". Added or updated display_name, documentation, and template metadata fields on note nodes. Minor template styling adjustments (backgroundColor changes in some files).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 7

✅ Passed checks (7 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Test Coverage For New Implementations	✅ Passed	PR contains only JSON configuration and documentation text updates to starter projects with no new code functionality, logic changes, or executable features requiring additional test coverage.
Test Quality And Coverage	✅ Passed	PR modifies only JSON metadata and documentation content in starter projects; existing tests validate structural integrity and loading, not content specifics.
Test File Naming And Structure	✅ Passed	The custom check for test file naming and structure is not applicable to this pull request. The PR exclusively modifies configuration files (.secrets.baseline) and starter project JSON documentation files. No test files are present or modified.
Excessive Mock Usage Warning	✅ Passed	This pull request does not include any test files in its changes. The PR exclusively modifies JSON configuration files for starter projects and the .secrets.baseline file. Since the custom check is designed to review test files for excessive mock usage, and this PR contains no test code modifications, the check is not applicable to the scope of these changes.
Title check	✅ Passed	The title accurately describes the main change: standardizing README titles and updating API key configuration notes across starter project templates, which aligns with the extensive modifications visible in the changeset.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch le-454

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Frontend Unit Test Coverage Report

Coverage Summary

Lines	Statements	Branches	Functions
	23.24% (8235/35429)	16.02% (4458/27826)	15.91% (1185/7445)

Unit Test Results

Tests	Skipped	Failures	Errors	Time
2631	0 💤	0 ❌	0 🔥	43.25s ⏱️

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 37.43%. Comparing base (335656f) to head (dc9968c).
⚠️ Report is 1 commits behind head on main.

❌ Your project status has failed because the head coverage (42.37%) is below the target coverage (60.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #12005      +/-   ##
==========================================
- Coverage   37.45%   37.43%   -0.03%     
==========================================
  Files        1616     1616              
  Lines       79060    79060              
  Branches    11946    11946              
==========================================
- Hits        29614    29595      -19     
- Misses      47788    47808      +20     
+ Partials     1658     1657       -1     

Flag	Coverage Δ
backend	57.33% <ø> (-0.10%)	⬇️
frontend	20.82% <ø> (ø)
lfx	42.37% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 9 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[coderabbitai]

Actionable comments posted: 1

Note

Due to the large number of review comments, Critical, Major severity comments were prioritized as inline comments.

🟡 Minor comments (20)

src/backend/base/langflow/initial_setup/starter_projects/Text Sentiment Analysis.json-769-769 (1)

769-769: ⚠️ Potential issue | 🟡 Minor

Remove OpenAI-specific setup text from this generalized README.

The note still requires an “OpenAI API key” and references an “OpenAI Model Component,” which conflicts with the new provider-agnostic quickstart and the actual LanguageModelComponent usage in this flow. Please make prerequisites and step descriptions fully provider-neutral.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/Text` Sentiment
Analysis.json at line 769, The README still contains OpenAI-specific text;
update it to be provider-agnostic by removing references to "OpenAI API key" and
"OpenAI Model Component" and replacing them with neutral phrases like "Model
provider credentials" or "API key for your chosen model provider" and mention
the actual component name used in the flow (LanguageModelComponent) where
appropriate; also adjust the Quick start steps and prerequisites to refer
generically to configuring the Model Provider and loading data into the File
Component, and ensure prompts and final step reference the
LanguageModelComponent (or "model component") rather than OpenAI-specific
wording.

src/backend/base/langflow/initial_setup/starter_projects/Invoice Summarizer.json-120-120 (1)

120-120: ⚠️ Potential issue | 🟡 Minor

Align prerequisites with provider-agnostic setup language.

Line 120 still requires an “OpenAI API key”, but the new quickstart says to configure a generic “Model Provider”. This can confuse users using non-OpenAI providers. Consider changing that prerequisite to provider-agnostic wording (e.g., “A Model Provider API key”).

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/Invoice`
Summarizer.json at line 120, Update the "description" field in Invoice
Summarizer.json to make the prerequisites provider-agnostic: replace the
specific "An OpenAI API key" line with wording like "A Model Provider API key
(e.g., OpenAI, Anthropic, or other supported provider)" so the quickstart aligns
with the earlier instruction to configure a generic Model Provider; target the
"description" property in the JSON to perform this change.

src/backend/base/langflow/initial_setup/starter_projects/Youtube Analysis.json-1964-1964 (1)

1964-1964: ⚠️ Potential issue | 🟡 Minor

Fix typo in README quickstart text ("YoutTube" → "YouTube").

Line 1964 has a user-facing typo in the setup instructions, which reduces polish and can confuse new users scanning prerequisites.

✏️ Suggested fix

-            "description": "# 📖 README\nThis flow performs comprehensive analysis of YouTube videos.\n1.  Extract video comments and transcripts.\n2.  Run sentiment analysis on comments using LLM.\n3.  Combine transcript content and comment sentiment for comprehensive video analysis.\n## Quick start\n- Configure your **Model Provider** with your API credentials.\n- Add your **YouTube Data API v3 key**\n- If you don't have a YoutTube API key, create one in the [Google Cloud Console](https://console.cloud.google.com).\n- Ensure the chat input is a valid YouTube video URL. A sample URL is provided in the chat input component.\n",
+            "description": "# 📖 README\nThis flow performs comprehensive analysis of YouTube videos.\n1.  Extract video comments and transcripts.\n2.  Run sentiment analysis on comments using LLM.\n3.  Combine transcript content and comment sentiment for comprehensive video analysis.\n## Quick start\n- Configure your **Model Provider** with your API credentials.\n- Add your **YouTube Data API v3 key**\n- If you don't have a YouTube API key, create one in the [Google Cloud Console](https://console.cloud.google.com).\n- Ensure the chat input is a valid YouTube video URL. A sample URL is provided in the chat input component.\n",

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/Youtube`
Analysis.json at line 1964, There's a typo in the JSON "description" string for
the README (the Quick start section) — replace the misspelled "YoutTube" with
the correct "YouTube" in the value assigned to the description property (the
long README string containing "## Quick start" and the YouTube API instructions)
so the user-facing text reads "YouTube API key" and "YouTube" consistently.

src/backend/base/langflow/initial_setup/starter_projects/Pokédex Agent.json-679-679 (1)

679-679: ⚠️ Potential issue | 🟡 Minor

Align prerequisites with provider-agnostic quickstart language.

This note now mixes generic setup (“Model Provider”) with a provider-specific prerequisite (“OpenAI API key”), which can confuse onboarding. Consider making prerequisites provider-neutral and keep “Pokédex” spelling consistent.

✏️ Suggested wording update

- "description": "# 📖 README\nCollect research on Pokémon with a specialized **Agent** and the Pokédex API.\n\n## Prerequisites\n\n* An [OpenAI API key](https://platform.openai.com/)\n\n## Quick start\n\n1. Configure your **Model Provider** with your API credentials.\n2.  Click **Playground** and ask about your favorite Pokémon.\nThe **Agent** queries the Pokedex API and returns a formatted entry.",
+ "description": "# 📖 README\nCollect research on Pokémon with a specialized **Agent** and the Pokédex API.\n\n## Prerequisites\n\n* API credentials for your selected **Model Provider**\n\n## Quick start\n\n1. Configure your **Model Provider** with your API credentials.\n2. Click **Playground** and ask about your favorite Pokémon.\nThe **Agent** queries the Pokédex API and returns a formatted entry.",

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/Pokédex` Agent.json
at line 679, Update the README "description" field to make prerequisites
provider-agnostic by replacing "An OpenAI API key" with a neutral phrase like
"An API key for your chosen model provider" (or "Model provider API key (e.g.,
OpenAI)") inside the "Prerequisites" bullet, and ensure consistent spelling of
"Pokédex" throughout the description (e.g., replace any "Pokedex API"
occurrences). Target the README/description JSON string (the "description"
field) and the "Prerequisites" section to apply these text changes.

src/backend/base/langflow/initial_setup/starter_projects/Financial Report Parser.json-689-689 (1)

689-689: ⚠️ Potential issue | 🟡 Minor

Fix grammar typo in README note text

On Line 689, the phrase “converts extracted data into a messages” is grammatically incorrect and user-visible. Please change it to “into messages” (or “into a message”).

✏️ Proposed text fix

- ... Finally, the **Parser** component converts extracted data into a messages to be returned to the user.
+ ... Finally, the **Parser** component converts extracted data into messages to be returned to the user.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/Financial` Report
Parser.json at line 689, Update the "description" string in the Financial Report
Parser template (the "description" field in Financial Report Parser.json) to fix
the grammar: replace the phrase "converts extracted data into a messages" with
"converts extracted data into messages" (or "into a message") inside the README
text so the user-visible sentence reads correctly.

src/backend/base/langflow/initial_setup/starter_projects/Vector Store RAG.json-1053-1053 (1)

1053-1053: ⚠️ Potential issue | 🟡 Minor

Fix typo in README guidance sentence

Line 1053 contains a user-facing typo: “Only the run the Load Data flow…”. This should read “Only run the Load Data flow…”.

✏️ Suggested text fix

-Only the run the **Load Data** flow when you need to populate your vector database with baseline content, such as product data.
+Only run the **Load Data** flow when you need to populate your vector database with baseline content, such as product data.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/Vector` Store
RAG.json at line 1053, In the "description" string for the starter project (the
README text), fix the typo "Only the run the **Load Data** flow when you need to
populate..." to read "Only run the **Load Data** flow when you need to
populate..." by updating that sentence inside the description field so the
user-facing README is correct.

src/backend/base/langflow/initial_setup/starter_projects/News Aggregator.json-828-828 (1)

828-828: ⚠️ Potential issue | 🟡 Minor

Keep prerequisites aligned with provider-agnostic setup.

Line 828 lists an OpenAI API Key as a prerequisite, but the same note now instructs users to configure a generic Model Provider. This mixed wording can mislead users who choose non-OpenAI providers. Please make the prerequisite provider-neutral (for example: “Model Provider API credentials”).

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/News`
Aggregator.json at line 828, The README's prerequisites are provider-specific;
update the "description" field in News Aggregator.json (the "description"
string) to replace the "OpenAI API Key" entry with a provider-neutral phrase
such as "Model Provider API credentials" (remove or replace the OpenAI-specific
link) so the prerequisites match the generic "Model Provider" wording used
elsewhere.

src/backend/base/langflow/initial_setup/starter_projects/Price Deal Finder.json-1514-1514 (1)

1514-1514: ⚠️ Potential issue | 🟡 Minor

Fix README copy errors and list formatting in onboarding note.

Line 1514 has user-facing text issues (typo "searcn", extra ) after the sample query, and inconsistent Agent QL naming). This weakens quickstart clarity.

✏️ Proposed text fix

-            "description": "# 📖 README\nThis flow searches and compares prices of a product on the web.\n## Prerequisites\n\n* **[AgentQL API Key](https://dev.agentql.com/api-keys)**\n* **[OpenAI API Key](https://platform.openai.com/)**\n* **[TavilyAI Search API Key](https://tavily.com/)**\n\n## Quick start\n\n1. Configure your **Model Provider** with your API credentials.\n2. Add your [AgentQL API Key](https://dev.agentql.com/api-keys) to the **AgentQL** component.\n3. Add your [TavilyAI Search API Key](https://tavily.com/) to the **Tavily AI Search** component.\n4. Click **Playground** and enter a product in chat. For example, search \"iPhone 16 Pro 512 GB\")\n* The **Agent** component populates the **Tavily AI Search** component's **Search Query** field, and the **Agent QL** component's **URL** and **Query** fields. \n\n* The **Agent** returns a structured response to your searcn in the chat.",
+            "description": "# 📖 README\nThis flow searches and compares prices of a product on the web.\n## Prerequisites\n\n* **[AgentQL API Key](https://dev.agentql.com/api-keys)**\n* **[OpenAI API Key](https://platform.openai.com/)**\n* **[TavilyAI Search API Key](https://tavily.com/)**\n\n## Quick start\n\n1. Configure your **Model Provider** with your API credentials.\n2. Add your [AgentQL API Key](https://dev.agentql.com/api-keys) to the **AgentQL** component.\n3. Add your [TavilyAI Search API Key](https://tavily.com/) to the **Tavily AI Search** component.\n4. Click **Playground** and enter a product in chat. For example, search \"iPhone 16 Pro 512 GB\".\n5. The **Agent** component populates the **Tavily AI Search** component's **Search Query** field, and the **AgentQL** component's **URL** and **Query** fields.\n6. The **Agent** returns a structured response to your search in the chat.",

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/Price` Deal
Finder.json at line 1514, Update the README text in the "description" field of
Price Deal Finder.json: fix the typo "searcn" -> "search", remove the stray
closing parenthesis after the sample query "iPhone 16 Pro 512 GB", and normalize
the component name to "AgentQL" everywhere (replace "Agent QL" with "AgentQL");
also tidy list/bullet spacing so the quick start steps are consistently
formatted as separate lines/bullets and the final sentence reads clearly (e.g.,
"The Agent returns a structured response to your search in the chat.").

src/backend/base/langflow/initial_setup/starter_projects/Basic Prompt Chaining.json-1232-1232 (1)

1232-1232: ⚠️ Potential issue | 🟡 Minor

Keep prerequisites provider-agnostic for consistency.

Line 1232 mixes generic setup (“Model Provider”) with an OpenAI-only prerequisite, which can mislead users selecting other providers.

✏️ Proposed docs tweak

- ## Prerequisites
-
- * [OpenAI API Key](https://platform.openai.com/)
+ ## Prerequisites
+
+ * API credentials for your selected **Model Provider**.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/Basic` Prompt
Chaining.json at line 1232, The README description in the "description" field of
Basic Prompt Chaining.json is OpenAI-specific by mentioning "OpenAI API Key";
update that line to be provider-agnostic (e.g., "API credentials for your chosen
Model Provider" or "Model Provider credentials (API key/token)"), remove the
OpenAI-only link, and ensure the prerequisites section references "Model
Provider" consistently so other providers are not misled.

src/backend/base/langflow/initial_setup/starter_projects/Research Translation Loop.json-896-896 (1)

896-896: ⚠️ Potential issue | 🟡 Minor

Align provider wording in README body with the new generic setup language.

The quickstart now correctly says Model Provider, but the body still says translation is done by the OpenAI component. Consider replacing those mentions with Language Model component (or “selected model provider”) to avoid implying OpenAI is required.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/Research`
Translation Loop.json at line 896, Update the README description string (the
"description" field in the Research Translation Loop template) to remove
explicit "OpenAI" mentions and instead use neutral wording like "Language Model
component" or "selected model provider"; specifically replace phrases such as
"translated into Portuguese by the **OpenAI** model component" with "translated
into Portuguese by the **Language Model component** (or selected model
provider)" and similarly update any other occurrences in that description text
to align with the generic "Model Provider" terminology.

src/backend/base/langflow/initial_setup/starter_projects/Blog Writer.json-772-772 (1)

772-772: ⚠️ Potential issue | 🟡 Minor

Align prerequisites with provider-agnostic quickstart text.

On Line 772, the Prerequisites section still requires an OpenAI key, while the quickstart now uses generic Model Provider wording. This is inconsistent for users using non-OpenAI providers.

Suggested wording update

-            "description": "# 📖 README\nCreate a blog post by using content fetched from URLs and user-provided instructions.\n\n## Prerequisites\n\n* An [OpenAI API key](https://platform.openai.com/)\n\n## Quick start\n\n1. Configure your **Model Provider** with your API credentials.\n2.  In the **URL** component, enter URLs you want to fetch content from. Ensure they start with `http://` or `https://`.\n3. Open the **Playground**. A blog post is written from the content fetched by the **URL** component.",
+            "description": "# 📖 README\nCreate a blog post by using content fetched from URLs and user-provided instructions.\n\n## Prerequisites\n\n* Access to a supported **Model Provider** and its API credentials\n\n## Quick start\n\n1. Configure your **Model Provider** with your API credentials.\n2. In the **URL** component, enter URLs you want to fetch content from. Ensure they start with `http://` or `https://`.\n3. Open the **Playground**. A blog post is written from the content fetched by the **URL** component.",

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/Blog` Writer.json at
line 772, The README description's Prerequisites still mentions "An [OpenAI API
key]" which is inconsistent with the provider-agnostic "Model Provider" wording;
update the "description" value in the Blog Writer.json (the README string) to a
generic prerequisite such as "A model provider API key or credentials (configure
your Model Provider in the app)" so it no longer references OpenAI by name and
matches the Quick start language.

src/backend/base/langflow/initial_setup/starter_projects/Document Q&A.json-663-663 (1)

663-663: ⚠️ Potential issue | 🟡 Minor

Minor typo: double space in Quick start step 2.

There's an extra space in the text: "select a file you want to load" should be "select a file you want to load".

🔤 Proposed fix

-            "description": "# 📖 README\nThis flow loads a file and uses an LLM to answer questions based on content from the loaded document. \n\n## Prerequisites\n\n* An [OpenAI API key](https://platform.openai.com/)\n\n## Quick start\n\n1. Configure your **Model Provider** with your API credentials.\n2.  In the **File** component, select a file  you want to load.\n3. Open the **Playground** and chat with your document.",
+            "description": "# 📖 README\nThis flow loads a file and uses an LLM to answer questions based on content from the loaded document. \n\n## Prerequisites\n\n* An [OpenAI API key](https://platform.openai.com/)\n\n## Quick start\n\n1. Configure your **Model Provider** with your API credentials.\n2. In the **File** component, select a file you want to load.\n3. Open the **Playground** and chat with your document.",

Note: There's also a double space after "2." in the numbered list (2. In the **File**), which should be a single space for consistency with the other list items.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/Document` Q&A.json
at line 663, In the "description" string of the Document Q&A starter (the
"description" value in Document Q&A.json) remove the double spaces in the Quick
start step so the line reads "2. In the **File** component, select a file you
want to load." (replace the current "2.  In the **File** component, select a
file  you want to load."), ensuring both the space after "2." and the extra
space before "you" are reduced to a single space.

src/backend/base/langflow/initial_setup/starter_projects/SEO Keyword Generator.json-400-400 (1)

400-400: ⚠️ Potential issue | 🟡 Minor

Align prerequisites with the provider-agnostic setup text.

Line 400 still hardcodes OpenAI API Key in prerequisites, while the rest of the README uses generic Model Provider instructions. This can confuse users choosing non-OpenAI providers.

✏️ Suggested update

- * [OpenAI API Key](https://platform.openai.com/)
+ * API credentials for your selected **Model Provider** (for example: OpenAI, Anthropic, Groq, etc.)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/SEO` Keyword
Generator.json at line 400, The README in the "description" field of SEO Keyword
Generator.json hardcodes "OpenAI API Key" which conflicts with the
provider-agnostic "Model Provider" text; update that sentence to a generic
phrasing such as "Model Provider API Key (your provider's API key)" and remove
or replace the OpenAI-specific link so the prerequisites are provider-agnostic;
ensure the "description" value consistently references "Model Provider"
elsewhere in the document.

src/backend/base/langflow/initial_setup/starter_projects/Social Media Agent.json-641-641 (1)

641-641: ⚠️ Potential issue | 🟡 Minor

Keep prerequisites provider-agnostic for consistency with the quickstart.

At Line 641, the README now says to configure a generic Model Provider, but the prerequisites still require an OpenAI API key specifically. That inconsistency can mislead users who use other providers.

Suggested wording update

- * An [OpenAI API key](https://platform.openai.com/)
+ * API credentials for your selected **Model Provider**

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/Social` Media
Agent.json at line 641, The README's prerequisites are inconsistent: the
"description" field currently names "An OpenAI API key" while the Quick start
refers generically to "Model Provider"; update the prerequisites to be
provider-agnostic (e.g., "An API key for your chosen model provider (for
example, an OpenAI API key)") so it matches the generic Model Provider wording
used elsewhere in the Social Media Agent.json description/README.

src/backend/base/langflow/initial_setup/starter_projects/Image Sentiment Analysis.json-701-701 (1)

701-701: ⚠️ Potential issue | 🟡 Minor

Consider clarifying prerequisites for multi-provider support.

The Prerequisites section lists "OpenAI API Key" specifically, while the Quick start section uses the generic term "Model Provider." Since this template supports multiple providers (Anthropic, Ollama, Google Generative AI, IBM WatsonX), consider updating the Prerequisites section to be provider-agnostic or note that OpenAI is just one option.

For example:

## Prerequisites

* API credentials for your chosen Model Provider (e.g., [OpenAI API Key](https://platform.openai.com/), Anthropic API Key, etc.)

This would align better with the generalized Quick start instructions and avoid confusion for users selecting non-OpenAI providers.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/Image` Sentiment
Analysis.json at line 701, Update the README "description" in Image Sentiment
Analysis starter (the JSON "description" string) to make Prerequisites
provider-agnostic: replace the single bullet "* [OpenAI API
Key](https://platform.openai.com/)" with a generic entry like "* API credentials
for your chosen Model Provider (e.g., OpenAI API Key, Anthropic API Key, Ollama,
Google Generative AI, IBM WatsonX)" so the Prerequisites match the generalized
"Model Provider" wording used elsewhere.

src/backend/base/langflow/initial_setup/starter_projects/Travel Planning Agents.json-750-750 (1)

750-750: ⚠️ Potential issue | 🟡 Minor

Fix duplicated step number in Quick start instructions (Line 750).

The list shows 1, 2, 2; the last step should be 3 for clarity in onboarding.

✏️ Proposed fix

-            "description": "# 📖 README\n\nThe travel planning system is a smart setup that uses several specialized Agent components to help plan incredible trips. Imagine each agent as a travel expert focusing on a part of your journey. Here's how it works:\nEach agent has a role defined in the **Agent Instructions** and relevant **Tools** attached. The user submits a query through the **Chat Input**, and the three agents create a complete travel plan based on the user's query.\n\n## Quick start\n1. Configure your **Model Provider** with your API credentials.\n2. Add your **Search API** key to the Search API component.\n2. Run the flow in the **Playground**.",
+            "description": "# 📖 README\n\nThe travel planning system is a smart setup that uses several specialized Agent components to help plan incredible trips. Imagine each agent as a travel expert focusing on a part of your journey. Here's how it works:\nEach agent has a role defined in the **Agent Instructions** and relevant **Tools** attached. The user submits a query through the **Chat Input**, and the three agents create a complete travel plan based on the user's query.\n\n## Quick start\n1. Configure your **Model Provider** with your API credentials.\n2. Add your **Search API** key to the Search API component.\n3. Run the flow in the **Playground**.",

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/Travel` Planning
Agents.json at line 750, Edit the "description" field's Quick start numbered
list in the Travel Planning Agents JSON: change the duplicate step number from
the second "2." to "3." so the list reads "1., 2., 3." under the "Quick start"
section inside the description string.

src/backend/base/langflow/initial_setup/starter_projects/Meeting Summary.json-2783-2783 (1)

2783-2783: ⚠️ Potential issue | 🟡 Minor

Use provider-neutral setup wording in the README note.

Line 2783 still requires an OpenAI API Key and names GPT-4, which conflicts with the flow’s Model Provider-based setup and can confuse users.

✏️ Proposed wording update

- "description": "# 📖 README\nThis flow automatically transcribes and summarizes meetings by converting audio recordings into concise summaries using **AssemblyAI** and **OpenAI GPT-4**. \n\n## Prerequisites\n\n- **[AssemblyAI API Key](https://www.assemblyai.com/)**\n- **[OpenAI API Key](https://platform.openai.com/)**\n\n## Quick start\n\n1. Upload an audio file. Most common audio file formats are [supported](https://github.com/langflow-ai/langflow/blob/main/src/backend/base/langflow/components/assemblyai/assemblyai_start_transcript.py#L27).\n2. To run the summary generator flow, click **Playground**.\n\nThe flow transcribes the audio using **AssemblyAI**.\nThe transcript is formatted for AI processing.\nThe **GPT-4** model extracts key points and insights.\nThe summarized meeting details are displayed in a chat-friendly format.\n\n\n\n",
+ "description": "# 📖 README\nThis flow automatically transcribes and summarizes meetings by converting audio recordings into concise summaries using **AssemblyAI** and a **Language Model**.\n\n## Prerequisites\n\n- **[AssemblyAI API Key](https://www.assemblyai.com/)**\n- **Model Provider API credentials**\n\n## Quick start\n\n1. Upload an audio file. Most common audio file formats are [supported](https://github.com/langflow-ai/langflow/blob/main/src/backend/base/langflow/components/assemblyai/assemblyai_start_transcript.py#L27).\n2. Configure your **Model Provider** with your API credentials.\n3. To run the summary generator flow, click **Playground**.\n\nThe flow transcribes the audio using **AssemblyAI**.\nThe transcript is formatted for AI processing.\nThe selected **Language Model** extracts key points and insights.\nThe summarized meeting details are displayed in a chat-friendly format.\n",

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/Meeting`
Summary.json at line 2783, Update the README description string in the Meeting
Summary flow to use provider-neutral wording: replace the explicit "OpenAI API
Key" and references to "GPT-4" with generic terms like "Model provider API key"
and "a compatible LLM from your selected model provider" (while keeping
AssemblyAI-specific audio prereq intact); modify the quick-start steps and the
summary sentences in the description field so they reference the flow's model
provider selection (e.g., "model provider" or "selected LLM") instead of
hardcoding OpenAI/GPT-4 so the text aligns with the Model Provider-based setup.

src/backend/base/langflow/initial_setup/starter_projects/Search agent.json-821-821 (1)

821-821: ⚠️ Potential issue | 🟡 Minor

Fix corrupted README heading character.

The heading currently renders as # � README, which is a user-facing text glitch. Replace it with the intended heading character.

🛠️ Proposed fix

-            "description": "# � README\nThis template connects the **Search Point** endpoint from [ScrapeGraphAI](https://scrapegraphai.com) to an **Agent** component.\n\n## Prerequisites\n\n* [OpenAI API key](https://platform.openai.com/docs/overview)\n* [ScrapeGraphAI API key](https://dashboard.scrapegraphai.com)\n\n## Quick start\n\n1. Configure your **Model Provider** with your API credentials.\n\n2. Add your **ScrapeGraphAI API key** to the **ScrapeGraphSearchApi** component.\n\n3. Open the **Playground** and ask your Agent a question. The Agent uses ScrapeGraph as a tool to answer you.",
+            "description": "# 📖 README\nThis template connects the **Search Point** endpoint from [ScrapeGraphAI](https://scrapegraphai.com) to an **Agent** component.\n\n## Prerequisites\n\n* [OpenAI API key](https://platform.openai.com/docs/overview)\n* [ScrapeGraphAI API key](https://dashboard.scrapegraphai.com)\n\n## Quick start\n\n1. Configure your **Model Provider** with your API credentials.\n\n2. Add your **ScrapeGraphAI API key** to the **ScrapeGraphSearchApi** component.\n\n3. Open the **Playground** and ask your Agent a question. The Agent uses ScrapeGraph as a tool to answer you.",

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/Search` agent.json
at line 821, The README description contains a corrupted heading " # � README";
update the description string in Search agent.json (the "description" field) to
replace the corrupted character with the intended heading — e.g., change " # �
README" to " # README" (or to the correct emoji if one was intended, such as " #
📘 README") so the heading renders properly in the agent template.

src/backend/base/langflow/initial_setup/starter_projects/Sequential Tasks Agents.json-2314-2314 (1)

2314-2314: ⚠️ Potential issue | 🟡 Minor

Avoid claiming this query bypasses the financial agent path.

Line 2314 says a generic prompt “doesn't trigger the financial research agent,” but this flow is statically chained, so that wording is misleading for users.

✏️ Suggested wording update

-... In contrast, asking the agent, "Tell me about Tesla" isn't as useful because it doesn't trigger the financial research agent or provide specific talking points for the other agents to research.
+... In contrast, asking the agent, "Tell me about Tesla" can still run through the full flow, but it usually yields weaker financial analysis because goals and talking points are underspecified.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/Sequential` Tasks
Agents.json at line 2314, Update the "description" README text (the description
field in Sequential Tasks Agents.json) to remove the misleading claim that a
generic prompt "doesn't trigger the financial research agent" and instead state
that this template uses a statically chained sequence of agents so all agents
run in order; replace the sentence with a clearer suggestion such as
recommending more specific, finance-focused prompts to make the financial
analysis agent’s output more useful while noting the flow still executes all
agents in sequence.

src/backend/base/langflow/initial_setup/starter_projects/Twitter Thread Generator.json-1647-1647 (1)

1647-1647: ⚠️ Potential issue | 🟡 Minor

Use provider-agnostic wording in the README note.

Line 1647 still says “The OpenAI model will create the thread…”, which conflicts with the new generic “Model Provider” guidance and can mislead users on other providers.

Suggested text tweak

-   - The OpenAI model will create the thread based on your specifications
+   - The configured model provider will create the thread based on your specifications

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/Twitter` Thread
Generator.json at line 1647, Replace the provider-specific sentence inside the
"description" field that reads “The OpenAI model will create the thread based on
your specifications” with provider-agnostic wording; update the README text in
Twitter Thread Generator.json (the description property) to something like “The
selected model will create the thread based on your specifications” or “The
chosen model provider will create the thread based on your specifications” so
the note aligns with generic Model Provider guidance.

🧹 Nitpick comments (2)

src/backend/base/langflow/initial_setup/starter_projects/Hybrid Search RAG.json (1)

1109-1109: Keep prerequisite wording consistent with the provider-agnostic quick start.

Line 1109 mixes generic setup guidance ("Model Provider") with an OpenAI-specific prerequisite, which can confuse users choosing a different provider.

✏️ Suggested wording adjustment

-* An [OpenAI API key](https://platform.openai.com/)
+* A **Model Provider API key** (for example, [OpenAI](https://platform.openai.com/))

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/Hybrid` Search
RAG.json at line 1109, The README description in the "description" field of
Hybrid Search RAG.json uses an OpenAI-specific prerequisite ("An OpenAI API
key") while elsewhere the quick start is provider-agnostic; update the wording
to be generic (e.g., "A model provider API key" or "API credentials for your
chosen model provider") so prerequisites match the provider-agnostic quick start
and remove OpenAI-specific mention; edit the "description" value in Hybrid
Search RAG.json to replace the OpenAI-specific line and ensure other references
to "Model Provider" remain consistent.

src/backend/base/langflow/initial_setup/starter_projects/Knowledge Ingestion.json (1)

321-321: Optional: align section structure with the other README-style templates.

Line 321 already has good content, but adding explicit ## Quick start (and optionally ## Next steps) headings would make this template match the standardized format more closely.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/Knowledge`
Ingestion.json at line 321, The README string in the Knowledge Ingestion starter
(the "description" value in the JSON) should be updated to include explicit
section headings matching other templates: insert a "## Quick start" heading
before the numbered steps (1–4) and optionally add a "## Next steps" heading
after the steps to mirror the standardized README structure; update the
"description" text in the Knowledge Ingestion.json entry (the JSON field labeled
"description") to include these headings while preserving the existing content
and formatting.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/backend/base/langflow/initial_setup/starter_projects/Nvidia` Remix.json:
- Line 2409: The README incorrectly states no extra configuration is needed and
references the wrong node label; update the README description to instruct users
to open the Agent node and select a Language Model (and add provider credentials
if required) before running, and change any references of "RTX Remix MCP
Connection" to the actual node label "MCP Connection" and update the "Testing
the Connection" steps to match the suggested four-step verification (open
project, locate MCP Connection node, click refresh, verify REST API tools
appear).

---

Minor comments:
In `@src/backend/base/langflow/initial_setup/starter_projects/Basic` Prompt
Chaining.json:
- Line 1232: The README description in the "description" field of Basic Prompt
Chaining.json is OpenAI-specific by mentioning "OpenAI API Key"; update that
line to be provider-agnostic (e.g., "API credentials for your chosen Model
Provider" or "Model Provider credentials (API key/token)"), remove the
OpenAI-only link, and ensure the prerequisites section references "Model
Provider" consistently so other providers are not misled.

In `@src/backend/base/langflow/initial_setup/starter_projects/Blog` Writer.json:
- Line 772: The README description's Prerequisites still mentions "An [OpenAI
API key]" which is inconsistent with the provider-agnostic "Model Provider"
wording; update the "description" value in the Blog Writer.json (the README
string) to a generic prerequisite such as "A model provider API key or
credentials (configure your Model Provider in the app)" so it no longer
references OpenAI by name and matches the Quick start language.

In `@src/backend/base/langflow/initial_setup/starter_projects/Document` Q&A.json:
- Line 663: In the "description" string of the Document Q&A starter (the
"description" value in Document Q&A.json) remove the double spaces in the Quick
start step so the line reads "2. In the **File** component, select a file you
want to load." (replace the current "2.  In the **File** component, select a
file  you want to load."), ensuring both the space after "2." and the extra
space before "you" are reduced to a single space.

In `@src/backend/base/langflow/initial_setup/starter_projects/Financial` Report
Parser.json:
- Line 689: Update the "description" string in the Financial Report Parser
template (the "description" field in Financial Report Parser.json) to fix the
grammar: replace the phrase "converts extracted data into a messages" with
"converts extracted data into messages" (or "into a message") inside the README
text so the user-visible sentence reads correctly.

In `@src/backend/base/langflow/initial_setup/starter_projects/Image` Sentiment
Analysis.json:
- Line 701: Update the README "description" in Image Sentiment Analysis starter
(the JSON "description" string) to make Prerequisites provider-agnostic: replace
the single bullet "* [OpenAI API Key](https://platform.openai.com/)" with a
generic entry like "* API credentials for your chosen Model Provider (e.g.,
OpenAI API Key, Anthropic API Key, Ollama, Google Generative AI, IBM WatsonX)"
so the Prerequisites match the generalized "Model Provider" wording used
elsewhere.

In `@src/backend/base/langflow/initial_setup/starter_projects/Invoice`
Summarizer.json:
- Line 120: Update the "description" field in Invoice Summarizer.json to make
the prerequisites provider-agnostic: replace the specific "An OpenAI API key"
line with wording like "A Model Provider API key (e.g., OpenAI, Anthropic, or
other supported provider)" so the quickstart aligns with the earlier instruction
to configure a generic Model Provider; target the "description" property in the
JSON to perform this change.

In `@src/backend/base/langflow/initial_setup/starter_projects/Meeting`
Summary.json:
- Line 2783: Update the README description string in the Meeting Summary flow to
use provider-neutral wording: replace the explicit "OpenAI API Key" and
references to "GPT-4" with generic terms like "Model provider API key" and "a
compatible LLM from your selected model provider" (while keeping
AssemblyAI-specific audio prereq intact); modify the quick-start steps and the
summary sentences in the description field so they reference the flow's model
provider selection (e.g., "model provider" or "selected LLM") instead of
hardcoding OpenAI/GPT-4 so the text aligns with the Model Provider-based setup.

In `@src/backend/base/langflow/initial_setup/starter_projects/News`
Aggregator.json:
- Line 828: The README's prerequisites are provider-specific; update the
"description" field in News Aggregator.json (the "description" string) to
replace the "OpenAI API Key" entry with a provider-neutral phrase such as "Model
Provider API credentials" (remove or replace the OpenAI-specific link) so the
prerequisites match the generic "Model Provider" wording used elsewhere.

In `@src/backend/base/langflow/initial_setup/starter_projects/Pokédex` Agent.json:
- Line 679: Update the README "description" field to make prerequisites
provider-agnostic by replacing "An OpenAI API key" with a neutral phrase like
"An API key for your chosen model provider" (or "Model provider API key (e.g.,
OpenAI)") inside the "Prerequisites" bullet, and ensure consistent spelling of
"Pokédex" throughout the description (e.g., replace any "Pokedex API"
occurrences). Target the README/description JSON string (the "description"
field) and the "Prerequisites" section to apply these text changes.

In `@src/backend/base/langflow/initial_setup/starter_projects/Price` Deal
Finder.json:
- Line 1514: Update the README text in the "description" field of Price Deal
Finder.json: fix the typo "searcn" -> "search", remove the stray closing
parenthesis after the sample query "iPhone 16 Pro 512 GB", and normalize the
component name to "AgentQL" everywhere (replace "Agent QL" with "AgentQL"); also
tidy list/bullet spacing so the quick start steps are consistently formatted as
separate lines/bullets and the final sentence reads clearly (e.g., "The Agent
returns a structured response to your search in the chat.").

In `@src/backend/base/langflow/initial_setup/starter_projects/Research`
Translation Loop.json:
- Line 896: Update the README description string (the "description" field in the
Research Translation Loop template) to remove explicit "OpenAI" mentions and
instead use neutral wording like "Language Model component" or "selected model
provider"; specifically replace phrases such as "translated into Portuguese by
the **OpenAI** model component" with "translated into Portuguese by the
**Language Model component** (or selected model provider)" and similarly update
any other occurrences in that description text to align with the generic "Model
Provider" terminology.

In `@src/backend/base/langflow/initial_setup/starter_projects/Search` agent.json:
- Line 821: The README description contains a corrupted heading " # � README";
update the description string in Search agent.json (the "description" field) to
replace the corrupted character with the intended heading — e.g., change " # �
README" to " # README" (or to the correct emoji if one was intended, such as " #
📘 README") so the heading renders properly in the agent template.

In `@src/backend/base/langflow/initial_setup/starter_projects/SEO` Keyword
Generator.json:
- Line 400: The README in the "description" field of SEO Keyword Generator.json
hardcodes "OpenAI API Key" which conflicts with the provider-agnostic "Model
Provider" text; update that sentence to a generic phrasing such as "Model
Provider API Key (your provider's API key)" and remove or replace the
OpenAI-specific link so the prerequisites are provider-agnostic; ensure the
"description" value consistently references "Model Provider" elsewhere in the
document.

In `@src/backend/base/langflow/initial_setup/starter_projects/Sequential` Tasks
Agents.json:
- Line 2314: Update the "description" README text (the description field in
Sequential Tasks Agents.json) to remove the misleading claim that a generic
prompt "doesn't trigger the financial research agent" and instead state that
this template uses a statically chained sequence of agents so all agents run in
order; replace the sentence with a clearer suggestion such as recommending more
specific, finance-focused prompts to make the financial analysis agent’s output
more useful while noting the flow still executes all agents in sequence.

In `@src/backend/base/langflow/initial_setup/starter_projects/Social` Media
Agent.json:
- Line 641: The README's prerequisites are inconsistent: the "description" field
currently names "An OpenAI API key" while the Quick start refers generically to
"Model Provider"; update the prerequisites to be provider-agnostic (e.g., "An
API key for your chosen model provider (for example, an OpenAI API key)") so it
matches the generic Model Provider wording used elsewhere in the Social Media
Agent.json description/README.

In `@src/backend/base/langflow/initial_setup/starter_projects/Text` Sentiment
Analysis.json:
- Line 769: The README still contains OpenAI-specific text; update it to be
provider-agnostic by removing references to "OpenAI API key" and "OpenAI Model
Component" and replacing them with neutral phrases like "Model provider
credentials" or "API key for your chosen model provider" and mention the actual
component name used in the flow (LanguageModelComponent) where appropriate; also
adjust the Quick start steps and prerequisites to refer generically to
configuring the Model Provider and loading data into the File Component, and
ensure prompts and final step reference the LanguageModelComponent (or "model
component") rather than OpenAI-specific wording.

In `@src/backend/base/langflow/initial_setup/starter_projects/Travel` Planning
Agents.json:
- Line 750: Edit the "description" field's Quick start numbered list in the
Travel Planning Agents JSON: change the duplicate step number from the second
"2." to "3." so the list reads "1., 2., 3." under the "Quick start" section
inside the description string.

In `@src/backend/base/langflow/initial_setup/starter_projects/Twitter` Thread
Generator.json:
- Line 1647: Replace the provider-specific sentence inside the "description"
field that reads “The OpenAI model will create the thread based on your
specifications” with provider-agnostic wording; update the README text in
Twitter Thread Generator.json (the description property) to something like “The
selected model will create the thread based on your specifications” or “The
chosen model provider will create the thread based on your specifications” so
the note aligns with generic Model Provider guidance.

In `@src/backend/base/langflow/initial_setup/starter_projects/Vector` Store
RAG.json:
- Line 1053: In the "description" string for the starter project (the README
text), fix the typo "Only the run the **Load Data** flow when you need to
populate..." to read "Only run the **Load Data** flow when you need to
populate..." by updating that sentence inside the description field so the
user-facing README is correct.

In `@src/backend/base/langflow/initial_setup/starter_projects/Youtube`
Analysis.json:
- Line 1964: There's a typo in the JSON "description" string for the README (the
Quick start section) — replace the misspelled "YoutTube" with the correct
"YouTube" in the value assigned to the description property (the long README
string containing "## Quick start" and the YouTube API instructions) so the
user-facing text reads "YouTube API key" and "YouTube" consistently.

---

Nitpick comments:
In `@src/backend/base/langflow/initial_setup/starter_projects/Hybrid` Search
RAG.json:
- Line 1109: The README description in the "description" field of Hybrid Search
RAG.json uses an OpenAI-specific prerequisite ("An OpenAI API key") while
elsewhere the quick start is provider-agnostic; update the wording to be generic
(e.g., "A model provider API key" or "API credentials for your chosen model
provider") so prerequisites match the provider-agnostic quick start and remove
OpenAI-specific mention; edit the "description" value in Hybrid Search RAG.json
to replace the OpenAI-specific line and ensure other references to "Model
Provider" remain consistent.

In `@src/backend/base/langflow/initial_setup/starter_projects/Knowledge`
Ingestion.json:
- Line 321: The README string in the Knowledge Ingestion starter (the
"description" value in the JSON) should be updated to include explicit section
headings matching other templates: insert a "## Quick start" heading before the
numbered steps (1–4) and optionally add a "## Next steps" heading after the
steps to mirror the standardized README structure; update the "description" text
in the Knowledge Ingestion.json entry (the JSON field labeled "description") to
include these headings while preserving the existing content and formatting.

---

ℹ️ Review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2fc6ca8 and 07dd950.

📒 Files selected for processing (34)

• .secrets.baseline
• src/backend/base/langflow/initial_setup/starter_projects/Basic Prompt Chaining.json
• src/backend/base/langflow/initial_setup/starter_projects/Basic Prompting.json
• src/backend/base/langflow/initial_setup/starter_projects/Blog Writer.json
• src/backend/base/langflow/initial_setup/starter_projects/Custom Component Generator.json
• src/backend/base/langflow/initial_setup/starter_projects/Document Q&A.json
• src/backend/base/langflow/initial_setup/starter_projects/Financial Report Parser.json
• src/backend/base/langflow/initial_setup/starter_projects/Hybrid Search RAG.json
• src/backend/base/langflow/initial_setup/starter_projects/Image Sentiment Analysis.json
• src/backend/base/langflow/initial_setup/starter_projects/Instagram Copywriter.json
• src/backend/base/langflow/initial_setup/starter_projects/Invoice Summarizer.json
• src/backend/base/langflow/initial_setup/starter_projects/Knowledge Ingestion.json
• src/backend/base/langflow/initial_setup/starter_projects/Knowledge Retrieval.json
• src/backend/base/langflow/initial_setup/starter_projects/Market Research.json
• src/backend/base/langflow/initial_setup/starter_projects/Meeting Summary.json
• src/backend/base/langflow/initial_setup/starter_projects/Memory Chatbot.json
• src/backend/base/langflow/initial_setup/starter_projects/News Aggregator.json
• src/backend/base/langflow/initial_setup/starter_projects/Nvidia Remix.json
• src/backend/base/langflow/initial_setup/starter_projects/Pokédex Agent.json
• src/backend/base/langflow/initial_setup/starter_projects/Portfolio Website Code Generator.json
• src/backend/base/langflow/initial_setup/starter_projects/Price Deal Finder.json
• src/backend/base/langflow/initial_setup/starter_projects/Research Agent.json
• src/backend/base/langflow/initial_setup/starter_projects/Research Translation Loop.json
• src/backend/base/langflow/initial_setup/starter_projects/SEO Keyword Generator.json
• src/backend/base/langflow/initial_setup/starter_projects/SaaS Pricing.json
• src/backend/base/langflow/initial_setup/starter_projects/Search agent.json
• src/backend/base/langflow/initial_setup/starter_projects/Sequential Tasks Agents.json
• src/backend/base/langflow/initial_setup/starter_projects/Simple Agent.json
• src/backend/base/langflow/initial_setup/starter_projects/Social Media Agent.json
• src/backend/base/langflow/initial_setup/starter_projects/Text Sentiment Analysis.json
• src/backend/base/langflow/initial_setup/starter_projects/Travel Planning Agents.json
• src/backend/base/langflow/initial_setup/starter_projects/Twitter Thread Generator.json
• src/backend/base/langflow/initial_setup/starter_projects/Vector Store RAG.json
• src/backend/base/langflow/initial_setup/starter_projects/Youtube Analysis.json

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Fix onboarding instructions to include required model setup and correct node label.

Line 2409 says no extra configuration is needed, but this flow still requires selecting a Language Model (and usually provider credentials) on the Agent node. Also, the text references “RTX Remix MCP Connection,” while the node here is labeled MCP Connection. This can block or confuse first-run setup.

Suggested README wording update

## Getting Started

Once prerequisites are met, complete this configuration in Langflow:

1. Open the **Agent** node.
2. Select a **Language Model** provider.
3. Add provider credentials if your selected provider requires them.

### Testing the Connection

1. Open the Langflow project.
2. Locate the **MCP Connection** node.
3. Click the **refresh** button on the node.
4. Verify that RTX Remix REST API tools appear.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/backend/base/langflow/initial_setup/starter_projects/Nvidia` Remix.json
at line 2409, The README incorrectly states no extra configuration is needed and
references the wrong node label; update the README description to instruct users
to open the Agent node and select a Language Model (and add provider credentials
if required) before running, and change any references of "RTX Remix MCP
Connection" to the actual node label "MCP Connection" and update the "Testing
the Connection" steps to match the suggested four-step verification (open
project, locate MCP Connection node, click refresh, verify REST API tools
appear).

[Cristhianzl]

lgtm