Flow

Launch the Langflow visual workflow builder with PraisonAI Agent + AgentTeam components pre-loaded

The praisonai flow command launches Langflow with PraisonAI components pre-loaded, and provides YAML ↔ Langflow JSON conversion utilities.

Diagram

🖥️ praisonai flow

🌐 Langflow
:7860

👁️ Browser UI

🤖 Agent

🤝 Agent Team

Requirements

ItemValue
Python3.11 / 3.12 / 3.13 (3.13 fixed in PraisonAI#5103)
Install size~500MB (Langflow + a2a-sdk + fastapi stack)
First-boot on Windows~5 minutes (Langflow migrations + cache)
First-boot on macOS/LinuxTypically < 2 minutes

Quick Start

  1. Install
    bash
    pip install "praisonai[flow]"
  2. Launch
    bash
    praisonai flow
  3. Build visually

    Open http://localhost:7860 and drag Agent / Agent Team components from the PraisonAI sidebar.


How It Works

Diagram
PraisonAI ComponentsLangflowpraisonai flowUserPraisonAI ComponentsLangflowpraisonai flowUserpraisonai flowlangflow run + LANGFLOW_COMPONENTS_PATHVisual UI on :7860Configure Agent / Agent TeamWorkflow result
PhaseDescription
Installpip install "praisonai[flow]" pulls Langflow and requests
LaunchCLI sets LANGFLOW_COMPONENTS_PATH to PraisonAI components
BuildDrag Agent and Agent Team nodes in the browser
Exportpraisonai flow export <flow_id> converts back to YAML

Subcommands

praisonai flow

Start the visual builder.

FlagTypeDefaultDescription
--port, -pint7860Port to listen on
--host, -Hstr127.0.0.1Host to bind to (use 0.0.0.0 to expose)
--env-filestrNonePath to a .env file Langflow should load
--no-openflagFalseDon’t open the browser on start
--log-level, -lstrerrordebug, info, warning, error, critical
--backend-onlyflagFalseRun backend API only (no frontend UI)
--components-pathstrNoneExtra custom components directory (appended to PraisonAI’s)
bash
praisonai flow --host 0.0.0.0 --port 8080
Env var pre-setEffect on LANGFLOW_COMPONENTS_PATH
unset`

| | set to /x |

,/x | | set to /x,/y |

,/x,/y (works) | | set to /x;/y |

,/x;/y — /x;/y` is treated as a single path by Langflow (broken) |

praisonai flow import

Convert PraisonAI YAML → Langflow JSON and upload.

FlagTypeDefaultDescription
yaml_pathstr—Path to YAML workflow file (positional)
--urlstrhttp://localhost:7860Langflow server URL
--dry-runflagFalsePreview JSON without uploading
--openflagFalseOpen the imported flow in the browser
--output, -ostrNoneSave JSON to file instead of uploading
bash
praisonai flow import my_workflow.yaml --open

praisonai flow export

Download a Langflow flow and convert back to YAML or JSON.

FlagTypeDefaultDescription
flow_idstr—Flow ID to export (positional)
--output, -ostr<flow_name>.<ext>Output file path
--urlstrhttp://localhost:7860Langflow server URL
--formatstryamlOutput format: yaml or json
bash
praisonai flow export abc-123-def -o my_workflow.yaml

praisonai flow list

List flows on a running Langflow server.

FlagTypeDefaultDescription
--urlstrhttp://localhost:7860Langflow server URL
--search, -sstrNoneSearch flows by name or description
bash
praisonai flow list --search research

praisonai flow version

Show installed Langflow version.

bash
praisonai flow version

Common Patterns

bash
# YAML → visual editor round-trip
praisonai flow                                   # 1. start the builder
praisonai flow import my_workflow.yaml --open    # 2. push YAML in
# (edit in browser, copy the flow ID from the URL)
praisonai flow export <flow_id> -o my_workflow.yaml   # 3. pull edits back to YAML

# Preview the converted JSON without uploading
praisonai flow import my_workflow.yaml --dry-run

# Run on a custom port / expose to LAN
praisonai flow --host 0.0.0.0 --port 8080

# Headless / API-only deploy
praisonai flow --backend-only --no-open

Best Practices

Keep YAML as source of truth

Always export back to YAML for version control after visual edits.

Use –dry-run before uploading

Preview JSON conversion with praisonai flow import workflow.yaml --dry-run before pushing to a running server.

Add custom components with –components-path

Extend the sidebar with your own Langflow components via --components-path /path/to/components.

Run –backend-only for headless deployments

Skip the UI in CI or Docker with praisonai flow --backend-only --no-open.

First boot on Windows is slow — that's expected

Langflow runs Alembic migrations and warms a component cache on first launch, which takes about 5 minutes on Windows. Watch for Uvicorn running on http://127.0.0.1:<port> in the log tail; subsequent starts are under 60s.


Related