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

docs: Audit admonitions, related links, and prerequisites for style and consistency (#9217)

Browse source 
* add some related links

* admonitions audit

* initial prereq audit

* standardize install LF prereqs

* some coderabbit
This commit is contained in:
April I. Murphy 2025-07-29 06:25:16 -07:00 • committed by GitHub
commit 575cde3e8d
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
47 changed files with 203 additions and 170 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/docs/Agents/agents-tools.mdx
View file

@ -175,4 +175,11 @@ Your flow should be visible in the response as a tool.
The connected flow returns an answer based on your question.
For example, a Basic Prompting flow connected as a tool returns a different result depending upon its LLM and prompt instructions.
![Run Flow as tool connected to an agent](/img/agent-example-run-flow-as-tool.png)
![Run Flow as tool connected to an agent](/img/agent-example-run-flow-as-tool.png)
## See also
* [**Agent** and **MCP Tools** components](/components-agents)
* [Use Langflow agents](/agents)
* [Use Langflow as an MCP client](/mcp-client)
* [Use Langflow as an MCP server](/mcp-server)

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

@ -96,7 +96,7 @@ You can configure the **Agent** component to use your preferred provider and mod
:::tip
Many optional **Agent** component input parameters are hidden by default in the visual editor.
You can view and toggle all parameters through the <Icon name="SlidersHorizontal" aria-hidden="true"/> **Controls** in the [component's header menu](/concepts-components#component-menus).
You can access all component parameters through the <Icon name="SlidersHorizontal" aria-hidden="true"/> **Controls** in the [component's header menu](/concepts-components#component-menus).
:::
### Provider and model
@ -154,9 +154,6 @@ For more information, see [Store chat memory](/memory#store-chat-memory) and [**
### Additional parameters
Many optional **Agent** component input parameters are hidden by default in the visual editor.
You can view and toggle all parameters through the <Icon name="SlidersHorizontal" aria-hidden="true"/> **Controls** in the [component's header menu](/concepts-components#component-menus).
With the **Agent** component, the available parameters can change depending on the selected provider and model.
For example, some models support additional modes, arguments, or features like chat memory and temperature.
@ -166,9 +163,16 @@ Some additional input parameters include the following:
* **Handle Parse Errors** (`handle_parsing_errors`): When enabled (`true`), this setting allows the agent to fix errors, like typos, when analyzing user input.
* **Verbose** (`verbose`): When enabled (`true`), this setting records detailed logging output for debugging and analysis.
To view and configure all parameters, click <Icon name="SlidersHorizontal" aria-hidden="true"/> **Controls** in the [component's header menu](/concepts-components#component-menus).
## Agent component output
The **Agent** component outputs a **Response** (`response`) that is [`Message` data](/data-types#message) containing the agent's raw response to the query.
Typically, this is passed to a **Chat Output** component to return the response in a human-readable format.
It can also be passed to other components if you need to process the response further before, or in addition to, returning it to the user.
It can also be passed to other components if you need to process the response further before, or in addition to, returning it to the user.
## See also
* [**Agent** and **MCP Tools** components](/components-agents)
* [Configure tools for agents](/agents-tools)