workflow

Think n8n, but for the command line. An AI-native workflow orchestrator that lives in your terminal.

Create a workflow with AI and run it — all from the terminal.

Stop losing one-liners to shell history. Stop rewriting the same maintenance scripts on every box.

workflow is a file-based workflow orchestrator for Linux built for the AI age. Like n8n gives you visual workflow automation in the browser, workflow gives you the same power in the terminal — parallel DAGs, sub-workflows, for-each loops, conditional branching, expression filters, a webhook REST API, step retries and timeouts, encrypted secrets, native notifications to 9 services — but with a TUI you can browse over SSH, a headless CLI for cron, and first-class integration with Claude Code, OpenAI Codex CLI, and Google Gemini CLI to generate, fix, and refine workflows using natural language. No web server to maintain. No Docker stack. Just a single binary.

Drop a .sh or .yaml file into ~/.config/workflow/ and it's immediately available to run, schedule, and track. No daemon. No database to set up. No YAML-hell configuration. Or skip the file entirely — describe what you need in English and let AI write it for you.

 workflow v0.4.0 ── 12 workflows ── 48 runs ── 2 failed

 Categories  Tasks                    Details
 > backup    ▲ db-full    ✓ 2d [sh]   #!/bin/bash
   deploy    · mysql-daily✗ 5h [yml]  pg_dump mydb > /tmp/mydb_$DATE.sql
   docker    ▽ s3-sync       [yml]    echo "Backup complete"
   k8s

 Log
 [14:32:01] ▶ dump — mysqldump --all-databases > /tmp/db.sql
 [14:32:03] ✓ dump (1850ms)

 r:run  d:dry-run  e:edit  w:new  a:ai  t:template  /:search  q:quit

Why workflow?

If you manage servers, you already have workflows — they're just scattered across shell histories, wiki pages, and half-remembered incantations. workflow gives them a proper home.

For the solo sysadmin managing a handful of boxes: stop re-typing docker system prune && docker compose pull && docker compose up -d every Tuesday. Save it once, run it from anywhere, get notified when you forget.

For the DevOps team maintaining production infrastructure: standardize runbooks as version-controlled YAML with dependency ordering, retries, timeouts, and cleanup steps. Sync them across machines via Git. Review run history when something breaks.

For the on-call engineer at 2am: browse 52 bundled templates covering sysadmin, Docker, Kubernetes, and Linux patching workflows. Don't remember the kubectl incantation for checking PV storage? It's already there.

For the AI-assisted operator: workflow is designed to work with AI coding tools, not around them. Claude Code, Codex CLI, and Gemini CLI can generate new workflows from a plain-English description, rewrite existing tasks ("add retries and error handling"), and auto-diagnose failures with one keypress. A bundled Claude Code skill lets you manage workflows entirely from AI conversations. The file-based, YAML-native design means AI tools can read and write workflows without any special adapters.

Quick start

# Install (download binary or build from source)
cargo install --path .

# Create your first task — it's just a shell script in a folder
mkdir -p ~/.config/workflow/backup
cat > ~/.config/workflow/backup/db-full.sh << 'EOF'
#!/bin/bash
pg_dump mydb > /tmp/mydb_$(date +%Y%m%d).sql
echo "Backup complete"
EOF

# Run it
workflow run backup/db-full

# Or browse everything interactively
workflow

That's it. No init command, no project file, no configuration. Every .sh and .yaml file in ~/.config/workflow/ is automatically discovered and organized by folder.

What makes it useful

Turn shell history into reusable tasks

Press w in the TUI to browse your recent shell history (zsh, bash, or fish). Select the commands you want, give it a name, and you have a workflow. The wizard auto-suggests a category based on the commands — docker commands go under docker/, kubectl commands under k8s/.

┌─ New Task from History ──────────────────────────────────┐
│ Filter: docker                                           │
│                                                          │
│   [x] docker compose up -d                    2h ago     │
│   [ ] docker ps --format "table {{.Names}}"   3h ago     │
│   [x] docker logs -f webapp                   5h ago     │
│                                                          │
│ Space: toggle  Enter: continue  /: filter  Esc: cancel   │
└──────────────────────────────────────────────────────────┘

AI-native workflow management

workflow treats AI CLI tools as first-class citizens. If claude (Claude Code), codex (OpenAI Codex CLI), or gemini (Google Gemini CLI) is on your PATH, you unlock four capabilities directly from the TUI:

Generate (a) — describe a task in plain English. "Set up daily postgres backup with S3 upload and Slack notification on failure." The AI generates executable YAML with proper step dependencies, error handling, and cleanup. Review the preview before saving.

Update (A) — select any existing task and describe what to change. "Add retry logic to the upload step", "parallelize the independent checks", "switch from rsync to rclone". The AI rewrites the full YAML while preserving your structure.

Fix (a after failure) — when a workflow fails, press a and AI analyzes the error output, diagnoses the root cause, and proposes a corrected YAML. No more staring at cryptic stderr at 2am.

