`progflow: command not found`
`progflow: command not found`
Why it happens: The binary was installed to To make this permanent, add the same line to your shell profile (You can verify the binary is present and the path is correct by running:
~/.local/bin but that directory is not in your shell’s PATH.Fix: Add ~/.local/bin to your PATH for the current session:~/.bashrc, ~/.zshrc, or ~/.profile):`No active flow found`
`No active flow found`
Error message:Why it happens: You ran If you’re not sure which flows are configured, list them:
progflow off without specifying a name, and Progflow couldn’t find any active lockfile in ~/.config/flow/. This means no flow was started in this session, or the lockfile was already removed.Fix: Specify the flow name explicitly:`No lock file found for flow 'name'`
`No lock file found for flow 'name'`
Error message:Why it happens: You tried to stop a flow that was never started in the current session. Progflow requires a lockfile (written by If you just want to clean up state without starting the flow, you can safely ignore this error — there is nothing running to stop.
progflow on) to know which processes to terminate.Fix: If you want to start and then stop the flow, run:`Directory does not exist: /path/to/dir`
`Directory does not exist: /path/to/dir`
Error message:Why it happens: The This opens
directory field in your flow’s config points to a path that no longer exists. This typically happens when a project directory is moved, renamed, or deleted after the flow was created.Fix: Update the flow config with the correct path using progflow edit:~/.config/flow/<name>.json in your $EDITOR. Update the "directory" field to the correct path and save.Alternatively, edit the file directly:`No editor set. Set $EDITOR or $VISUAL`
`No editor set. Set $EDITOR or $VISUAL`
Error message:Why it happens: You ran To make this permanent, add it to your shell profile:Then retry:
progflow edit <name> but neither the $EDITOR nor the $VISUAL environment variable is set. Progflow uses these standard variables to know which editor to open for editing config files.Fix: Set $EDITOR for the current session:URLs not opening on Linux
URLs not opening on Linux
Why it happens: Progflow uses Fix: Install If Progflow also tries
xdg-open as its primary URL opener on Linux. If xdg-utils is not installed, the call fails silently and you may see:xdg-utils:xdg-open is installed but URLs still don’t open, check that a default browser is configured:gio open, firefox, chromium, and brave as fallbacks if xdg-open fails.Editor doesn't open when running `progflow on`
Editor doesn't open when running `progflow on`
Why it happens: The editor command stored in This usually means the editor binary is not in If that fails, check that the editor is installed and that its binary is in your Set
editorCmd failed to launch. Progflow prints a warning but continues:PATH, or the command is written incorrectly.Fix: First, test the command manually in your terminal:PATH. Then update the flow config:"editorCmd" to the exact command that works in your terminal, for example "nvim .", "code .", or "nano .".Build fails during installation
Build fails during installation
Why it happens: The install script builds Progflow from source using or:Fix: Check your Rust version:If Rust is missing or outdated, install the latest stable version via rustup:On Termux:Then re-run the installer:You also need a C compiler (
cargo. If Rust is not installed or the version is too old (Progflow requires Rust 1.70+), the build will fail.Symptoms:gcc or clang) and make. On Debian/Ubuntu: