Custom actions that follow your prompt
Custom agent actions no longer have to pretend that every job ends as a task update, a new task, or a project-context change. New actions now default to Not specified (follow prompt), which adds no result-target instruction and lets the action prompt define the work. Project actions can also explicitly target Repository changes when the intended result is code, configuration, a version bump, or Git work. The distinction between result and permission remains visible: Propose produces a reviewable answer without changing the board, files, or Git, while Apply permits only the changes the prompt requests. The action editor now explains Context, Result target, and Behavior directly beneath each choice, and launch confirmation calls out repository and open-ended permissions before a run starts.
Workflow hooks have also been narrowed to the automations that earn their place. Add comment, Set priority, Require move note, and Require fields are gone. Change tags, Set assignee, Set dates, Run agent action, and Run project command remain, with stronger warnings around token use, tools, local permissions, and commands that can modify files. Older saved workflows quietly drop retired hooks while preserving supported hooks and semantic destinations. The review role is now simply called Review destination.