Thanks for the suggestion! That’s definitely in our roadmap. We’re currently compiling an repository of autotask examples on github (which we’ll make public soon), and the next step is for Defender to be able to source them directly, without the need for copy-paste.
This is the only part that’s delicate. We definitely don’t want to have the power to push a change to our users’ autotasks code. We could add an option to “manually update” when the template changes, though.
yep sounds about right. could have a notice there that there’s a new update to the task, and i could click a “view changes” button that has a nice in page diff, like quickdiff.com or something similar, and if we like the changes - have another button to update the task with the new version.