@rubenf I'm trying to discard a draft

**🚀 AI agents are now a standalone kind** They sit next to your scripts, flows and apps, so you build, run and share one without wrapping it in a flow first. ➡️ Run one straight away as a chat or a form, with no flow around it. ➡️ It runs with the caller's permissions, operators included, so you can hand an agent to someone who can only run things. ➡️ Its editor keeps version history and evals, so you can diff a prompt change and score it against a dataset before shipping. 📖 https://www.windmill.dev/docs/core_concepts/ai_agents

Fratera · 4d ago

**Git sync auto-pull, promotion and PRs now on Pro licenses** The git-native deploy features that used to need Enterprise now work on a Pro license too: automatic pull from Git, promotion between workspaces, and a pull request opened on each deploy. ➡️ Auto-pull keeps a workspace in step with its tracked branch, over webhooks or polling. ➡️ Promotion mode moves changes from a dev workspace up to prod through Git. ➡️ A deploy can open a pull request instead of writing to the branch directly. Community (non-Enterprise) builds are unchanged and still don't run auto-pull or promotion. v1.814.0. 📖 https://www.windmill.dev/docs/advanced/git_sync

Fratera · 7d ago

**Allowed origins for HTTP routes** Restrict which browser origins can call an HTTP route, rather than answering every page with Access-Control-Allow-Origin: . Set the list under Advanced > Request Options. ➡️ Enforced on the preflight, so a disallowed origin never reaches the runnable. ➡️ On Enterprise, superadmins set an instance-wide default; a route opts out with *. The list overrides Access-Control-Allow-Origin from wm_headers, and static websites are exempt. v1.812.0. 📖 https://www.windmill.dev/changelog/http-route-allowed-origins

Fratera · 3w ago