Refine (r at preview) — iteratively improve any AI-generated result before saving. Each round sends the current YAML plus your instructions back to the AI. Repeat as many times as needed:

Preview → r → "add error handling" → Enter → (AI refines) → Preview
                                                               ↓
                                                    r → "also add logging" → Enter → ...

Press d at any preview stage to dry-run the workflow without saving — verify it works, then save or keep refining.

All of this works from the CLI too:

workflow ai-update backup/db-full --prompt "add error handling and retries"
workflow ai-update backup/db-full --prompt "parallelize steps" --dry-run
workflow ai-update backup/db-full --prompt "add cleanup" --save-as db-full-v2

The AI integration is intentionally tool-agnostic — workflow auto-detects whichever AI CLI you have installed and uses it transparently. The file-based YAML format means AI tools can also read and write workflows directly from outside the TUI, making workflow a natural fit for agentic coding sessions.

52 bundled templates ready to go

Don't start from scratch. Press t to browse templates covering real operational tasks:

Sysadmin — disk usage reports, SSL certificate expiry checks, SMART disk health, NTP sync verification, cron audit, SSH key audit, firewall review, failed services check, log cleanup, system updates, memory monitoring, port scanning, user audit, backup verification, CPU load checks, service status

Docker — container cleanup, compose status, image updates, log tailing, network inspection, resource limits, restart unhealthy containers, security scanning, volume backup

Kubernetes — cluster health, deployment status, failed pod diagnostics, namespace audit, PV storage, RBAC review, resource usage, secret/configmap audit, service endpoints

Patching — security-only patches, patch audit, kernel updates, rollback, compliance reports, unattended updates setup, package holds, reboot checks, changelog review, post-patch verification (Debian/Ubuntu, RHEL/Fedora, SUSE, Arch)

Templates support variables — fill in {{db_name}} or {{backup_path}} when you save. Fetch community templates from GitHub with workflow templates --fetch.

Never forget maintenance again

Add overdue: 7 to any task. When you launch the TUI, overdue tasks pop up immediately:

┌──────────── ⚠ Overdue Tasks ──────────────────┐
│  ! backup/db-full           3 day(s) overdue   │
│  ! monitoring/disk-check    7 day(s) overdue   │
│                                                 │
│  Enter: jump to task  Esc: dismiss              │
└─────────────────────────────────────────────────┘

Multi-step workflows with real dependency management

YAML workflows support DAG execution with topological ordering. If step B depends on step A, it waits. If step C is independent, it doesn't:

name: MySQL Daily Backup
overdue: 1
steps:
  - id: dump
    cmd: mysqldump --all-databases > /tmp/db.sql
    timeout: 300
  - id: compress
    cmd: gzip /tmp/db.sql
    needs: [dump]
  - id: upload
    cmd: aws s3 cp /tmp/db.sql.gz s3://backup/
    needs: [compress]
    retry: 3
    retry_delay: 5
    run_if: "test -f /tmp/db.sql.gz"
cleanup:
  - id: remove-tmpfiles
    cmd: rm -f /tmp/db.sql /tmp/db.sql.gz
env:
  AWS_PROFILE: prod

If a step fails, its dependents are skipped — but independent branches keep running. Steps can capture output via regex and pass values downstream with {{step_id.var}}. Cleanup steps run regardless of success or failure, like a finally block. Interactive commands (REPLs, journalctl -f, TUI tools) are auto-detected and run with the terminal restored — or mark steps interactive: true explicitly.

Sub-workflows and `call` steps

Compose complex automation by calling workflows from other workflows. Use the call: field instead of cmd: to invoke any task by reference:

name: Full Deploy Pipeline
steps:
  - id: pre-checks
    call: monitoring/health-check
  - id: backup
    call: backup/db-full
    needs: [pre-checks]
  - id: deploy
    call: deploy/rolling-update
    needs: [backup]
  - id: smoke
    call: monitoring/smoke-test
    needs: [deploy]
  - id: rollback
    call: deploy/rollback
    run_if: "test '{{smoke.status}}' = 'failed'"

Sub-workflows execute recursively with a depth limit (max 10) to prevent cycles. Each inherits the parent's environment and template variables. This is how you build runbooks that orchestrate other runbooks — the n8n equivalent of sub-workflow nodes.

Loops with `for_each`

Iterate over static lists, template variable references, or dynamic command output. Each iteration gets {{item}} as a template variable:

steps:
  - id: backup-all
    cmd: pg_dump {{item}} > /tmp/{{item}}_backup.sql
    for_each:
      source: list
      items: [users_db, orders_db, analytics_db]
    for_each_parallel: true         # run iterations concurrently
    for_each_continue_on_error: true # keep going if one fails

Dynamic lists from command output:

steps:
  - id: restart-unhealthy
    cmd: docker restart {{item}}
    for_each:
      source: command
      command: "docker ps --filter health=unhealthy --format '{{.Names}}'"

Expression language with pipe filters

Template variables support pipe filters for in-line transformation — no shell gymnastics needed:

cmd: echo "Host: {{hostname | upper}}, DB: {{db_name | default 'mydb'}}"

