Windmill v1.660.0: Local Script Testing in Flow Preview

Here at Lead AI Dot Dev, we tracked Windmill's v1.660.0 release, which addresses a friction point in local development cycles. The update (#8365) enables the CLI to reference and execute local scripts when previewing flows - meaning you can test automation logic against actual code running on your machine before deploying.

Previously, flow preview required either deployed scripts or workarounds to test with local code. Now the CLI bridges that gap. This is a direct response to how builders actually work: iterating rapidly on local machines, then promoting to production environments.

• CLI can now reference local scripts during flow preview mode
• Eliminates the deploy-to-test cycle for simple iterations
• Maintains security by keeping preview local to your environment

The friction point being solved is real: testing flow logic in Windmill previously required either committing changes or deploying preview versions. For builders running tight iteration loops, this adds latency to feedback cycles.

With local script execution in preview, your workflow becomes: write code locally - test it in flow context immediately - refine - commit when confident. This reduces cycle time significantly for debugging complex automation logic where the flow orchestration matters as much as individual script logic.

The scope is intentionally narrow. This isn't a full local runtime environment - it's specifically about using local scripts when previewing flows. That's actually the right design decision. It solves the immediate problem without building unnecessary infrastructure.

• Test flow logic locally without pushing to staging or production
• Iterate on script execution patterns within the flow context
• Catch orchestration issues before deployment
• Useful for debugging multi-step flows where order and data flow matter

This feature benefits specific workflows. If you're building flows with multiple custom scripts that need orchestration testing, local preview becomes essential. It's particularly valuable when scripts interact with each other or when the flow's conditional logic depends on script outputs.

Consider using local script preview when: you're in active development of a new flow, you're debugging why a flow behaves differently than expected scripts run in a certain order, or you need to test error handling in orchestration logic. It's less critical for simple single-script flows or when you have a robust staging environment.

One caveat: local preview still has limitations. External dependencies, data connections, and environment variables need to be handled carefully. This isn't a replacement for full integration testing - it's an acceleration tool for the most common iteration pattern.

• Use for multi-script flows requiring orchestration testing
• Essential when debugging conditional logic between scripts
• Accelerates iteration during active development phases
• Skip it if your flows are simple or you have reliable staging

Windmill continues positioning itself in the workflow automation space with pragmatic developer-first improvements. This release shows they're listening to actual usage patterns - not building feature theater, but solving real iteration friction.

The smaller scope of this update (focused CLI improvement vs. major new feature) suggests Windmill is in stabilization mode. They're addressing the gaps between 'works in isolation' and 'works in production workflows.' That's healthy product maturity.

For builders evaluating workflow automation tools, this signals Windmill's commitment to the development experience, not just the final runtime. They understand that better local tooling reduces overall deployment friction. This compounds over time - small workflow improvements add up to significantly faster iteration.Thank you for listening, Lead AI Dot Dev

• Developer experience continues to be Windmill's differentiator
• Local-first testing patterns are becoming table stakes
• Watch for similar improvements in integration testing and debugging