-
Notifications
You must be signed in to change notification settings - Fork 885
Description
Description
When using Windmill AI (with Claude Opus 4.5) to configure AI Agent nodes, I've encountered several issues that can leave the UI in an unrecoverable state.
Issues Encountered
-
Output type incorrectly set to
json
When providing an output JSON schema, the AI often sets the output type tojson, which doesn't appear to be supported by Windmill. This causes errors. -
Memory block configuration breaks the UI
Memory-related settings frequently cause issues. The memory section of the AI Agent step settings sometimes disappears entirely, and the UI becomes unresponsive/stuck. -
AI provider settings configured incorrectly
The AI provider field is often set to invalid values, and I'm unable to correct it from the UI once it's broken. -
UI becomes stuck with no way to recover
When the AI misconfigures the node, the UI gets stuck and I can't interact with it to manually fix the issue. I end up blocked with no clear path forward.
Current Workaround
I've found that in the local development environment, the AI tends to get the configuration right more often. When the cloud UI gets stuck, my only option is to pull the Flow locally, fix it there, and push it back.
Suggestions
- Improve AI instructions — Provide clearer guidance to the AI about valid configurations for AI Agent nodes (valid output types, memory settings, provider options, etc.)
- Graceful error handling in UI — Even when configuration is invalid, allow users to access and edit the raw settings so we can manually fix issues instead of getting completely blocked
Environment
- Model: Claude Opus 4.5
- windmill version: CE v1.599.3