Available filters: upper, lower, trim, default, replace, truncate, split, first, last, nth, count. Ternary expressions work too: {{var | eq "prod" ? "production" : "staging"}}. Date offsets: {{date_offset +7d}}, {{date_offset -1w}}. Docker and Go template syntax (e.g. {{.Names}}) is passed through untouched.

Webhook server — trigger workflows via HTTP

Run workflow serve to expose a REST API for triggering workflows from CI pipelines, monitoring alerts, or chatbots:

workflow serve --port 8080

Endpoints:

Method	Path	Description
`GET`	`/health`	Health check
`GET`	`/tasks`	List all available tasks
`POST`	`/run/<category>/<task>`	Trigger workflow (returns 202 + run_id)
`GET`	`/status/<run_id>`	Poll run status

Authenticated via auto-generated Bearer token (printed at startup). Supports JSON body for environment variable injection, concurrent run limits (default 4), CSRF protection, and 1MB max body size.

curl -X POST http://localhost:8080/run/backup/db-full \
  -H "Authorization: Bearer <token>" \
  -H "X-Workflow-Client: curl" \
  -d '{"env": {"TARGET": "production"}}'

Step-level branching with `run_if` / `skip_if`

After each step completes, {{step_id.status}} is automatically set to success, failed, skipped, or timedout. Use this in run_if or skip_if to branch on outcomes:

steps:
  - id: deploy
    cmd: ./deploy.sh
  - id: rollback
    run_if: "test '{{deploy.status}}' = 'failed'"
    cmd: ./rollback.sh
  - id: smoke-test
    skip_if: "test '{{deploy.status}}' = 'failed'"
    cmd: ./smoke-test.sh

run_if runs the step only when the condition succeeds (exit 0). skip_if is the inverse — it skips when the condition succeeds. Both support full template expansion, so {{var}} references work in conditions.

Native notifications — 9 services, zero external dependencies

Send notifications to Slack, Discord, Mattermost, Telegram, Microsoft Teams, ntfy, Gotify, generic webhooks, and email — all via native HTTP (no curl or mail required). Each backend is gated behind a cargo feature flag so you only pull the dependencies you need.

notify:
  on_failure:
    - "slack://https://hooks.slack.com/services/T00/B00/xxx"
    - "telegram://$TELEGRAM_BOT_TOKEN@$TELEGRAM_CHAT_ID"
    - "ntfy://ntfy.sh/ops-alerts"
  on_success:
    - "webhook://https://status.example.com/api/deploy"
  env:
    environment: production
    team: platform

Single-string config still works for backward compatibility. Or use severity-based routing for fine-grained control:

notify:
  channels:
    - target: "slack://https://hooks.slack.com/..."
      on: [failure, warning]
    - target: "ntfy://ntfy.sh/ops-info"
      on: [success, failure, warning]

Scheme	Service	Rich format
`slack://WEBHOOK_URL`	Slack	Block Kit with colored sidebar
`discord://WEBHOOK_URL`	Discord	Embeds with severity colors and fields
`telegram://BOT_TOKEN@CHAT_ID`	Telegram	MarkdownV2 with severity icons
`teams://WEBHOOK_URL`	Microsoft Teams	Adaptive Cards
`ntfy://SERVER/TOPIC`	ntfy	Priority-mapped push notifications
`gotify://SERVER?token=TOKEN`	Gotify	Priority-mapped push notifications
`webhook://URL`	Generic webhook	JSON body with all fields
`mattermost://SERVER/hooks/ID`	Mattermost	Slack-compatible attachments with fields
`email://USER@HOST?smtp=...&port=...`	Email (SMTP)	Formatted email via `lettre`

Environment variables ($VAR) are expanded in URLs. Notifications include retry with exponential backoff and per-service rate limiting. Failures are logged but never block workflow execution. Per-workflow notify: merges with global config.toml defaults (set notify_override: true to replace instead).

Notification commands have access to rich template variables: {{task_ref}}, {{exit_code}}, {{workflow_name}}, {{hostname}}, {{failed_steps}}, {{duration_ms}}, {{timestamp}}, {{status}}, plus any keys from notify.env.

Cargo feature flags (default: slack, discord, webhook, ntfy, telegram, email, mattermost):

# Build with all defaults
cargo build --release

# Minimal build without any notification backends
cargo build --release --no-default-features

# Pick specific backends
cargo build --release --no-default-features --features "slack,ntfy"

Runtime variable prompting

Workflows can declare variables with descriptions, defaults, and dynamic choices. When you run the task from the TUI, it prompts for values before execution:

name: Database Restore
variables:
  - name: db_name
    description: "Target database"
    default: "mydb"
  - name: backup_file
    description: "Backup to restore"
    choices_cmd: "ls /backups/*.sql.gz"
steps:
  - id: restore
    cmd: zcat {{backup_file}} | psql {{db_name}}

Soft delete and trash recovery

Press D in the TUI or use the CLI to safely remove tasks. Nothing is permanently deleted — files move to a timestamped .trash/ directory:

