* fix: refuse unknown roles and stale operator_settings in settings apply
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: keep omitted-key clears when a push only removes a workspace role
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: load instance roles on the held connection in the settings document
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix: resolve gitsync-settings wmill.yaml entry by workspace, not branch
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: write gitsync-settings pull overrides to the resolved workspace entry
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: refuse ambiguous gitsync-settings override target instead of guessing
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: never adopt a branch entry that names another workspace on override
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: refuse gitsync-settings override when the workspace resolves to no entry
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: keep the branch binding in the gitsync-settings override refusal hint
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: pin git-sync hub scripts to windmill-cli 1.862.1
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat: add max iterations and max duration bounds to while loops
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: fail exhausted while loops regardless of skip_failures and prior recovery
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: state that a while loop's duration limit can overrun by one iteration
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: let the while loop iterations field be cleared and retyped
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Ruben Fiszel <ruben@windmill.dev>
* feat: filter workspace webhook events by type
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: carry webhook_events through workspace rename and cli settings sync
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: update sqlx cache for workspace rename
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: add category presets to the webhook event filter
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: reject an empty webhook event list and document editWebhook's url field
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: hint when every webhook event is selected and check presets cover all types
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: make event categories the main webhook filter control
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(cli): suggest known instance URLs in workspace add
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* ci: retry bun setup in cli tests after a release download outage
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat: flow-level wall-clock timeout
* chore: regenerate flow schema prompts after rebase
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: claim timed-out flows before cancelling, scope the handler to the expired flow
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor: scope the flow timeout to root flows
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor: drop flownode from the flow timeout sweep
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: apply a flow's timeout when it runs as a subflow step
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: align subflow timeouts with script timeouts and let the ai chat set them
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: give a calling step the timeout error whether or not the subflow has a failure module
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* refactor: point the pipeline editor prompt at the shared pipeline guidance
* fix: keep a read-side annotation summary for sessions that cannot write drafts
* fix: count non-BMP characters once when naming a default table in the canvas and cli
* fix: teach pipeline nodes to attach the lake and read real columns
* test: run the data pipelines ai evals build against a real ducklake
* test: run only fed-by-nothing pipeline nodes and record run failures
* feat: name a materialized table after its script when the target names none
* fix: inspect pipeline columns read-only and cap the eval run's roots
* test: cap the roots of the tables-named-after-steps eval
* fix: keep flow steps and explicit targets out of the materialize default
* fix: name the table of a script run from a flow, recover bare materialize in the cli
* ci: point eval workers at the installed bun and serve native scripts
* fix: keep inline step tests out of the materialize default, recover bare scd2 in the cli
* chore: drop formatter-only changes from the materialize default diff
* fix: let a referenced-script step test name its table after the script
* fix: tell inline step tests apart by the missing script hash, not the path
* fix: teach pipeline nodes to attach the lake and read real columns
* test: run the data pipelines ai evals build against a real ducklake
* test: run only fed-by-nothing pipeline nodes and record run failures
* fix: inspect pipeline columns read-only and cap the eval run's roots
* ci: point eval workers at the installed bun and serve native scripts
- settings.yaml carries `role_overrides`, the workspace's per-role overrides and
workspace-only roles, applied as a whole after the legacy `operator_settings`.
- users/*.user.yaml carries the member's workspace role by name, so a custom role
survives `wmill sync pull` and `wmill sync push`; `admin` is still the admin flag.
- The User API schema documents the `role` field the endpoints already return.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat: reference existing HashiCorp Vault secrets from secret variables
A secret variable can hold `$external:vault://<path>#<key>` instead of a
value. The reference is resolved from Vault each time the variable is
read, so the value is never stored in Windmill. An instance-level
allow-list of path prefixes, optionally per workspace, is checked when a
reference is saved and again when it is resolved. Other schemes are
parsed and refused as unsupported backends.
Adds AppRole as a Vault auth method, an "External reference" toggle in
the variable editor and an instance settings section for the connection
and the allow-list.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: point ee-repo-ref at the external secret references branch
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: keep external secret references intact on delete, deploy and export
- Deleting a reference no longer runs the managed backend cleanup, which
could delete the secret it points at.
- Deploying a variable to another workspace copies the reference, which
the target's allow-list then checks, instead of its resolved value.
- A plain-secrets workspace export writes references verbatim.
- Reference paths reject backslashes, `#` and control characters, which
the URL parser would otherwise normalize past the allow-list.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: skip external secret references in key rotation and the read cache
- Workspace key rotation no longer tries to decrypt references.
- `get_value?allow_cache=true` does not cache a resolved reference, so
Vault rotation and allow-list changes apply on the next read.
- `VaultSettings.mount_path` is optional in the OpenAPI spec, matching
its serde default.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: keep the OSS Vault reader stub public and regenerate workspace tool schemas
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: restrict external secret references to workspace admins and keep them out of the managed Vault storage
Creating, repointing or removing a reference now takes a workspace admin, on
create and update including already-encrypted pushes and cross-workspace
deploys; the variable form disables the toggle and fields for anyone else.
A reference into the storage of Windmill's own Vault secret backend (same
address, namespace folded into the path) is refused on save and on resolve,
whatever the allow-list says.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: compare external secret references as written in workspace comparison
Two references that currently resolve to the same value still point at
different secrets, so comparing their resolved values hid a repoint from the
diff and from deployment.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: let external secret references reuse the Vault backend connection
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: hide the external reference toggle from non-admins unless already set
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: read whole Vault secrets, show allowed paths, and pick the variable type in one control
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: mask JSON fields only for whole Vault secrets, and skip PEM armor and JSON lines
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: align the reference editor and settings warning with the form and alert guidelines
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: let a saved reference become non-secret directly, and warn when no prefix is allowed
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: save an empty value when a reference is switched to another type
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: keep a saved reference's baseline through type round trips
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: drop an unused binding in the reference parser
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: offer vault reference only when a vault path is allowed
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: update ee-repo-ref to c0fd22ba77e6618cea7611d72fe2e75c8855c595
This commit updates the EE repository reference after PR #932 was merged in windmill-ee-private.
Previous ee-repo-ref: 56cba4e7771e7a87e56a67eb115549a31dd12b1a
New ee-repo-ref: c0fd22ba77e6618cea7611d72fe2e75c8855c595
Automated by sync-ee-ref workflow.
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Ruben Fiszel <ruben@windmill.dev>
Co-authored-by: windmill-internal-app[bot] <windmill-internal-app[bot]@users.noreply.github.com>
* feat: add read-only generic HTTP secret store backend
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: keep forks and oauth tokens working under the http secret store
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: redact http store credentials, refuse workspace id changes over references
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: refuse invalid http secret store settings when they are saved
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: update http store form readers after in-place edits
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: keep the ai config comment above its hook arm
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: update ee-repo-ref to 235a17b0ffe64a77bc816b8c38270437d3596674
This commit updates the EE repository reference after PR #935 was merged in windmill-ee-private.
Previous ee-repo-ref: 3c46237920cc20fc4ab34bd07d0773f761aa63d2
New ee-repo-ref: 235a17b0ffe64a77bc816b8c38270437d3596674
Automated by sync-ee-ref workflow.
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: windmill-internal-app[bot] <windmill-internal-app[bot]@users.noreply.github.com>
* fix(cli): drop deprecated and unused fields from trigger new templates
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): flow preview takes the windmill path and runs hub steps with --step
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): run a deployed script step with its deployed lock in flow preview --step
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): flow preview --remote honors nonDottedPaths when resolving the folder
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The worker schedules step i after the sleep of module i-1
(worker_flow.rs), so a module's sleep delays the step after it. The
schema said "Delay before executing this step", and that text reaches
the write-flow skill, the flow chat and the MCP session instructions.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat: add ai review to the drafts page, draft diffs and the session review
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: drop an ai review when its workspace changes
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: follow the diff version picker in ai review and review only your own draft from the badge
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: give the drafts page ai review the full width
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat: gate guest apps by their mode and the protection rule alone
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: keep apps that admitted no guest closed on upgrade
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: update ee-repo-ref to 0605eac866b49f0de913ab41c1168b79eec31ca0
This commit updates the EE repository reference after PR #931 was merged in windmill-ee-private.
Previous ee-repo-ref: 1f643a1aaa697578b36d67982358299ee20af7f4
New ee-repo-ref: 0605eac866b49f0de913ab41c1168b79eec31ca0
Automated by sync-ee-ref workflow.
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: windmill-internal-app[bot] <windmill-internal-app[bot]@users.noreply.github.com>
* fix(cli): resolve /ui/ in app dev and lint, and its bare imports from the app
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): match shared ui/ files by real path so a symlinked ui/ still redirects
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): keep relative css @import in shared ui/ resolving next to the file
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(cli): let esbuild resolve relative css @import in ui/ so suffixes keep working
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat: rebuild raw apps on a ui/-only change and fail sync push on ui/ errors
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: catch unquoted css ui/ imports and surface app lookup errors
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: match the raw app metadata file on windows sync paths
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat: add ai review to deployment requests
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: bound ai review fetches and surface unreadable items
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: add fix in ai session and model picker to deployment ai review
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: add workspace instructions for deployment ai review
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: read review instructions from the parent and bind ai review to the fork
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: pin the fix-all session preview to the fork's compare page
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: show the protection-rule bypass toggle inline
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: make the bypass toggle small and red
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor: drop workspace-settings instructions from deployment ai review
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: folder-scoped review instructions for the deployment ai review
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: review the selected items with ai on compare and deploy
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: keep reviewing when review instructions cannot be listed
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: say the review instruction floor is a prompt request, not enforcement
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: mark an ai review out of date when its items change
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: update ee-repo-ref to 77703cf32e58964906d87ee83ddda44b5b8d1b7e
This commit updates the EE repository reference after PR #926 was merged in windmill-ee-private.
Previous ee-repo-ref: e30ab9e69d1854fcaed5620c934ace32acb0a729
New ee-repo-ref: 77703cf32e58964906d87ee83ddda44b5b8d1b7e
Automated by sync-ee-ref workflow.
* feat: review git sync pull requests with wmill review
* fix: withhold retyped resources and encryption keys, fall back from the responses route
* fix: withhold fileset children, workspace-specific resources and pathspec-named files
* feat: include the ready-to-post review in wmill review --json
* feat: review a workspace synced into a repository subfolder
* docs: say what wmill review takes from flags rather than wmill.yaml
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: windmill-internal-app[bot] <windmill-internal-app[bot]@users.noreply.github.com>
* feat: fork capability per role and fork role mapping on rulesets
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: keep unset fork for unrestricted roles and apply fork role mapping to fork-owner adds
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: fork_roles feature usage telemetry
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: derive an unset fork in the role editor as the server does
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: update ee-repo-ref to d535972f0b35c6a7f257720816bdaec18465adef
This commit updates the EE repository reference after PR #929 was merged in windmill-ee-private.
Previous ee-repo-ref: 4a8d59cd1563382fcec85b1367f7e15e09bc13c2
New ee-repo-ref: d535972f0b35c6a7f257720816bdaec18465adef
Automated by sync-ee-ref workflow.
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: windmill-internal-app[bot] <windmill-internal-app[bot]@users.noreply.github.com>
* feat: app conversations through the memory_id query parameter, chat-mode flows included
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: regenerate the mcp session instructions
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: type backendAsync's memoryId option in the eval diagnostics
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: pin git-sync hub scripts to windmill-cli 1.849.0
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: memoryId option on the sync backend call too
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: bump the ui builder artifact for the memoryId option
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: shared-utils 1.0.14
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: cli takes shared-utils 1.0.14 for the memoryId option
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test: pin the app conversation scoping and the memoryId signatures
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test: assert the ownership refusal, not any refusal
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test: match the memoryId option in the cli wmill.ts signature tests
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: file an app's turns as the deployed flow's conversation, preview included
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat: guidance for building standalone ai agents in ai sessions
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: agent guidance for resource-only sessions, no flow tools
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: tell the user to deploy a drafted tool script with its agent
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: scope plain agent values, document tool_inputs, list agents in get_instructions
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: test and run ai agents from ai sessions, open agents in their editor
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: full-bleed agent editor tabs, back to the run form for agent tests
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: describe read-and-run as running agents too, pin agent run links
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: host the agent editor natively in session tabs
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: switch the agent editor to tabs below 900px
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: name an agent's session tab after its summary
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: show deployed agents in session tabs, open and run them from the chat
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: deploy agents from the chat, report agent tabs as the active editor
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: pick agents from the tab picker, name their tabs, scope the agent page to its workspace
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: leave open editors alone on agent writes, read the agent page's workspace user
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: refresh an agent's deployed page when the chat deploys or deletes it
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: name agent tabs before they load, mark agents in the changes drawer, stay on a deleted agent's tab
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: keep a cleared agent summary out of its tab name
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: keep the resource drawer's json option that the resources list still passes
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: open an agent in an AI session from its pages, fix review findings on agent tabs
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: name the reserved agent tool names in the agent guidance
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: reload an agent's editor on a discard, open a new agent in a session
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: show agents as agents on compare and deploy, name a never-deployed one by its path
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: keep a deployed agent's type in its draft diff
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: link a fork row to the agent editor only on the side that holds the agent
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: guard agent page paths, mark drafted agents in the picker, side-aware agent rows on fork compare
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat(ai-agent): built-in approval tool that parks the agent
An AI agent step can now be given a built-in "Request approval" tool. The model
calls `request_approval` with a message; the agent stores its conversation in
the new `ai_agent_checkpoint` table, releases its worker by parking its own
queue row like a workflow-as-code parent, and resumes with the answer (approved,
approver, comment) or a timeout once someone answers from the run page.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(ai-agent): tie approval answers to their request and hold the turn
- A turn that asks for approval runs none of its other calls; they are refused
so the model repeats them after the answer.
- The run page sends the request's call id. An answer naming another request is
ignored and the agent parks again for the time left; `suspend` is zeroed when
the answer is read, so answers sent while the agent runs are refused.
- The checkpoint is read whatever the current roster holds, the answer's
outcome is written by position, and a cancel that beats the park completes
the job as cancelled.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(ai-agent): say why calls beside an invalid approval request were refused
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(ai-agent): one approval form per request, none on a finished run
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(ai-agent): answer approval requests from a flow's chat
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(ai-agent): show chat approvals for agents that do not stream
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(ai-agent): approval as a per-tool setting, built-in tool asks a question
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(ai-agent): say when a nested agent leaves out tools that require approval
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(ai-agent): show chat approvals and questions on the tool's own card
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(ai-agent): question choices, and approval buttons shared with approval steps
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(ai-agent): show a waiting agent as suspended, and refused calls as not run
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(ai-agent): each added chat card shows its own call, answered marker keyed by job
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(ai-agent): approve and reject a held call through resume_suspended
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(ai-agent): require approval in a tool settings tab, plain descriptions on built-in tool panes
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(ai-agent): sentence case for the web search tool label
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat(ai-agent): built-in tool drawers explain themselves in the header subtitle
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(ai-agent): clearer question tool subtitle
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(ai-agent): badge the tool settings tab like run settings
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(ai-agent): regenerate system prompts and MCP session files
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The change-versions job on the release PR failed to push after the branch
was deleted on merge, so v1.848.0 shipped with only version.txt bumped.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat: run a workspace handler when a secret variable expires
Secret variables gain an optional `value_expires_at`, and a workspace can point
at a script or flow to run once that date passes, so a rotation is driven by the
platform instead of tracked out of band.
The secret never leaves the database. The sweep selects the path, description and
expiry and nothing else, so the handler is given a reference to rotate rather than
a value to handle. Job results are stored in cleartext and shown in Runs, which is
what makes that a boundary rather than a preference; a test asserts the job's args
never contain the value.
Each row is claimed by writing `expiration_dispatched_for` in the same transaction
as the push, so a failed push un-claims it and a lost race claims nothing. Moving
the date re-arms the row; re-saving the same date does not. A pass takes at most
100 rows under a transaction-scoped advisory lock, and orders so that one broken
workspace cannot starve the rest.
Dispatch runs as `g/variable_expiration_handler`, exempt from the CE group limit
and from non-premium exec metering the way the error and schedule handlers already
are. A handler that keeps failing backs off and raises a critical alert instead of
retrying every pass, and the back-off ends when the handler is repointed.
The expiry travels with the variable through workspace clone, tarball export and
workspace comparison. The dispatch marker deliberately does not, so a fork re-arms
on its own copy.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* feat(frontend): expose variable value expiration in the UI
The variable drawer takes an optional expiry on a secret value, and the variables
list badges it, turning red once the date has passed. A workspace settings tab
picks the handler, its extra args, and whether variables under `u/` are skipped.
That mute flag is stored inside the handler setting, so the toggle stays disabled
until a handler is picked: saving it on its own would clear the setting it lives
in and still report success.
The expiry is carried as a tri-state through the draft deploy and copilot paths —
absent leaves the remote value alone, an explicit null clears it — so deploying a
draft cannot silently drop a date someone set elsewhere.
The settings tab names the one case where the configured identity does not apply:
a handler script carrying `on_behalf_of` runs as that user rather than as
`g/variable_expiration_handler`, which matters because the same tab asks the admin
to grant that group write access to the variables it rotates.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* feat(cli): sync variable expiry and the workspace expiration handler
`wmill sync` carries `value_expires_at` on variables in both directions, and
pushes the workspace handler alongside the error and success handlers in the
grouped settings format. Dropping the key from a variable's yaml clears the
remote expiry, so the file stays canonical rather than accumulating fields that
can only ever be added.
The handler follows the same rule, with the caveat recorded where the type is
declared: an omitted handler only reaches the clear when some other setting
differs, because the push short-circuits on a comparison that walks the local
object's keys and so never sees a missing one. That gate is shared with the two
existing handlers and is left as it is here.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix(frontend): open the variable expiration handler template in a new tab
The "Create a handler" button hands its script template to /scripts/add through
the URL hash, which `load` reads from `window.location`. A client-side navigation
leaves the previous page's hash in place, so the payload was dropped and the
editor opened on the default template at a `u/` path. `target="_blank"` forces a
full page load, matching the success handler's "Create from template" button.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix(frontend): make the variable expiry field state its own status
The expiry field rendered a DateTimeInput whose time defaults to 12:00 when it
holds no value, so a variable with no expiry looked like one already configured,
and "cleared" looked identical to "never set". Setting an expiry is optional, so
the field has to say which it is.
Rebuild it on the shape ScriptAdvancedSettings already uses for Timeout, Cache and
Concurrency limits: a toggle whose checked state is the stored value being present,
seeding a date on enable rather than revealing an empty picker, with the input
under its own label. Drop `clearable` with it, so the toggle is the single way to
mean "no expiry" instead of competing with an X.
Stop the surrounding copy promising a run that may not happen. A handler is only
dispatched if the workspace has one configured and does not skip u/ paths, so the
list tooltip now states the date alone, and the form hedges both conditions,
naming the u/ mute only on personal paths where it can apply.
Also anchor the mute toggle's tooltip: Popover's trigger is a span around a
block-level label, which stretched to the full width of its SettingCard and left
the popup floating beside the card rather than under the control.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix(rust-client): initialize value_expires_at in the variable models
The generated `CreateVariable` / `EditVariable` structs gain the field from
openapi.yaml, and client.rs builds both with exhaustive literals.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix(frontend): drop extra_args when the variable expiration handler is cleared
Clearing the handler nulls the whole setting server-side, extra_args included,
but the tab kept its loaded copy. A handler picked afterwards without reloading
was persisted with the cleared one's arguments, which the tab does not display.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* feat: back the variable expiration handler's built-in Slack and Teams destinations
Backfills the Slack bot token grant for g/variable_expiration_handler, mirroring
20231016142659 for g/error_handler: the slack_bot folder's extra_perms is written
once at Slack connect and never refreshed, and disconnecting leaves the folder
behind, so workspaces that already connected Slack cannot pick the grant up from
the creation-time list alone.
Adds run_variable_expiration_test_job so an admin can exercise the handler on
demand rather than waiting for a real expiry, which may be months away. It goes
through push_variable_expiration_handler so the test run proves what matters:
the handler resolves, and the group can read what it needs, under the same
identity and argument shape the sweep uses.
Also covers extra_args on the edit endpoint, which the settings tab now writes
for the built-ins' channel. The endpoint rebuilds the setting from the request,
so an omitted extra_args erases it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Do7wJTnL6MG6ngFpCGW4DG
* feat(frontend): offer Slack and Teams as variable expiration handlers
Gives the variable expiration tab the same no-code destinations the workspace
error handler has, so "tell #ops before this credential expires" no longer
requires writing a script.
A sibling component rather than a fourth mode of ErrorOrRecoveryHandler: that
one is shared with the workspace error handler and the three schedule handlers,
and its stripped-args list, hub path suffixes and Email tab are all
error-shaped. This reuses the pieces that are already generic
(SlackConnectionStatus, TeamsConnectionStatus, ChannelSelector, ScriptPicker,
SchemaForm) and leaves those five call sites untouched.
extra_args stops being an API/CLI-only escape hatch now that the built-ins write
their channel into it, so it joins the unsaved-changes comparison and the
discard path, normalised through the existing helper that drops the two
auto-managed keys.
The two hub ids are placeholders until the scripts are pushed to the hub.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Do7wJTnL6MG6ngFpCGW4DG
* fix(frontend): scope the handler identity notice to the chosen destination
The notice told every admin to grant g/variable_expiration_handler write access
to the variables it rotates. That is right for a custom handler and wrong for
the built-ins, which only post a message and are granted the Slack bot token by
migration. Following it for a Slack handler would hand a group write access to
the workspace's secrets for no reason.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Do7wJTnL6MG6ngFpCGW4DG
* feat(frontend): flag the Slack and Teams handlers as EE
Connecting a workspace to Slack or Teams is EE-only (oauth2_oss.rs returns
"Slack only available on enterprise"), so on CE those two tabs can never be
completed. Says so up front, the way the error/success handler tab does,
instead of leaving the user at a "not connected" badge with no working path.
Only on those two tabs: a custom script or flow handler is CE.
Drops the "Connect Slack first" alert, now that the banner and the connection
badge above it already say it twice.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Do7wJTnL6MG6ngFpCGW4DG
* chore(backend): regenerate the sqlx cache after the merge
The merged workspace_settings column list in change_workspace_id is a new
query text, so it needs a new cached entry. Drops the two pre-merge entries
it supersedes; both had been left with conflict markers by the merge, since
rename/rename markers are eight characters and escape the usual scan.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Do7wJTnL6MG6ngFpCGW4DG
* fix(cli): narrow the expiry-clear check to a variable that exists remotely
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Do7wJTnL6MG6ngFpCGW4DG
* feat(frontend): point the built-in handlers at their published hub scripts
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* chore(backend): regenerate the sqlx cache after the merge
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* fix(frontend): disable the Slack and Teams handler controls without a license
Matches the workspace error handler, which greys out its built-in destinations
and hides the test button on an unlicensed instance. The custom destination stays
editable: unlike the error handler, the variable expiration handler itself is not
an EE feature.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* feat: record which destination a variable expiration handler uses
handler_configured now counts slack, teams, custom or cleared instead of
set or cleared, so usage shows whether the built-in destinations are picked.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(frontend): let the variable expiration handler template run on any worker
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: guard the variable expiration test endpoint and correct its help text
* fix: reuse the error handler's slack arg and built-in path helpers
* docs: trim variable expiration sweep and backfill comments
* feat: put the variable value expiration under an advanced section
* fix: restrict the expiration test job to built-ins and keep expiry on conflict reload
* fix: link the expiry hint to the variable's workspace and document built-in test paths
* fix: give the expiration sweep its own lock id and reuse double_option
* fix: pin the variable expiration presets so the hub-paths test accepts them
* feat: let the variable expiration handler set how far ahead it runs
* fix: give the notify before expiry setting its own card
* feat: remind the variable expiration handler at a set interval
* fix: tighten the gap between the Slack channel field and its test button
* feat: refuse a value expiry on variables linked to an OAuth account
* refactor: reuse the shared handler form for variable expiration
* refactor: sweep expiring variables round-robin and check the handler exists
* chore: trim comments to the constraints they record
* fix: compare expiry dates by moment when deploying a variable draft
* refactor: rename value_expires_at to value_valid_until
* fix: neutralize variable fields in expiration handler args
* fix: reserve the variable_expiration_handler group name for admins
* fix: send first expiry notices before reminders
* test: pin that a handler failing to start leaves its rows unclaimed
* chore: say any hub handler path skips the existence check
* fix: empty a pre-existing handler group before granting it the Slack token
* docs: correct the registered feature usage counts
* fix: let a workspace whose handler failed to start sit out for an hour
* fix: send first notices before reminders across workspaces
* fix: end a failed handler's wait as soon as it is redeployed
* fix: show an expiry-only variable change in the AI fork diff
* chore: regenerate workspace tool schemas
* test: keep one variable expiration guard per behavior
* fix: use the renamed hub expiration handlers and template
* feat: carry the variable expiry in windmill-utils-internal 1.8.4
* fix: keep the variable expiry through MCP drafts
* chore: bump windmill-utils-internal to 1.8.4
* fix: keep the variable expiry through mcp deploys
* fix: disable saving a slack or teams expiry handler without ee
* fix: skip the failure mark when the expiry handler was saved mid-sweep
* fix: count expiry telemetry only where the expiry changed
* test: assert the exact variable expiry in export and cli push tests
* fix: stamp an expiry handler failure with the pass's read time
* fix: wait for a pending handler lock instead of marking it failed
* test: isolate expiry handler tests from the deployed-script cache
* fix: retry a failing expiry handler every pass instead of waiting an hour
* chore: update ee-repo-ref to b6e23d229966cf0019c0a1926a254fda658d8def
This commit updates the EE repository reference after PR #744 was merged in windmill-ee-private.
Previous ee-repo-ref: c52c06d145b13a6fb04459e85ca5818bf3c1bff4
New ee-repo-ref: b6e23d229966cf0019c0a1926a254fda658d8def
Automated by sync-ee-ref workflow.
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: windmill-internal-app[bot] <windmill-internal-app[bot]@users.noreply.github.com>
Co-authored-by: hugocasa <hugo@casademont.ch>