Synopsis
Arguments
| Argument | Required | Description |
|---|---|---|
name | No | The name of the flow to stop. If omitted, Progflow uses the most recently modified lockfile. |
What it does
Resolve the flow name
If you provide a
name, Progflow looks for ~/.config/flow/<name>.lock.If you omit name, Progflow scans ~/.config/flow/ for .lock files and picks the one with the most recent modification time. If no lockfile is found, the command exits with code 1.Send SIGTERM to tracked processes
Progflow reads the PID list from the lockfile and sends
SIGTERM to each process. If a process is no longer running, the signal is silently ignored. Any other failure prints a warning but does not abort the command.Prompt for a context note (interactive mode only)
When stdin is a terminal, Progflow asks:If you answer The note is saved to the
y, it follows up with:note field in ~/.config/flow/<name>.json. You can read it back later with progflow note.If stdin is not a terminal (for example, when running in a script or CI), this prompt is skipped entirely.Example
Non-interactive mode
When stdin is piped or redirected, the note prompt is skipped automatically:The note prompt only appears in interactive terminal sessions. Scripts and automated pipelines are never blocked waiting for input.
Error cases
| Condition | Exit code | Message |
|---|---|---|
No name given and no active flow found | 1 | No active flow found |
| Named flow has no lockfile | 1 | No lock file found for flow '<name>' |
| Config or lockfile cannot be read/parsed | 2 | IO or JSON error |
Exit codes
| Code | Meaning |
|---|---|
0 | Flow stopped successfully |
1 | User error — no active flow, lockfile not found |
2 | IO or JSON parse error |
See also
progflow on— start a flowprogflow note— read the saved context note for a flow