workflow trash list                  # see trashed files with timestamps
workflow trash restore db-full.yaml  # put it back
workflow trash empty                 # permanently delete when you're sure

Built-in safety nets

Accidentally pasting rm -rf / into a workflow won't ruin your day. workflow blocks known destructive patterns — fork bombs, dd to block devices, chmod -R 777 / — before execution. Override with --force when you actually mean it.

Environment variable values from env: blocks are automatically redacted in live output and logs. sudo steps get a pre-flight check before prompting. Failed steps produce actionable hints: "permission denied → check sudo", "command not found → check PATH".

Track everything

Every run is recorded in SQLite with who ran it, from which machine, via which interface (TUI or CLI), and how long it took. JSON logs capture full step output. Compare consecutive runs to spot regressions:

workflow compare backup/db-full        # side-by-side diff
workflow compare backup/db-full --ai   # AI-powered analysis

Tasks show heat indicators based on 30-day run frequency: ▲ (hot, ≥5 runs), · (warm), ▽ (cold). Press f to sort hot tasks to the top. Press F to filter by status: All → Failed → Overdue → Never-run.

File structure

~/.config/workflow/
├── backup/                  # Category (folder name)
│   ├── db-full.sh           # Bash script — runs directly
│   └── mysql-daily.yaml     # Multi-step YAML workflow
├── deploy/
│   └── staging.yaml
├── docker/
│   └── cleanup.yaml
├── logs/                    # Auto-generated (JSON per run)
├── history.db               # Auto-generated (SQLite)
└── config.toml              # Optional

Folders are categories. .sh files are bash tasks. .yaml files are multi-step workflows. That's the entire data model.

CLI reference

# Run tasks
workflow run backup/db-full
workflow run deploy/staging --dry-run
workflow run deploy/staging --env ENV=production --timeout 60
workflow run risky-task --force          # bypass dangerous command check

# List and inspect
workflow list                            # all tasks
workflow list --json                     # machine-readable
workflow status backup/db-full           # run history
workflow validate                        # check all YAML syntax

# AI-powered updates
workflow ai-update backup/db-full --prompt "add error handling"
workflow ai-update backup/db-full --prompt "parallelize steps" --dry-run
workflow ai-update backup/db-full --prompt "add cleanup" --save-as db-full-v2

# Scheduling
workflow schedule backup/db-full --cron "0 2 * * *"
workflow schedule backup/db-full --systemd
workflow schedule backup/db-full --remove

# Compare runs
workflow compare backup/db-full
workflow compare backup/db-full --ai

# Templates
workflow templates
workflow templates --fetch

# Export / import
workflow export -o my-workflows.tar.gz --include-history
workflow import my-workflows.tar.gz --overwrite

# Secrets
workflow secrets init                    # setup encrypted store
workflow secrets set DB_PASSWORD         # prompt for value
workflow secrets set API_KEY --value x   # set directly
workflow secrets list                    # names only
workflow secrets get DB_PASSWORD         # decrypt and print
workflow secrets rm DB_PASSWORD          # remove

# Trash
workflow trash list                  # timestamped soft-deleted files
workflow trash restore db-full.yaml  # restore from trash
workflow trash empty                 # permanently delete

# Webhook server
workflow serve                       # start on default port 8080
workflow serve --port 9090           # custom port

# Logs
workflow logs backup/db-full
workflow logs --limit 20 --json

# MCP tools (requires --features mcp)
workflow mcp list-tools github              # list available tools
workflow mcp list-tools github --json       # full schemas as JSON
workflow mcp call github create_issue --arg repo=myorg/app --arg title="Bug"
workflow mcp check github                   # verify server connectivity

# Memory (anomaly detection & trends)
workflow memory health                          # health scores for all tasks
workflow memory anomalies                       # recent anomalies
workflow memory baseline backup/db-full         # statistical baselines
workflow memory trends backup/db-full           # duration trend (30d)
workflow memory ack all --task backup/db-full   # acknowledge anomalies
workflow memory recompute                       # recompute all baselines

# Snapshots (key-value baselines)
workflow snapshot set backup/db-full baseline '{"hash":"abc123"}'
workflow snapshot get backup/db-full baseline        # prints value (for shell capture)
workflow snapshot delete backup/db-full baseline     # reset baseline
workflow snapshot list                               # all snapshots
workflow snapshot list backup/db-full                # filter by task
workflow snapshot list --json                        # machine-readable

# Sync across machines
workflow sync setup                      # one-time: init + private GitHub repo
workflow sync push                       # auto-commit and push
workflow sync pull                       # pull latest
workflow sync status
workflow sync branch                     # list all branches
workflow sync branch customer-acme       # switch branch (auto-commits first)

Exit code is 0 on success, non-zero on failure — works directly in cron jobs and CI pipelines.

TUI keybindings

