Langflow release notes

This page summarizes significant changes to Langflow in each release. For all changes, see the Changelog.

Due to strict SemVer requirements, Langflow Desktop can have different patch versions than the core Langflow OSS Python package, but the major and minor versions are aligned.

Prepare to upgrade

important

Whenever possible, the Langflow team recommends installing new Langflow versions in a new virtual environment or VM before upgrading your primary installation. This allows you to import flows from your existing installation and test them in the new version without disrupting your existing installation. In the event of breaking changes or bugs, your existing installation is preserved in a stable state.

To avoid the impact of potential breaking changes and test new versions, the Langflow team recommends the following upgrade process:

1. Recommended: Export your projects to create backups of your flows:

   
   

   _10

   curl -X GET \

   _10

   "$LANGFLOW_SERVER_URL/api/v1/projects/download/$PROJECT_ID" \

   _10

   -H "accept: application/json" \

   _10

   -H "x-api-key: $LANGFLOW_API_KEY"

   
   

   To export flows from the visual editor, see Import and export flows.

2. Install the new version:

   • Langflow OSS Python package: Install the new version in a new virtual environment. For instructions, see Install and run the Langflow OSS Python package.
   • Langflow Docker image: Run the new image in a separate container.
   • Langflow Desktop: To upgrade in place, open Langflow Desktop, and then click Upgrade Available in the Langflow header. If you want to isolate the new version, you must install Langflow Desktop on a separate physical or virtual machine, and then import your flows to the new installation.

3. Import your flows to test them in the new version, upgrading components as needed.

   When upgrading components, you can use the Create backup flow before updating option if you didn't previously export your flows.

4. If you installed the new version in isolation, upgrade your primary installation after testing the new version.

   If you made changes to your flows in the isolated installation, you might want to export and import those flows back to your upgraded primary installation so you don't have to repeat the component upgrade process.

1.5.0

Highlights of this release include the following changes. For all changes, see the Changelog.

New features and enhancements

• Authentication changes

  To enhance security and ensure proper authentication for automatic login features, most API endpoints now require authentication with a Langflow API key, regardless of the AUTO_LOGIN setting. The only exceptions are the MCP endpoints /v1/mcp, /v1/mcp-projects, and /v2/mcp, which never require authentication. For more information, see API keys and authentication.

• Centralized Language Model and Embedding Model components

  The Language Model component and Embedding Model component are now core components for your LLM and embeddings flows. They support multiple models and model providers, and allow you to experiment with different models without swapping out single-provider components. Find them in the Components menu in the Models category.

  The single-provider components are still available for your flows in the Components menu in the Bundles section, and you can use them to replace the Language Model and Embedding Model core components, or connect them to the Agent component with the Custom provider option.

• MCP server one-click installation

  On your Langflow project's MCP server page, click Auto install to install your Langflow MCP server to MCP clients with just one click. The option to install with a JSON configuration file is available for macOS, Windows, and WSL. For more information, see Use Langflow as an MCP server.

• MCP server management

  You can now add, remove, and edit your MCP servers in the MCP Tools components and through your Langflow Settings page. For more information, see Use Langflow as an MCP client.

• Input schema replaces temporary overrides

  The Input schema pane replaces the need to manage tweak values in the API access pane. When you enable a parameter in the Input schema pane, the parameter is automatically added to your flow's code snippets, providing ready-to-use templates for making requests in your preferred programming language.

• Tools components are redistributed

  All components in the Tools category were moved to other component categories, such as Helpers and bundles, or marked as legacy.

  The MCP Tools component is now under the Agents category.

  Tools that performed the same function were combined into single components that support multiple providers, such as the Web Search component and the News Search component.

  For more information, see Tools components.

• Stability improvements

  General stability improvements and bug fixes for enhanced reliability. See an issue? Raise it on GitHub.

• New integrations and bundles

  • Cleanlab bundle

1.4.2

Highlights of this release include the following changes. For all changes, see the Changelog.

New features and enhancements

• Enhanced file and flow management system with improved bulk capabilities.
• Added the BigQuery component
• Added the Twelve Labs bundle
• Added the NVIDIA System Assistant component

Deprecations

• Deprecated the Combine Text component.

1.4.1

Highlights of this release include the following changes. For all changes, see the Changelog.

New features and enhancements

• Added an enhanced Breaking Changes feature to help update components without breaking flows after updating Langflow.

1.4.0

Highlights of this release include the following changes. For all changes, see the Changelog.

New features and enhancements

• Introduced MCP server functionality to serve Langflow tools to MCP-compatible clients.
• Renamed Folders to Projects in the visual editor.
• The /folders endpoints now redirect to /projects.

Deprecations

• Deprecated the Gmail, Google Drive, and Google Search components. For alternatives, see the Google bundle.

Earlier releases

See the Changelog.