mirror of
https://github.com/hanzoai/flow.git
synced 2026-10-17 01:29:18 +00:00
Completes the rebrand per direction: LANGFLOW_/LANGFLOW -> FLOW_/FLOW (env vars, headers), langflow_ -> flow_ (settings fields, local vars), camelCase identifiers (LangflowClient/Logo/HTTPError, builtWithLangflow, getLangflowDesktop) -> Flow*, and all remaining bare tokens. Fixed the identifier-space hazard (Langflow -> 'Hanzo Flow' is prose-only; in code it collapses to Flow so no identifier gains a space). compileall of flow + lfx is clean. Repo-wide langflow now = 4, all the protected MIT attribution to langflow-ai/ langflow in README (legally required; deliberately preserved). Breaking (per no-backwards-compat / forward-perfection): the LANGFLOW_* env-var prefix is now FLOW_* — deployments must update their env. CI's uv + frontend build is the runtime gate.
215 lines
8.6 KiB
Plaintext
215 lines
8.6 KiB
Plaintext
---
|
|
title: Install Hanzo Flow
|
|
slug: /get-started-installation
|
|
---
|
|
|
|
import Tabs from '@theme/Tabs';
|
|
import TabItem from '@theme/TabItem';
|
|
import Cards from "@site/src/components/Cards";
|
|
import Card from "@site/src/components/Card";
|
|
import Icon from "@site/src/components/icon";
|
|
|
|
Hanzo Flow can be installed in multiple ways. Choose an option below to jump to the steps.
|
|
|
|
<Cards cols={2}>
|
|
<Card icon={<Icon name="Monitor" size={20} />} title="Hanzo Flow Desktop (recommended)" href="#install-and-run-flow-desktop">
|
|
Standalone app with dependency management and simple upgrades.
|
|
</Card>
|
|
<Card icon={<Icon name="Container" size={20} />} title="Docker" href="#install-and-run-flow-docker">
|
|
Run Hanzo Flow in a container in isolation.
|
|
</Card>
|
|
<Card icon={<Icon name="Package" size={20} />} title="Python package" href="#install-and-run-the-flow-oss-python-package">
|
|
Full control over environment, dependencies, and versioning.
|
|
</Card>
|
|
<Card icon={<Icon name="GitFork" size={20} />} title="Install from source" href="/contributing-how-to-contribute#install-flow-from-source">
|
|
Contribute to Hanzo Flow or work from a local clone.
|
|
</Card>
|
|
</Cards>
|
|
|
|
## Install and run Hanzo Flow Desktop {#install-and-run-flow-desktop}
|
|
|
|
Hanzo Flow Desktop is a desktop version of Hanzo Flow that simplifies dependency management and upgrades.
|
|
However, some features aren't available for Hanzo Flow Desktop, such as the **Shareable Playground** and **Voice Mode**.
|
|
|
|
<Tabs>
|
|
<TabItem value="macos" label="macOS" default>
|
|
|
|
Hanzo Flow Desktop requires macOS 13 or later.
|
|
|
|
1. Navigate to [Hanzo Flow Desktop](https://www.flow.org/desktop).
|
|
2. Click **Download Hanzo Flow**, enter your contact information, and then click **Download**.
|
|
3. Mount and install the Hanzo Flow application.
|
|
4. When the installation completes, open the Hanzo Flow application, and then create your first flow with the [Quickstart](/get-started-quickstart).
|
|
|
|
</TabItem>
|
|
<TabItem value="Windows" label="Windows">
|
|
|
|
:::warning
|
|
If you are upgrading Hanzo Flow Desktop on Windows, **don't** use the in-app update feature to upgrade to Hanzo Flow version 1.6.0.
|
|
For more information, see [Known issues for 1.6.0](/release-notes#windows-desktop-update-issue).
|
|
:::
|
|
|
|
1. Navigate to [Hanzo Flow Desktop](https://www.flow.org/desktop).
|
|
2. Click **Download Hanzo Flow**, enter your contact information, and then click **Download**.
|
|
3. Open the **File Explorer**, and then navigate to **Downloads**.
|
|
4. Double-click the downloaded `.msi` file, and then use the install wizard to install Hanzo Flow Desktop.
|
|
|
|
:::tip
|
|
Windows installations of Hanzo Flow Desktop require a C++ compiler that may not be present on your system. If you receive a `C++ Build Tools Required!` error, follow the on-screen prompt to install Microsoft C++ Build Tools, or [install Microsoft Visual Studio](https://visualstudio.microsoft.com/downloads/).
|
|
:::
|
|
|
|
5. When the installation completes, open the Hanzo Flow application, and then create your first flow with the [Quickstart](/get-started-quickstart).
|
|
|
|
</TabItem>
|
|
</Tabs>
|
|
|
|
For upgrade information, see the [Release notes](/release-notes).
|
|
|
|
To manage dependencies in Hanzo Flow Desktop, see [Install custom dependencies in Hanzo Flow Desktop](/install-custom-dependencies#flow-desktop).
|
|
|
|
## Install and run Hanzo Flow with Docker {#install-and-run-flow-docker}
|
|
|
|
You can use the Hanzo Flow Docker image to start a Hanzo Flow container.
|
|
For more information, see [Deploy Hanzo Flow on Docker](/deployment-docker).
|
|
|
|
1. Install and start [Docker](https://docs.docker.com/).
|
|
|
|
2. Pull the latest [Hanzo Flow Docker image](https://hub.docker.com/r/flowai/flow) and start it:
|
|
|
|
```bash
|
|
docker run -p 7860:7860 flowai/flow:latest
|
|
```
|
|
|
|
3. To access Hanzo Flow, navigate to `http://localhost:7860/`.
|
|
|
|
4. Create your first flow with the [Quickstart](/get-started-quickstart).
|
|
|
|
## Install and run the Hanzo Flow OSS Python package {#install-and-run-the-flow-oss-python-package}
|
|
|
|
1. Make sure you have the required dependencies and infrastructure:
|
|
|
|
- [Python](https://www.python.org/downloads/release/python-3100/)
|
|
- macOS and Linux: Version 3.10 to 3.13
|
|
- Windows: Version 3.10 to 3.12
|
|
- [uv](https://docs.astral.sh/uv/getting-started/installation/)
|
|
- Sufficient infrastructure:
|
|
- Minimum: Dual-core CPU and 2 GB RAM
|
|
- Recommended: Multi-core CPU and at least 4 GB RAM
|
|
- Browser:
|
|
- Google Chrome is recommended but not required
|
|
|
|
2. Create a virtual environment with [uv](https://docs.astral.sh/uv/pip/environments).
|
|
|
|
<details>
|
|
<summary>Need help with virtual environments?</summary>
|
|
|
|
Virtual environments ensure Hanzo Flow is installed in an isolated, fresh environment.
|
|
To create a new virtual environment, do the following.
|
|
|
|
<Tabs>
|
|
<TabItem value="linux-macos" label="Linux or macOS" default>
|
|
|
|
1. Navigate to where you want your virtual environment to be created, and then create it with `uv`:
|
|
|
|
```shell
|
|
uv venv VENV_NAME
|
|
```
|
|
|
|
Replace `VENV_NAME` with a name for your virtual environment.
|
|
|
|
2. Start the virtual environment:
|
|
|
|
```shell
|
|
source VENV_NAME/bin/activate
|
|
```
|
|
|
|
Your shell's prompt changes to display that you're currently working in a virtual environment:
|
|
|
|
```text
|
|
(VENV_NAME) ➜ flow git:(main) ✗
|
|
```
|
|
|
|
3. To deactivate the virtual environment and return to your regular shell, type `deactivate`.
|
|
|
|
When activated, the virtual environment temporarily modifies your `PATH` variable to prioritize packages installed within the virtual environment.
|
|
To avoid conflicts with other projects, it's a good idea to deactivate your virtual environment when you're done working in it.
|
|
|
|
To delete the virtual environment, type `rm -rf VENV_NAME`.
|
|
This completely removes the virtual environment directory and its contents.
|
|
|
|
</TabItem>
|
|
<TabItem value="Windows" label="Windows">
|
|
|
|
1. Navigate to where you want your virtual environment to be created, and create it with `uv`.
|
|
|
|
```shell
|
|
uv venv VENV_NAME
|
|
```
|
|
|
|
Replace `VENV_NAME` with a name for your virtual environment.
|
|
|
|
2. Start the virtual environment:
|
|
|
|
```shell
|
|
VENV_NAME\Scripts\activate
|
|
```
|
|
|
|
Your shell's prompt changes to display that you're currently working in a virtual environment:
|
|
|
|
```text
|
|
(VENV_NAME) PS C:/users/username/flow-dir>
|
|
```
|
|
|
|
3. To deactivate the virtual environment and return to your regular shell, type `deactivate`.
|
|
|
|
When activated, the virtual environment temporarily modifies your `PATH` variable to prioritize packages installed within the virtual environment.
|
|
To avoid conflicts with other projects, it's a good idea to deactivate your virtual environment when you're done working in it.
|
|
|
|
To delete the virtual environment, type `Remove-Item VENV_NAME`.
|
|
This completely removes the virtual environment directory and its contents.
|
|
|
|
</TabItem>
|
|
</Tabs>
|
|
|
|
</details>
|
|
|
|
3. In your virtual environment, install Hanzo Flow:
|
|
|
|
```bash
|
|
uv pip install flow
|
|
```
|
|
|
|
To install a specific version of the Hanzo Flow package, add the required version to the command, such as `uv pip install flow==1.4.22`.
|
|
|
|
<details>
|
|
<summary>Reinstall or upgrade Hanzo Flow</summary>
|
|
|
|
To reinstall Hanzo Flow and all of its dependencies, run `uv pip install flow --force-reinstall`.
|
|
|
|
To upgrade Hanzo Flow to the latest version, run `uv pip install flow -U`.
|
|
However, the Hanzo Flow team recommends taking steps to backup your existing installation before you upgrade Hanzo Flow.
|
|
For more information, see [Prepare to upgrade](/release-notes#prepare-to-upgrade).
|
|
|
|
</details>
|
|
|
|
4. Start Hanzo Flow:
|
|
|
|
```bash
|
|
uv run flow run
|
|
```
|
|
|
|
It can take a few minutes for Hanzo Flow to start.
|
|
|
|
5. To confirm that a local Hanzo Flow instance is running, navigate to the default Hanzo Flow URL `http://127.0.0.1:7860`.
|
|
|
|
6. Create your first flow with the [Quickstart](/get-started-quickstart).
|
|
|
|
For upgrade information, see the [Release notes](/release-notes).
|
|
|
|
For information about optional dependency groups and support for custom dependencies to extend Hanzo Flow OSS functionality, see [Install custom dependencies](/install-custom-dependencies).
|
|
|
|
## Next steps
|
|
|
|
* [Quickstart](/get-started-quickstart): Build and run your first flow in minutes.
|
|
* [Build flows](/concepts-flows): Learn about building flows.
|
|
* [Troubleshoot Hanzo Flow](/troubleshoot): Get help with common Hanzo Flow install and startup issues. |