Key	Action
`j`/`k` or arrows	Navigate
`Tab` / `h`/`l`	Switch panes
`r`	Run selected task
`d`	Dry-run (preview without executing)
`e`	Open in `$EDITOR`
`/`	Search tasks and step commands
`f`	Toggle heat sort (hot tasks first)
`F`	Cycle status filter (All/Failed/Overdue/Never-run)
`w`	New task from shell history
`a`	New task via AI (or AI fix when error visible)
`A`	AI-update selected task
`t`	New task from template catalog
`W`	Clone and optimize selected task
`n`	Rename task or category
`D`	Delete (soft — moves to `.trash/`)
`R`	Recent runs (last 10 across all tasks)
`S`	Toggle bookmark
`s`	View bookmarked tasks
`L`	View run logs
`K`	Secrets manager (add/view/edit/delete)
`G`	Git sync controls
`c`	Compare last two runs
`?`	Help (context-sensitive)
`q`	Quit

YAML workflow format

name: Deploy with Rollback
overdue: 1                          # remind if not run within N days
steps:
  - id: check-health
    cmd: curl -sf http://localhost/health
    timeout: 10                     # seconds
  - id: deploy
    cmd: ./deploy.sh {{version}}
    needs: [check-health]           # dependency
    retry: 2                        # retry on failure
    retry_delay: 5                  # seconds between retries
    run_if: "test -f deploy.sh"     # conditional execution
  - id: rollback
    cmd: ./rollback.sh
    run_if: "test '{{deploy.status}}' = 'failed'"   # branch on step outcome
  - id: smoke-test
    cmd: ./smoke-test.sh
    skip_if: "test '{{deploy.status}}' = 'failed'"  # skip when condition is true
  - id: get-version
    cmd: cat VERSION
    outputs:                        # capture output as variable
      - name: ver
        pattern: "^(\\S+)"
  - id: tag
    cmd: git tag v{{get-version.ver}}
    needs: [get-version]
cleanup:                            # runs regardless of success/failure
  - id: unlock
    cmd: rm -f /tmp/deploy.lock
env:
  DEPLOY_ENV: production            # values auto-redacted in logs
notify:
  on_failure:                         # single string or array of targets
    - "slack://https://hooks.slack.com/services/T00/B00/xxx"
    - "ntfy://ntfy.sh/ops-alerts"
  on_success: "webhook://https://status.example.com/api/deploy"
  env:                              # extra vars available in notify commands
    environment: production
    team: platform

Template variables available in all commands: {{date}}, {{datetime}}, {{hostname}}, {{task_ref}} (current task identity), {{step_id.status}} (after each step: success/failed/skipped/timedout), plus any captured step outputs.

Snapshot baselines (push/pop content checks)

Workflows often need to verify that something hasn't changed — a web page still has the expected content, a config file hasn't drifted, an API response matches a known shape. The snapshot subcommand provides a generic key-value store in SQLite for this pattern.

The idea: first run auto-learns a baseline, subsequent runs compare against it. No hardcoded expected values to maintain.

name: Page Drift Check
steps:
  - id: fingerprint
    cmd: curl -s https://example.com | sha256sum | cut -d' ' -f1
    outputs:
      - name: hash
        pattern: '^(\S+)'

  - id: baseline-check
    needs: [fingerprint]
    cmd: |
      EXISTING=$(workflow snapshot get "{{task_ref}}" content-hash 2>/dev/null || true)
      if [ -z "$EXISTING" ]; then
        echo "First run — storing baseline"
        workflow snapshot set "{{task_ref}}" content-hash "{{fingerprint.hash}}"
      elif [ "$EXISTING" != "{{fingerprint.hash}}" ]; then
        echo "DRIFT: $EXISTING -> {{fingerprint.hash}}"
        exit 1
      else
        echo "OK: matches baseline"
      fi

Snapshots are stored in the same history.db that tracks run history — no extra files, no git noise. Reset a baseline anytime with workflow snapshot delete.

workflow snapshot get mycat/mytask baseline       # inspect stored value
workflow snapshot delete mycat/mytask baseline     # force re-learn on next run
workflow snapshot list --json                      # all snapshots as JSON

Shell steps can capture workflow snapshot get output via $(...) since get prints the raw value to stdout (exits 1 if not found). The set subcommand reads from stdin when --value is omitted, so you can pipe content directly: echo '{"k":"v"}' | workflow snapshot set task key.

Workflow memory (anomaly detection & trends)

Every run is automatically profiled. After 5+ executions, workflow builds statistical baselines per task and flags anomalies — no configuration needed.

What it detects:

Duration spikes — a step or workflow takes significantly longer than usual (Modified Z-score via MAD)
New failures — a normally-stable task suddenly fails (success rate monitoring)
Flapping — alternating pass/fail pattern (≥3 transitions in 6 runs)
Output drift — step output changed when it was previously stable (FNV-1a fingerprinting)
Metric shifts — extracted values (MB, %, counts) deviate from baseline

Anomalies appear automatically after workflow run:

success: run logged to database
  ⚠ 1 anomalies detected: 1 warning
    [warning] step 'backup' 892ms (baseline 145ms ±23ms, z=3.2)

