cli-commands

Reference Windmill CLI commands for managing scripts, flows, apps, jobs, and workspace resources.

Updated May 28, 2026
One-click install
npx skills add https://github.com/kma-core/windmill --skill cli-commands-kma-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-commands
Source: https://github.com/kma-core/windmill/tree/main/system_prompts/auto-generated/skills/cli-commands
Command: npx skills add https://github.com/kma-core/windmill --skill cli-commands-kma-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working with the Windmill CLI requires knowing dozens of commands, subcommands, and flags across scripts, flows, apps, jobs, sync, and workspace administration. This Skill provides the complete command reference so you can correctly invoke wmill operations, debug job failures, and inspect run history without guessing syntax. ## Core Features & Use Cases - Full Command Reference: Covers every wmill command group including app, flow, script, job, sync, schedule, resource, folder, group, instance, datatable, and object-storage, with all flags and subcommands. - Job Debugging: Use wmill job list, job get, job logs, job result, job cancel, job rerun, and job restart to inspect run history and diagnose failures. - Local Development & Sync: Preview scripts and flows locally, run dev servers with live reload, and push or pull changes with wmill sync. - Use Case: A deployed flow fails in production. Use wmill job list to find the failed run, wmill job logs <id> to read aggregated step logs, then wmill job restart <id> --step <stepId> to resume from the failing step. ## Quick Start Use the cli-commands skill to show me how to list recent failed jobs and view their logs with the wmill CLI.

Frequently Asked Questions about cli-commands

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a failed Windmill job from the CLI?

Use `wmill job list` to find recent jobs, then `wmill job logs <id>` to view logs and `wmill job get <id>` for details. For flows, job get shows the step tree with sub-job IDs, and job logs aggregates all step logs.

How to run a Windmill script or flow from the command line?

Use `wmill script run <path>` or `wmill flow run <path>`, passing inputs with `-d` as a JSON string, a file via @filename, or stdin via @-. Add `-s` for silent mode that outputs only the final result.

Can I test a Windmill flow locally without deploying it?

Yes, `wmill flow preview <flow_path>` runs a local flow definition without deploying, using local PathScripts by default. Use `--step <id>` to run a single module in isolation or `--remote` to use deployed workspace scripts.

How do I sync local Windmill changes to a remote workspace?

Run `wmill sync push` to apply local changes remotely, or `wmill sync pull` for the reverse. Both support --dry-run to preview changes, plus flags to skip or include specific resource types like scripts, flows, secrets, and schedules.

How do I restart a failed Windmill flow at a specific step?

Use `wmill job restart <id> --step <stepId>` to restart a completed flow from a given top-level step. For branchall or for-loop steps, add `--iteration <n>` to restart at a specific iteration.

Does the wmill CLI support JSON output for scripting?

Yes, most list and get commands support a `--json` flag for piping to jq. Commands like `wmill job result` and silent mode (`-s`) on run commands also produce machine-friendly output suitable for automation.