Local-first CLI for defining and running your project's workflows.
136
stars
535
commits
Go
primary language
Sep 1, 2026
updated
flow is a workflow manager for developers who work across many projects. One interface for all your scripts, secrets, and automation — no matter the stack.
Most projects come with their own Makefile, npm scripts, or shell scripts — each with different conventions, flags and undocumented quirks. AI-generated tools and side projects have made this worse. The real cost isn't running the scripts; it's remembering how everything works every time you switch contexts.
Flow sits above your projects, not inside them: one place to see, run, and compose everything — regardless of what's underneath.
# Install
curl -sSL https://install.flowexec.io | bash
# Add the examples workspace
flow workspace add examples https://github.com/flowexec/examples.git --set
# Explore all workflows in the TUI
flow browse
You'll have a real workspace with runnable examples immediately. No configuration needed.
See the full quickstart guide to define your own workflows.
flow complements existing CLI tools by adding multi-project organization, built-in security, and visual discovery to your automation toolkit.

# api.flow
executables:
- verb: deploy
name: staging
serial:
execs:
- cmd: npm run build
- cmd: docker build -t api:staging .
- ref: shared-tools/k8s:deploy-staging
- cmd: curl -f https://api-staging.example.com/health
- verb: backup
name: database
exec:
params:
- secretRef: database-url
envKey: DATABASE_URL
cmd: pg_dump $DATABASE_URL > backup-$(date +%Y%m%d).sql
# Run workflows
flow deploy staging
flow backup database
# Visual discovery
flow browse
Complete documentation at flowexec.io
Go
96.5%
Shell
3.1%
Local-first CLI for defining and running your project's workflows.
136
stars
535
commits
Go
primary language
Sep 1, 2026
updated
flow is a workflow manager for developers who work across many projects. One interface for all your scripts, secrets, and automation — no matter the stack.
Most projects come with their own Makefile, npm scripts, or shell scripts — each with different conventions, flags and undocumented quirks. AI-generated tools and side projects have made this worse. The real cost isn't running the scripts; it's remembering how everything works every time you switch contexts.
Flow sits above your projects, not inside them: one place to see, run, and compose everything — regardless of what's underneath.
# Install
curl -sSL https://install.flowexec.io | bash
# Add the examples workspace
flow workspace add examples https://github.com/flowexec/examples.git --set
# Explore all workflows in the TUI
flow browse
You'll have a real workspace with runnable examples immediately. No configuration needed.
See the full quickstart guide to define your own workflows.
flow complements existing CLI tools by adding multi-project organization, built-in security, and visual discovery to your automation toolkit.

# api.flow
executables:
- verb: deploy
name: staging
serial:
execs:
- cmd: npm run build
- cmd: docker build -t api:staging .
- ref: shared-tools/k8s:deploy-staging
- cmd: curl -f https://api-staging.example.com/health
- verb: backup
name: database
exec:
params:
- secretRef: database-url
envKey: DATABASE_URL
cmd: pg_dump $DATABASE_URL > backup-$(date +%Y%m%d).sql
# Run workflows
flow deploy staging
flow backup database
# Visual discovery
flow browse
Complete documentation at flowexec.io
Go
96.5%
Shell
3.1%