In the TUI, press M on any task to see health scores, baselines, trends, and recent anomalies.

CLI commands

workflow memory health                          # health scores for all tasks
workflow memory anomalies                       # recent anomalies (all tasks)
workflow memory anomalies backup/db-full        # anomalies for one task
workflow memory baseline backup/db-full         # statistical baselines
workflow memory trends backup/db-full           # duration trend (30 days)
workflow memory trends backup/db-full --metric "Disk Used:%"  # custom metric
workflow memory ack all --task backup/db-full   # acknowledge anomalies
workflow memory recompute                       # recompute all baselines

All commands support --json for machine-readable output.

How it works

Short-term memory: in-process cache in the TUI for instant display
Long-term memory: four SQLite tables (memory_baselines, memory_metrics, memory_anomalies, memory_trends) in the same history.db
Baselines are recomputed from the last 50 runs after every execution using statrs for percentiles and standard deviation
Anomaly detection uses Modified Z-score (MAD-based, robust to outliers) with thresholds: >1.5σ info, >2.0σ warning, >3.0σ critical
Memory tables are automatically rotated alongside run history (respects log_retention_days)

Sync across machines

Sync workflow definitions via a private GitHub repo:

workflow sync setup    # creates private repo, enables auto-sync

After setup, changes auto-commit and push. The TUI pulls on startup. Press G in the TUI for manual sync controls. Logs, history, and local config stay local.

Branch switching (workflow libraries)

Each git branch holds a complete workflow library — one per customer, environment, or site. Switching branches swaps your entire set of workflows in one command:

workflow sync branch                 # list branches (* marks current)
workflow sync branch customer-acme   # switch to branch (creates if needed)

In the TUI, press G → "Switch branch" to browse and switch interactively. Dirty changes are auto-committed before switching, and workflows are rescanned automatically for the new branch content. This is how MSPs manage per-client runbooks, or how teams keep dev/staging/prod workflow sets separated — all version-controlled in one repo.

# ~/.config/workflow/config.toml
[sync]
enabled = true
auto_commit = true
auto_push = true
auto_pull_on_start = true

Configuration

Optional ~/.config/workflow/config.toml — everything has sensible defaults:

workflows_dir = "/home/user/.config/workflow"
log_retention_days = 30
editor = "vim"
default_timeout = 600

[hooks]
pre_run = "echo 'starting'"
post_run = "echo 'done'"

[notify]
on_failure = "slack://https://hooks.slack.com/services/..."

[server]
port = 8080
max_concurrent_runs = 4

bookmarks = ["backup/db-full", "deploy/staging"]

For machine-specific overrides (different editor, custom paths), create config.local.toml alongside config.toml. It merges on top without affecting the shared configuration — useful when syncing config across machines via Git.

AI tool integration

Supported AI CLIs

workflow auto-detects these tools at startup and shows which is available in the TUI header:

Tool	Detection	Used for
Claude Code (`claude`)	`claude -p`	Generate, update, fix, and refine workflows
Codex CLI (`codex`)	`codex exec`	Generate, update, fix, and refine workflows
Gemini CLI (`gemini`)	`gemini -p`	Generate, update, fix, and refine workflows

Install any one of these and authenticate it — workflow handles the rest. No API keys to configure inside workflow itself.

Claude Code skill

A bundled Claude Code skill lets you manage workflows entirely from within Claude Code or Claude Code-powered agents. Install it:

mkdir -p ~/.claude/skills
ln -s "$(pwd)/skills/workflow-manager" ~/.claude/skills/workflow-manager

Then ask Claude naturally — "create a workflow for daily database backups", "list my overdue tasks", "dry-run the staging deploy" — or use /workflow-manager run backup/db-full --dry-run.

This makes workflow a natural building block for agentic automation: AI agents can create, validate, and execute operational tasks through a well-defined file-based interface without any special APIs.

Encrypted secrets store

Workflows can reference secrets by name in secrets: — but where do the values come from? Instead of leaving passwords in .bashrc or .env files, workflow ships an encrypted secrets store backed by age and your SSH key.

# One-time setup (auto-detects ~/.ssh/id_ed25519)
workflow secrets init

# Store secrets (prompts for value securely)
workflow secrets set DB_PASSWORD
workflow secrets set API_TOKEN --value sk-live-abc123

# List and retrieve
workflow secrets list
workflow secrets get DB_PASSWORD

# Remove
workflow secrets rm DB_PASSWORD

Secrets are encrypted at rest in ~/.config/workflow/secrets.age using your SSH public key and decrypted to memory only at runtime. Values are zeroized after use.

TUI secrets manager

Press K in the TUI to manage secrets without leaving the interface:

Browse — see all stored secret names at a glance
Add (a) — enter a new secret name and value (value input is masked)
View (v/Enter) — decrypt and reveal a secret's value (any key dismisses)
Edit (e) — update an existing secret's value
Delete (d) — remove a secret with confirmation

If the secrets store hasn't been initialized yet, the modal offers to set it up automatically using your SSH key.

Auto-injection into workflows

