Question 1

Do I need the CLI to develop locally?

Accepted Answer

The CLI is the primary tool for syncing a workspace to a local folder. Once synced, you can edit files in any editor. The VS Code extension adds previews and testing on top.

Question 2

Which editors are supported?

Accepted Answer

Any text editor works for editing scripts and flows as files. The VS Code extension provides the richest experience with live previews, YAML validation, and direct testing. Cursor is also supported.

Question 3

Can AI assistants create flows?

Accepted Answer

Yes. The wmill init command generates skill files that teach AI assistants how to write valid flow YAML. Combined with the VS Code YAML linter, AI tools can create and iterate on flows with real-time validation feedback.

Question 4

How does the MCP server differ from the CLI?

Accepted Answer

The CLI syncs files between your local directory and a workspace. The MCP server gives AI tools direct API access to a workspace: executing scripts, managing resources, and monitoring jobs. They complement each other.

Question 5

Can I run scripts locally without a Windmill instance?

Accepted Answer

You can run script code locally like any regular script. To access Windmill features like resources and state, you need a running instance or can use mocked API files to simulate the Windmill environment.

Question 6

How do I set up a local development workflow?

Accepted Answer

Install the CLI with npm install -g windmill-cli, run wmill workspace add to connect to your instance, then wmill sync pull to clone the workspace. Optionally run wmill init for AI context files and install the VS Code extension.

Develop locally, deploy to Windmill

Local development for Windmill

Sync your workspace to a local folder

VS Code extension

Built-in skills and AGENTS.md

Create scripts, flows, and apps from the CLI

Script

Flow

Full-code app

Run and debug locally

Deploy and sync to Git

Frequently asked questions

Build your internal platform on Windmill