When a workflow declares secrets:, values are automatically injected from the store at execution time:

name: Deploy
secrets:
  - DB_PASSWORD
  - API_TOKEN
steps:
  - id: migrate
    cmd: DATABASE_URL="postgres://app:$DB_PASSWORD@db/prod" ./migrate.sh

Precedence: explicit env: in YAML > --env CLI flag > secrets store > environment variables. Secrets never override values you set explicitly. If the store doesn't exist or a secret isn't found, the workflow falls back to environment variables (existing behavior preserved).

MCP Integration (Model Context Protocol)

Call any of 16,000+ MCP-compatible tools — GitHub, Slack, databases, cloud providers — directly from workflow steps. No shell glue code, no curl pipelines, no API client scripting. MCP steps are a first-class step type alongside cmd: and call:.

MCP support is opt-in behind a feature flag to keep the base binary small:

cargo build --release --features mcp
cargo install --path . --features mcp

Configuring MCP servers

Define server aliases in config.toml so workflows can reference them by short name:

# Stdio transport — spawns a child process
[mcp.servers.github]
command = "npx -y @modelcontextprotocol/server-github"
secrets = ["GITHUB_TOKEN"]

[mcp.servers.slack]
command = "npx -y @modelcontextprotocol/server-slack"
secrets = ["SLACK_BOT_TOKEN"]
env = { SLACK_TEAM_ID = "T0123456" }

# HTTP transport — connects directly to a remote MCP endpoint
[mcp.servers.cpanel-whm]
url = "https://myserver.example.com:2087/mcp"
auth_header = "whm root:APITOKEN"
timeout = 60

Server fields (stdio transport):

command — the shell command to spawn the MCP server process
secrets — list of secret names resolved from the encrypted secrets store and injected as environment variables
env — additional environment variables for the server process
timeout — optional timeout in seconds for tool calls

Server fields (HTTP transport):

url — the HTTP/HTTPS endpoint URL for the MCP server
auth_header — the raw Authorization header value (supports any scheme: Bearer, Basic, WHM, etc.)
headers — optional table of custom HTTP headers
timeout — optional timeout in seconds for tool calls

Credentials are stored in the encrypted secrets store (see above) and injected automatically — no plaintext tokens in config files.

Writing MCP steps in YAML

Use the mcp: field instead of cmd: to call an MCP tool:

name: GitHub Release Workflow
steps:
  - id: create-release
    mcp:
      server: github
      tool: create_release
      args:
        owner: myorg
        repo: myapp
        tag: "v{{version}}"
        body: "Release {{version}} — {{date}}"
    outputs:
      - name: url
        pattern: "(https://github.com/.*releases/.*)"

  - id: notify-slack
    mcp:
      server: slack
      tool: send_message
      args:
        channel: "#releases"
        text: "Released {{version}}: {{create-release.url}}"
    needs: [create-release]

MCP steps support all the same DAG features as cmd: steps: needs: dependencies, run_if/skip_if conditions, retry/retry_delay, timeout, for_each loops, output capture via outputs:, and template variable expansion ({{var}}, {{date}}, {{step_id.output_name}}).

Inline server definitions

For one-off use or workflows shared across machines, define the server inline instead of referencing a config alias:

steps:
  - id: query
    mcp:
      server:
        command: "npx -y @modelcontextprotocol/server-postgres"
        env:
          DATABASE_URL: "postgres://localhost/mydb"
        secrets: ["DB_PASSWORD"]
      tool: query
      args:
        sql: "SELECT count(*) FROM users WHERE created_at > '{{date_offset -1d}}'"

Practical example: database backup with notification

name: DB Backup with MCP
steps:
  - id: dump
    cmd: pg_dump mydb > /tmp/mydb_{{date}}.sql
    timeout: 300

  - id: record-size
    cmd: stat --format='%s' /tmp/mydb_{{date}}.sql
    needs: [dump]
    outputs:
      - name: bytes
        pattern: "^(\\d+)"

  - id: notify
    mcp:
      server: slack
      tool: send_message
      args:
        channel: "#ops"
        text: "Backup complete: {{record-size.bytes}} bytes"
    needs: [record-size]

cleanup:
  - id: clean
    cmd: rm -f /tmp/mydb_{{date}}.sql

CLI commands

Discover and test MCP servers from the command line:

# List all tools available on a server
workflow mcp list-tools github
workflow mcp list-tools github --json    # full schemas

# Call a tool directly (ad-hoc testing)
workflow mcp call github create_issue \
  --arg repo=myorg/myapp \
  --arg title="Bug report" \
  --arg body="Found an issue with..."

# Health check a server (verify connectivity and credentials)
workflow mcp check github

list-tools shows tool names, parameter counts, and descriptions in a formatted table. With --json, it outputs full tool schemas including input parameters — useful for scripting or discovering API shapes.

call parses --arg key=value pairs into a JSON object. Values are auto-typed: true/false become booleans, numeric strings become numbers, everything else stays a string. Server credentials are injected from the secrets store automatically.

check spawns the server, initializes the MCP connection, and lists tools — verifying that the command works, credentials are valid, and the server responds. Useful for debugging setup issues.

How it works

MCP steps support two transports:

Stdio — spawns the server as a child process, communicates via JSON-RPC over stdin/stdout. The same protocol used by Claude Code, VS Code, and other MCP hosts.
HTTP — connects directly to a remote MCP endpoint via Streamable HTTP transport. No proxy needed — talk to cPanel/WHM, remote APIs, or any HTTP-based MCP server natively.

At execution time:

Server config is resolved (alias lookup in config.toml or inline definition)
For stdio: secrets are loaded from the encrypted store and injected as environment variables. For HTTP: auth header is attached to requests.
Template variables ({{var}}) are expanded in all args string values (recursively through nested objects/arrays)
The MCP connection is established (child process spawn or HTTP handshake)
The tool is called with the expanded args
The result text is captured as stdout (available for outputs: regex patterns and downstream {{step_id.var}} references)
The connection is shut down

JSON output in the TUI

MCP tools typically return JSON data. The detail pane automatically detects JSON output and enhances the display:

Pretty-printing — compact JSON is reformatted with indentation
Syntax highlighting — keys (cyan), strings (green), numbers (yellow), booleans (magenta), braces (white bold)
Collapsible sections — navigate and fold JSON blocks directly in the TUI

Detail pane keybindings (when focused):

Key	Action
`-`	Collapse JSON block at current line
`+`	Expand collapsed JSON block
`Z`	Fold all / unfold all
`{` / `}`	Jump to previous / next JSON block
`PgUp` / `PgDn`	Scroll by 20 lines

The AI wizard (a key in TUI) is MCP-aware: when MCP servers are configured, it prefers generating mcp: steps over shell commands for matching services. For example, if you have a github server configured and ask "create a release workflow", the AI will use mcp: { server: github, tool: create_release } instead of curl calls to the GitHub API.

Security

Multiple layers of protection are built in:

Dangerous command blocking — rm -rf /, fork bombs, dd to devices, mkfs on real devices, and similar destructive patterns are caught before execution. Override with --force.
Encrypted secrets store — secrets encrypted at rest with age + SSH key, decrypted to memory only, zeroized after use. File written as 0600.
Secret masking — env: values and injected secrets are redacted in live output and log files.
Path traversal protection — task references can't escape the workflows directory.
Command injection prevention — template variables and task names are sanitized.
Import validation — archive imports reject paths that would write outside the target directory.

Install

Pre-built binary — download from GitHub Releases.

From source:

git clone https://github.com/vchaindz/workflow.git
cd workflow
cargo build --release
# Binary: target/release/workflow

Requires Rust 1.56+ (2021 edition). Single binary. Notification backends use native HTTP (ureq) and SMTP (lettre) — no curl or mail needed at runtime. For MCP support, add --features mcp (pulls in rmcp v1.2, tokio, and reqwest for HTTP transport).

Name		Name	Last commit message	Last commit date
Latest commit History 98 Commits
.claude/commands		.claude/commands
.github/workflows		.github/workflows
assets		assets
docs		docs
scripts/ralph		scripts/ralph
skills/workflow-manager		skills/workflow-manager
src		src
templates		templates
tests		tests
tmp		tmp
.gitignore		.gitignore
CHANGELOG.md		CHANGELOG.md
CLAUDE.md		CLAUDE.md
CONTRIBUTING.md		CONTRIBUTING.md
Cargo.lock		Cargo.lock
Cargo.toml		Cargo.toml
LICENSE		LICENSE
README.md		README.md

Folders and files

Latest commit

History

Repository files navigation

workflow

Why workflow?

Quick start

What makes it useful

Turn shell history into reusable tasks

AI-native workflow management

52 bundled templates ready to go

Never forget maintenance again

Multi-step workflows with real dependency management

Sub-workflows and call steps

Loops with for_each

Expression language with pipe filters

Webhook server — trigger workflows via HTTP

Step-level branching with run_if / skip_if

Native notifications — 9 services, zero external dependencies

Runtime variable prompting

Soft delete and trash recovery

Built-in safety nets

Track everything

File structure

CLI reference

TUI keybindings

YAML workflow format

Snapshot baselines (push/pop content checks)

Workflow memory (anomaly detection & trends)

CLI commands

How it works

Sync across machines

Branch switching (workflow libraries)

Configuration

AI tool integration

Supported AI CLIs

Claude Code skill

Encrypted secrets store

TUI secrets manager

Auto-injection into workflows

MCP Integration (Model Context Protocol)

Configuring MCP servers

Writing MCP steps in YAML

Inline server definitions

Practical example: database backup with notification

CLI commands

How it works

JSON output in the TUI

Security

Install

License

About

Topics

Resources

License

Contributing

Uh oh!

Stars

Watchers

Forks

Releases 9

Packages 0

Uh oh!

Contributors

Uh oh!

Languages

Sub-workflows and `call` steps

Loops with `for_each`

Step-level branching with `run_if` / `skip_if`

Packages